Run any Skill in Manus with one click

encode-policy-v2

Stars0

Forks2

UpdatedMay 19, 2026 at 20:53

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.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

PolicyEngine

PolicyEngine/policyengine-skills

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

File Explorer

3 files

SKILL.md

readonly

name	encode-policy-v2
description	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.

encode-policy-v2

This is the Codex equivalent of the Claude /encode-policy-v2 command.

Treat the text after $encode-policy-v2 as the command arguments:

$encode-policy-v2 STATE PROGRAM [--skip-review] [--research-only] [--600dpi]

Before starting, read workflow.md and subagents.md. Follow them as the source of truth for phases, checkpoints, handoff files, validation gates, and Codex subagent delegation.

Operational rules:

Use /tmp/{PREFIX}-... handoff files to keep large research, diffs, PDFs, and reports out of the main context.
Ask the user before making scope decisions that affect modeled requirements.
Use PolicyEngine skills explicitly when implementing: $policyengine-us, $policyengine-parameter-patterns, $policyengine-variable-patterns, $policyengine-testing-patterns, $policyengine-code-style, $policyengine-code-organization, and $policyengine-vectorization.
This workflow is designed for Codex subagents. When subagent use is available and authorized, delegate independent phases to worker or explorer agents using subagents.md; otherwise execute the same steps directly while preserving handoff-file boundaries.
Every PDF reference href must include #page=XX, using the PDF file page number.

More from this repository

same repository

policyengine-calibration-diagnostics

PolicyEngine/policyengine-skills

Sensitivity registry for PolicyEngine microsim results — maps {program × deviation signature} to the most likely calibration target or imputed variable driving the mismatch. The knowledge base that powers the calibration-diagnostics agent. Load when investigating why a microsim result differs from a prior score, or when reviewing whether a reform classification is calibration-sensitive. Triggers: "why does my reform not match", "policyengine cost off", "calibration mismatch", "imputed variable", "takeup rate", "non-filer", "itemizer share", "small state variance", "ECPS calibration target", "policyengine-us-data target", "calibration dashboard", "diagnose mismatch", "deviation signature".

2026-06-220

policyengine-prior-scores

PolicyEngine/policyengine-skills

Structured index of PolicyEngine's previously-published scored reforms. Use this skill to find an anchor for Stage 5 comparison in /analyze-policy, or any time you need a benchmark magnitude for a new policy analysis. Returns a queryable mapping of {reform name → (cost, poverty, distribution, year, methodology)} drawn from policyengine.org/{us,uk,canada}/research and blog.policyengine.org. Triggers: "prior PE score", "PolicyEngine has scored", "what did PE find", "PE benchmark", "anchor reform", "comparable reform", "EITC expansion scored", "CTC expansion scored", "SALT cap analysis", "state CTC analysis", "ARPA reform impact", "American Family Act score".

2026-06-220

policyengine-api-v2

PolicyEngine/policyengine-skills

PolicyEngine API v2 - Next-generation microservices architecture with monorepo structure

2026-06-080

python

PolicyEngine/policyengine-skills

ALWAYS LOAD THIS SKILL before setting up any Python environment or installing packages. Defines the standard: uv, Python 3.13, uv pip install, .venv at project root. Triggers: "set up python", "install python", "create a venv", "virtual environment", "pip install", "install packages", "uv pip", "uv venv", "python version", "VIRTUAL_ENV", "venv conflict", "which python", "activate", "deactivate", "run the script", "run with uv", "uv run", "pyproject.toml", "install dependencies", "install requirements", "install the package", "editable install", "pip install -e", "latest package", "latest version", "current version", "newest version".

2026-06-070

policyengine-microsimulation

PolicyEngine/policyengine-skills

ALWAYS USE THIS SKILL for PolicyEngine microsimulation, population-level analysis, winners/losers calculations. Triggers: microsimulation, share who would lose/gain, policy impact, national average, weighted analysis, cost, revenue impact, budgetary, estimate the cost, federal revenues, tax revenue, budget score, how much would it cost, how much would the policy cost, total cost of, aggregate impact, cost to the government, revenue loss, fiscal impact, poverty impact, child poverty, deep poverty, poverty rate, poverty reduction, how many people lifted out of poverty, SPM poverty, distributional impact, state tax, state-level, California, New York, UBI, universal basic income, flat tax, standard deduction, winners and losers, winners, losers, inequality, Gini, decile, SALT, marginal tax rate, effective tax rate. NOT for single-household calculations like "what would my benefit be" - use policyengine-us or policyengine-uk for those. Use this skill's code pattern; explore codebase for parameter paths if needed.

2026-06-070

policyengine-python-client

PolicyEngine/policyengine-skills

ONLY use this skill when users explicitly ask about the PolicyEngine Python package installation, REST API endpoints, API authentication, rate limits, or policyengine.py client library. DO NOT use for household benefit/tax calculations — ALWAYS use policyengine-us or policyengine-uk instead. This skill is about the API/client tooling itself, not about calculating benefits or taxes.

2026-06-070

name	encode-policy-v2
description	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.

encode-policy-v2

This is the Codex equivalent of the Claude /encode-policy-v2 command.

Treat the text after $encode-policy-v2 as the command arguments:

$encode-policy-v2 STATE PROGRAM [--skip-review] [--research-only] [--600dpi]

Before starting, read workflow.md and subagents.md. Follow them as the source of truth for phases, checkpoints, handoff files, validation gates, and Codex subagent delegation.

Operational rules:

Use /tmp/{PREFIX}-... handoff files to keep large research, diffs, PDFs, and reports out of the main context.
Ask the user before making scope decisions that affect modeled requirements.
Use PolicyEngine skills explicitly when implementing: $policyengine-us, $policyengine-parameter-patterns, $policyengine-variable-patterns, $policyengine-testing-patterns, $policyengine-code-style, $policyengine-code-organization, and $policyengine-vectorization.
This workflow is designed for Codex subagents. When subagent use is available and authorized, delegate independent phases to worker or explorer agents using subagents.md; otherwise execute the same steps directly while preserving handoff-file boundaries.
Every PDF reference href must include #page=XX, using the PDF file page number.