build-cge
Skill4 starsChanged 6 days agoMITView on GitHub
Builds a CGE model (static or recursive-dynamic, single- or multi-region) with benchmark replication, closures, elasticity sensitivity and welfare decomposition.
In this repository210 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .cursor/rules/ai-ml-code.mdcCursor rule
- .cursor/rules/code-translation.mdcCursor rule
- .cursor/rules/data-pipelines.mdcCursor rule
- .cursor/rules/documentation.mdcCursor rule
- .cursor/rules/dsge-code.mdcCursor rule
- .cursor/rules/econometrics-code.mdcCursor rule
- .cursor/rules/eviews-code.mdcCursor rule
- .cursor/rules/forecasts.mdcCursor rule
- .cursor/rules/gempack-code.mdcCursor rule
- .cursor/rules/lego-manifests.mdcCursor rule
- .cursor/rules/llm-code.mdcCursor rule
- .cursor/rules/model-code.mdcCursor rule
- .cursor/rules/notebooks-and-scripts.mdcCursor rule
- .cursor/rules/r-code.mdcCursor rule
- .cursor/rules/restricted-data.mdcCursor rule
- .cursor/rules/rl-code.mdcCursor rule
- .cursor/rules/sectoral-trade-climate-code.mdcCursor rule
- .cursor/rules/semi-structural-code.mdcCursor rule
- .cursor/rules/stata-code.mdcCursor rule
- .cursor/rules/tests.mdcCursor rule
- .cursor/rules/validation.mdcCursor rule
- adoptSkill
- ai-auditSkill
- backtestSkill
- build-abmSkill
- build-causal-mlSkill
- build-climate-macroSkill
- build-deep-forecasterSkill
- build-drl-policySkill
- build-dsgeSkill
- build-financial-programmingSkill
- build-fpasSkill
- build-game-modelSkill
- build-hankSkill
- build-io-samSkill
- build-llm-agentsSkill
- build-llm-pipelineSkill
- build-multicountrySkill
- build-neural-solverSkill
- build-rag-kbSkill
- build-semi-structuralSkill
- build-sfcSkill
- build-trade-modelSkill
- calibrate-modelSkill
- calibration-planSkill
- carbon-pricing-analysisSkill
- chart-packSkill
- climate-scenarioSkill
- code-inventorySkill
- code-reviewSkill
- country-typologySkill
- create-exerciseSkill
- data-requirementsSkill
- debt-decompositionSkill
- debt-sustainabilitySkill
- design-trainingSkill
- distributional-analysisSkill
- equivalence-testSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
10 rules. About 0 are common, 7 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 27
If a required input is ABSENT, that part is NOT ASSESSED — NO DATA: do not estimate or invent it.
- Very specific: line 29
Collaboration: Follow .claude/docs/collaboration-protocol.md: ask questions first, present options, get approval before writing files, and …
- Distinctive: line 54
Write the closure rules and justify each for the horizon
- Very specific: line 56
Check SAM balance first (/build-io-sam if the SAM must be built)
- Distinctive: line 59
Test homogeneity, Walras' law and numeraire invariance
- Distinctive: line 60
Run policy scenarios under at least two closures.
- Distinctive: line 61
Use quadrature or Monte Carlo over elasticity ranges.
- Distinctive: line 68
After the structure note: confirm sectors, households and closures
- Distinctive: line 69
After benchmark replication: confirm the elasticity table and its ranges
- Distinctive: line 70
After first scenarios: confirm the results are interpretable before sensitivity runs
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
<!-- Generated from .claude/skills/build-cge/SKILL.md by tools/sync_agents.py. Edit the source, then run the script. -->/build-cge — Build CGE
Category: Build · Primary agent: cge-modeling-specialist
Builds a CGE model (static or recursive-dynamic, single- or multi-region) with benchmark replication, closures, elasticity sensitivity and welfare decomposition.
Arguments: whatever the user wrote after the command name.
Purpose
Build a computable general equilibrium model that replicates its benchmark data exactly, solves reliably, and traces how a policy reallocates production, factors and income across sectors and households. The output is a documented model whose results can be decomposed and defended, with closures and elasticities shown to matter or not.
Use it when the question involves economy-wide reallocation through prices: tax and tariff reform, carbon pricing, subsidy reform, productivity shocks by sector, trade agreements with sectoral detail, structural change over decades.
Do not use it when fixed-coefficient multipliers suffice (/build-io-sam), when short-run dynamics with nominal rigidities are central (/build-dsge, /build-semi-structural), or when bilateral trade flows and gravity are the main focus (/build-trade-model).
Before you start
- Check required inputs. For each input below record
FOUNDorABSENT(never 'assumed'):- Approved model-spec
- Balanced SAM or global database
- Elasticity sources
If a required input is
ABSENT, that part isNOT ASSESSED — NO DATA: do not estimate or invent it; name what is missing and which skill produces it. If all required inputs are absent, stop and say so.
- Check confidentiality. Identify the data classification level of the inputs (
.claude/docs/confidentiality-and-ai-use.md). Do not proceed with restricted or confidential data in a way the policy does not allow. - Collaboration. Follow
.claude/docs/collaboration-protocol.md: ask questions first, present options, get approval before writing files, and updateproduction/session-state/active.mdafter each approved section.
Agents
cge-modeling-specialist— primary agent; coordinates the work and integrates resultsinput-output-sam-specialist— Builds input-output, supply-use and social accounting matrix frameworkstrade-policy-simulation-specialist— Simulates trade policy with quantitative trade modelstax-benefit-microsimulation-specialist— Builds tax-benefit microsimulationcarbon-pricing-emissions-specialist— Analyzes carbon pricing and emissions policy
Each agent is defined in .claude/agents/<name>.md. If your tool runs subagents, run these agents as subagents, in parallel where the steps are independent; otherwise read each agent's file and apply its instructions in turn. Subagents only write to the paths named in your instructions.
Key design decisions (present options, let the user choose)
| Decision | Typical options | What it changes |
| Time | static, recursive-dynamic, forward-looking | Adjustment paths; investment behavior |
| Regions | single country, multi-region (global database) | Terms-of-trade effects; data needs |
| Production nests | CES value added and intermediates; energy nests; Leontief intermediates | Substitution possibilities |
| Trade | Armington with CET exports; small or large country | Import and export responses; terms of trade |
| Households | one or many groups from the SAM; LES or other demand systems | Distributional detail |
| Closures | savings–investment, government, external, factor markets, numeraire | Results can change sign across closures |
| GTAP route (multi-region) | GEMPACK with the standard GTAP model, GAMS (for example GTAPinGAMS) | Solution method, decompositions, license needs |
Workflow
- Agree the structure: regions, sectors, factors, production nests, trade treatment and closures
- Map the policy question to the sectors, factors and households that must be separate
- Write the closure rules and justify each for the horizon
- Calibrate to the SAM; implement as a complementarity problem; replicate the benchmark exactly
- Check SAM balance first (
/build-io-samif the SAM must be built) - Source every elasticity with its sector definition and horizon
- For a GTAP model: keep the aggregation mapping, record the database version and license, keep the database out of git, and follow
.claude/rules/gempack-code.mdfor GEMPACK
- Check SAM balance first (
- Test homogeneity, Walras' law and numeraire invariance
- Run policy scenarios under at least two closures; run systematic sensitivity on key elasticities
- Use quadrature or Monte Carlo over elasticity ranges; report the spread
- Report sectoral, welfare (EV/CV) and, where possible, household effects; document the model for handover
- Decompose welfare into allocative, terms-of-trade and endowment effects
- Link to microsimulation for household detail (
/distributional-analysis)
- Register the model as a lego set (
/lego-map): a baseplate plus bricks with declared studs (variables, units, timing) and stubs, so components can later be attached, detached or swapped
Checkpoints with the user
- After the structure note: confirm sectors, households and closures
- After benchmark replication: confirm the elasticity table and its ranges
- After first scenarios: confirm the results are interpretable before sensitivity runs
Common pitfalls
- Results driven by an unexamined closure
- Elasticities borrowed from different aggregations or horizons
- Reporting GDP as welfare
- Treating static results as an adjustment path
- Committing or sharing a licensed global database (GTAP)
Output
models/cge/<name>/ (+ model.lego.json)
The folder holds the SAM, calibration scripts, model code, the replication test, scenario and sensitivity scripts, the elasticity table with sources, the results pack with welfare decomposition and the lego manifest. Every run saves its results to output/<run-id>/ in the model folder, with a run log (.claude/rules/model-code.md).
Gate / verdict
- Benchmark replicated to tolerance
- Closure and elasticity sensitivity reported
- Lego manifest passes
python tools/lego.py check - Homogeneity and Walras' law tests pass
- Welfare is reported as EV or CV with its decomposition
Suggested next steps
/trade-policy-analysis/carbon-pricing-analysis/distributional-analysis/validate-model/lego-map
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

