skills/technical-patterns/policyengine-aggregation-skill/SKILL.md
PolicyEngine aggregation patterns - using adds attribute and add() function for summing variables across entities
npx skillsauth add policyengine/policyengine-claude policyengine-aggregationInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Essential patterns for summing variables across entities in PolicyEngine.
Is the variable ONLY a sum of other variables?
│
├─ YES → Use `adds` attribute (NO formula needed!)
│ adds = ["var1", "var2"]
│
└─ NO → Use `add()` function in formula
(when you need max_, where, conditions, etc.)
| Need | Use | Example |
|------|-----|---------|
| Simple sum | adds | adds = ["var1", "var2"] |
| Sum from parameters | adds | adds = "gov.path.to.list" |
| Sum + max_() | add() | max_(0, add(...)) |
| Sum + where() | add() | where(cond, add(...), 0) |
| Sum + conditions | add() | if cond: add(...) |
| Count booleans | adds | adds = ["is_eligible"] |
adds Class Attribute (Preferred When Possible)Use adds when a variable is ONLY the sum of other variables with NO additional logic.
class variable_name(Variable):
value_type = float
entity = Entity
definition_period = PERIOD
# Option 1: List of variables
adds = ["variable1", "variable2", "variable3"]
# Option 2: Parameter tree path
adds = "gov.path.to.parameter.list"
formula() method neededclass tanf_gross_earned_income(Variable):
value_type = float
entity = SPMUnit
label = "TANF gross earned income"
unit = USD
definition_period = MONTH
adds = ["employment_income", "self_employment_income"]
# NO formula needed! Automatically:
# 1. Gets each person's employment_income
# 2. Gets each person's self_employment_income
# 3. Sums all values across SPM unit members
class income_tax_refundable_credits(Variable):
value_type = float
entity = TaxUnit
definition_period = YEAR
adds = "gov.irs.credits.refundable"
# Parameter file contains list like:
# - earned_income_tax_credit
# - child_tax_credit
# - additional_child_tax_credit
class count_eligible_people(Variable):
value_type = int
entity = SPMUnit
definition_period = YEAR
adds = ["is_eligible_person"]
# Automatically sums True (1) and False (0) across members
add() Function (When Logic Needed)Use add() inside a formula() when you need:
max_(), where(), or conditionsfrom policyengine_us.model_api import *
def formula(entity, period, parameters):
result = add(entity, period, variable_list)
Parameters:
entity: The entity to operate onperiod: The time period for calculationvariable_list: List of variable names or parameter pathclass adjusted_earned_income(Variable):
value_type = float
entity = SPMUnit
definition_period = MONTH
def formula(spm_unit, period, parameters):
# Need max_() to clip negative values
gross = add(spm_unit, period, ["employment_income", "self_employment_income"])
return max_(0, gross) # Prevent negative income
class household_benefits(Variable):
value_type = float
entity = Household
definition_period = YEAR
def formula(household, period, parameters):
# Sum existing benefits
BENEFITS = ["snap", "tanf", "ssi", "social_security"]
existing = add(household, period, BENEFITS)
# Add new benefit conditionally
new_benefit = household("special_benefit", period)
p = parameters(period).gov.special_benefit
if p.include_in_total:
return existing + new_benefit
return existing
class total_deductions(Variable):
value_type = float
entity = TaxUnit
definition_period = YEAR
def formula(tax_unit, period, parameters):
p = parameters(period).gov.irs.deductions
# Get standard deductions using parameter list
standard = add(tax_unit, period, p.standard_items)
# Apply phase-out logic
income = tax_unit("adjusted_gross_income", period)
phase_out_rate = p.phase_out_rate
phase_out_start = p.phase_out_start
reduction = max_(0, (income - phase_out_start) * phase_out_rate)
return max_(0, standard - reduction)
# WRONG - Never do this!
def formula(spm_unit, period, parameters):
person = spm_unit.members
employment = person("employment_income", period)
self_emp = person("self_employment_income", period)
return spm_unit.sum(employment + self_emp) # ❌ BAD
# RIGHT - Clean and simple
adds = ["employment_income", "self_employment_income"] # ✅ GOOD
# WRONG - Unnecessary complexity
def formula(spm_unit, period, parameters):
return add(spm_unit, period, ["income1", "income2"]) # ❌ Overkill
# RIGHT - Simpler
adds = ["income1", "income2"] # ✅ GOOD
When using adds or add(), PolicyEngine automatically handles entity aggregation:
class household_total_income(Variable):
entity = Household # Higher-level entity
definition_period = YEAR
adds = ["employment_income", "self_employment_income"]
# employment_income is defined for Person (lower-level)
# PolicyEngine automatically:
# 1. Gets employment_income for each person in household
# 2. Gets self_employment_income for each person
# 3. Sums all values to household level
This works across all entity hierarchies:
Parameters can define lists of variables to sum:
Parameter file (gov/irs/credits/refundable.yaml):
description: List of refundable tax credits
values:
2024-01-01:
- earned_income_tax_credit
- child_tax_credit
- additional_child_tax_credit
Usage in variable:
adds = "gov.irs.credits.refundable"
# Automatically sums all credits in the list
| Scenario | Solution | Code |
|----------|----------|------|
| Sum 2-3 variables | adds attribute | adds = ["var1", "var2"] |
| Sum many variables | Parameter list | adds = "gov.path.list" |
| Sum + prevent negatives | add() with max_() | max_(0, add(...)) |
| Sum + conditional | add() with where() | where(eligible, add(...), 0) |
| Sum + phase-out | add() with calculation | add(...) - reduction |
| Count people/entities | adds with boolean | adds = ["is_child"] |
development
ALWAYS LOAD THIS SKILL for PolicyEngine PR reviews, including when the user invokes $review-program or Codex /review on a PolicyEngine PR. Performs read-only code validation, source-reference checks, regulatory review, optional PDF audit, summary reporting, and optional GitHub comment posting.
development
Use when the user invokes $fix-pr or asks Codex to apply fixes to a PolicyEngine PR based on $review-program findings, GitHub review comments, CI failures, or local review reports.
development
Use when the user invokes $encode-policy-v2 or asks Codex to implement a new PolicyEngine-US state benefit program from official rules. Covers research, source collection, requirement extraction, scoped implementation, tests, validation, and draft PR preparation.
development
Deploying PolicyEngine frontend apps to Vercel - naming, scope, team settings