calibration-plan
Skill4 starsChanged 6 days agoMITView on GitHub
Plans calibration and estimation: parameter sources, priors, moments, targets, identification checks.
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
- 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
7 rules. About 0 are common, 5 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
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 25
If a required input is ABSENT, that part is NOT ASSESSED — NO DATA: do not estimate or invent it.
- Very specific: line 27
Collaboration: Follow .claude/docs/collaboration-protocol.md: ask questions first, present options, get approval before writing files, and …
- Distinctive: line 47
Prefer evidence from comparable economies and periods
- Distinctive: line 53
After classification: confirm the split
- Distinctive: line 54
After priors: confirm their rationale
- Distinctive: line 59
No plan for parameters the data cannot identify
- Distinctive: line 67
Every parameter has a classification and a source or prior
≈ “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/calibration-plan/SKILL.md by tools/sync_agents.py. Edit the source, then run the script. -->/calibration-plan — Calibration Plan
Category: Scoping & Design · Primary agent: bayesian-dsge-estimation-specialist
Plans calibration and estimation: parameter sources, priors, moments, targets, identification checks.
Arguments: whatever the user wrote after the command name.
Purpose
Plan, before any code is run, how each parameter of a model will be set: calibrated to data, estimated with a stated prior, or fixed at a literature value, with the source and the identification checks that will be used. The output is a plan that prevents ad hoc tuning later and tells reviewers in advance what will count as evidence.
Use it when a model specification is agreed and the team is about to calibrate or estimate it.
Do not use it when the calibration is already done and needs documenting (/calibrate-model) or estimation is in progress (/estimate-dsge).
Before you start
- Check required inputs. For each input below record
FOUNDorABSENT(never 'assumed'):- docs/models/
<name>/model-spec.md If a required input isABSENT, 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.
- docs/models/
- 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
bayesian-dsge-estimation-specialist— primary agent; coordinates the work and integrates resultsemde-lic-dsge-specialist— Adapts structural models to emerging, developing and low-income economiesvar-vecm-specialist— Builds VAR, SVAR and VECM models
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 |
| Split | which parameters to calibrate, estimate or fix | Data requirements and identification |
| Prior families | beta, gamma, inverse gamma, normal; endogenous priors | What data must override |
| Targets | steady-state ratios, second moments, IRF matching | Discipline on dynamics |
| Identification checks | local identification, prior–posterior overlap, simulation recovery | Credibility |
Workflow
- Classify parameters: calibrate, estimate, or fix at literature values
- Source each calibrated value (data moment, micro study, published estimate)
- Prefer evidence from comparable economies and periods
- Specify priors with rationale; plan prior predictive checks
- List calibration targets and the identification diagnostics to run
- Include a simulation–recovery exercise for estimated parameters
Checkpoints with the user
- After classification: confirm the split
- After priors: confirm their rationale
Common pitfalls
- Priors chosen to deliver expected results
- Literature values from different contexts used without comment
- No plan for parameters the data cannot identify
Output
docs/models/<name>/calibration-plan.md
The plan lists every parameter with its treatment, source or prior with rationale, targets, and the identification diagnostics to run.
Gate / verdict
- Every parameter has a classification and a source or prior
- Identification diagnostics are listed for every estimated parameter
Suggested next steps
/estimate-dsge/calibrate-model
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.

