US tax-benefit domain knowledge for analysts computing household or population impacts with the policyengine package (pe.us). Load for: which entity a US program attaches to (tax_unit vs spm_unit vs person), tax-unit role flags and filing status, post-OBBBA current-law values (2026 CTC, standard deduction, SALT cap), the parameter tree (gov.irs / gov.states.{xx} / gov.usda.snap / gov.ssa), state income-tax and credit coverage, and SNAP monthly/FPL semantics. Triggers: EITC, CTC, SNAP, TANF, SSI, income tax, state income tax, standard deduction, SALT cap, federal poverty level, spm_unit, tax_unit, filing status, is_tax_unit_dependent, household_net_income, in_poverty, state credit, CalEITC, ca_eitc, ny_eitc, OBBBA. NOT for: implementing new US variables/parameters (use policyengine-model-development); Medicaid/ACA/CHIP/Medicare (use policyengine-healthcare); the core calculate_household / Simulation / reform mechanics shared across countries (use the policyengine skill).
How to install policyengine-us?
policyengine/policyengine-claude/policyengine-us
$npx -y skills add policyengine/policyengine-claude --skill policyengine-usInstalls into the current project.
›Prefer a prompt? Paste this to your agent
Run `npx skills use "https://github.com/policyengine/policyengine-claude" --skill "policyengine/policyengine-claude/policyengine-us"` and follow the generated skill instructions now. Read its complete output, redirecting it to a temporary file first if necessary. Resolve relative paths from the supporting-files directory it provides.
Use the skills in "https://github.com/policyengine/policyengine-claude" that are relevant to the current task. Run `npx skills add "https://github.com/policyengine/policyengine-claude"` and select the relevant skills, then follow their instructions.
Related
6 picksType
- gpt-image-2Create or edit images with Pilio GPT Image 2 through the unified Pilio developer API.Jul 2026
- spec-driven-implementationDrive a spec-first workflow for substantial features by writing PRODUCT.md before implementation, writing TECH.md when warranted, and keeping both specs…Jul 2026
- review-prReview a pull request diff and write structured feedback to review.json for the workflow to publish.Jul 2026
- write-product-specWrite a PRODUCT.md spec for a significant user-facing feature in Warp, focused on detailed behavior and validation.Jul 2026
- write-tech-specWrite a TECH.md spec for a significant Warp feature after researching the current codebase and implementation constraints.Jul 2026
- fix-errorsFix compilation errors, linting issues, and test failures in the warp Rust codebase. Covers presubmit checks, WASM-specific errors, and running specific tests.Jul 2026
