carbon-pricing-analysis
Skill4 starsChanged 6 days agoMITView on GitHub
Analyzes carbon pricing and emissions policy: tax or trading design, border adjustment, revenue recycling, competitiveness and distributional effects.
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-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
- 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
4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
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 61
After the design: confirm price path, coverage and revenue options to compare
- Distinctive: line 62
After first results: confirm which compensation options to cost
≈ “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/carbon-pricing-analysis/SKILL.md by tools/sync_agents.py. Edit the source, then run the script. -->/carbon-pricing-analysis — Carbon Pricing Analysis
Category: Analysis · Primary agent: carbon-pricing-emissions-specialist
Analyzes carbon pricing and emissions policy: tax or trading design, border adjustment, revenue recycling, competitiveness and distributional effects.
Arguments: whatever the user wrote after the command name.
Purpose
Analyze a carbon tax, emissions trading system or related measure end to end: emissions and economic effects, public revenue and its use, competitiveness and leakage, border adjustments, and who bears the cost. The output is an assessment that shows trade-offs across design options and states how much the conclusions depend on models, closures and elasticities.
Use it when a government or analyst is designing, reforming or evaluating carbon pricing, fossil-fuel subsidy reform, or a border carbon adjustment.
Do not use it when long-run damages and optimal carbon paths are the question (/build-climate-macro), or macro scenario translation is needed (/climate-scenario).
Before you start
- Check required inputs. For each input below record
FOUNDorABSENT(never 'assumed'):- Emissions baseline
- Approved CGE, IO or macro model
- Household data for incidence (optional)
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
carbon-pricing-emissions-specialist— primary agent; coordinates the work and integrates resultscge-modeling-specialist— Builds computable general equilibrium modelsclimate-macro-specialist— Models climate and macrotax-benefit-microsimulation-specialist— Builds tax-benefit microsimulationtrade-policy-simulation-specialist— Simulates trade policy with quantitative trade modelsinput-output-sam-specialist— Builds input-output, supply-use and social accounting matrix frameworks
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 |
| Instrument | tax, trading with price floor/ceiling, feebates, standards | Price certainty versus quantity certainty |
| Coverage | power and industry, transport and buildings, economy-wide | Emissions and incidence |
| Revenue use | lump-sum transfers, labor-tax cuts, targeted support, investment, deficit reduction | Efficiency and progressivity |
| Trade treatment | free allocation, output-based rebates, border adjustment | Leakage and competitiveness |
| Models | IO price model, CGE, macro model, microsimulation | Coverage of channels |
Workflow
- Define the policy design: instrument, price path, coverage, revenue use and border treatment
- Build the emissions baseline with documented accounting conventions
- Compute emissions, output, price and fiscal effects with at least two models or closures
- Analyze competitiveness, leakage and border-adjustment effects
- Identify emissions-intensive trade-exposed sectors
- Estimate distributional incidence and compensation options
- Direct (fuel) and indirect (goods) effects by decile and region; cost of compensation
- Report trade-offs with uncertainty and the dependence on assumptions
Checkpoints with the user
- After the design: confirm price path, coverage and revenue options to compare
- After first results: confirm which compensation options to cost
Common pitfalls
- Mixing production- and consumption-based emissions
- Incidence reported without offsetting transfers
- Ignoring interactions with existing energy taxes and subsidies
- Overstating leakage
Output
forecasts/climate/<name>-carbon-pricing.md
The report covers the design, emissions baseline, economic and fiscal effects, competitiveness and leakage, distributional incidence with compensation, and sensitivity to models and elasticities.
Gate / verdict
- Revenue recycling variants shown
- Distributional effects reported
- Emissions accounting conventions are documented
- Results are shown for at least two models or closures
Suggested next steps
/policy-brief/distributional-analysis
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.

