build-climate-macro
Skill4 starsChanged 6 days agoMITView on GitHub
Builds a climate-macro model: climate-augmented macro or integrated-assessment-style model with damage functions, abatement and carbon pricing.
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-cgeSkill
- 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
6 rules. About 0 are common, 4 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
2
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 56
Run baseline and policy pathways.
- Distinctive: line 63
After choosing the structure: confirm the horizon and questions
- Distinctive: line 64
After specifying damages and discounting: confirm which alternatives to report
- Distinctive: line 65
After baseline calibration: confirm the emissions baseline
≈ “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-climate-macro/SKILL.md by tools/sync_agents.py. Edit the source, then run the script. -->/build-climate-macro — Build Climate Macro
Category: Build · Primary agent: climate-macro-specialist
Builds a climate-macro model: climate-augmented macro or integrated-assessment-style model with damage functions, abatement and carbon pricing.
Arguments: whatever the user wrote after the command name.
Purpose
Build a model that connects climate and the macroeconomy: emissions from economic activity, damages from warming, abatement and its costs, carbon pricing and its revenue, and adaptation. The output is a model whose normative choices (damages, discounting) are explicit and varied, and whose results are presented as ranges that reflect deep uncertainty.
Use it when the question involves carbon pricing paths, the social cost of carbon, long-run damages, transition dynamics, or the macro and fiscal implications of climate scenarios.
Do not use it when the question is a near-term carbon-tax incidence or revenue estimate (/carbon-pricing-analysis), a scenario translation into an existing macro model (/climate-scenario), or sector-level detail without macro feedback (/build-io-sam).
Before you start
- Check required inputs. For each input below record
FOUNDorABSENT(never 'assumed'):- Approved model-spec
- Emissions and energy data
- Damage-function evidence
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
climate-macro-specialist— primary agent; coordinates the work and integrates resultscarbon-pricing-emissions-specialist— Analyzes carbon pricing and emissions policyphysical-climate-risk-specialist— Quantifies physical climate risktransition-risk-energy-specialist— Analyzes energy systems and transition riskeconomic-reasoning-specialist— Frames the economic question and tests whether results make economic sense
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 |
| Model family | climate-augmented DSGE, IAM (DICE-type), multi-sector, CGE-linked | Horizon, policy detail, uncertainty treatment |
| Damage function | quadratic level damages, growth damages, empirically estimated nonlinear, tipping points | Size and timing of losses |
| Discounting | Ramsey parameters, declining rates, descriptive versus prescriptive | Present value of damages and optimal carbon price |
| Energy detail | aggregate emissions intensity, energy nest, explicit technologies | Abatement costs and transition dynamics |
| Uncertainty | deterministic scenarios, Monte Carlo over parameters, robust decision | How uncertainty is reported |
Workflow
- Choose the structure (climate-augmented DSGE, IAM-style, multi-sector, CGE-linked) with the user
- Match the horizon and policy question to the family; state what the model cannot answer
- Specify emissions, abatement, damage and (if relevant) adaptation blocks; document discounting and damage-function choices
- Label normative choices as such; keep alternatives ready to run
- Calibrate and test the model against historical emissions and energy intensity
- Reconcile with national inventories and energy balances
- Run baseline and policy pathways; test sensitivity to damages, discounting and technology costs
- Include orderly and delayed transition paths where relevant
- Report deep uncertainty as ranges and document limitations
- Show results across damage functions and discount rates side by side
- 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 choosing the structure: confirm the horizon and questions
- After specifying damages and discounting: confirm which alternatives to report
- After baseline calibration: confirm the emissions baseline
Common pitfalls
- A single damage function presented as fact
- Discount rates chosen without stating their normative basis
- Technology-cost assumptions anchored on outdated estimates
- Mixing scenario sources with incompatible assumptions
Output
models/climate/<name>/ (+ model.lego.json)
The folder holds model code, calibration and emissions-baseline files, scenario scripts, the sensitivity pack across damages, discounting and technology costs, the limitations note 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
- Damage-function and discount-rate alternatives shown
- Emissions accounting consistent with the baseline
- Lego manifest passes
python tools/lego.py check - Normative choices are labeled and alternatives reported side by side
- Results are presented as ranges, not single paths
Suggested next steps
/climate-scenario/carbon-pricing-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.

