calibrate-model
Skill4 starsChanged 6 days agoMITView on GitHub
Calibrates a model to targets: moments, micro evidence and published estimates, with sensitivity of targets to parameters.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- playcanvas/skillstheir own version, first seen Oct 12, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- playcanvas/skills★ 43same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
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
- 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
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 26
If a required input is ABSENT, that part is NOT ASSESSED — NO DATA: do not estimate or invent it.
- Very specific: line 28
Collaboration: Follow .claude/docs/collaboration-protocol.md: ask questions first, present options, get approval before writing files, and …
- Distinctive: line 56
After target moments: confirm the sample and targets
- Distinctive: line 57
After matching: review weakly pinned parameters and their assumptions
≈ “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/calibrate-model/SKILL.md by tools/sync_agents.py. Edit the source, then run the script. -->/calibrate-model — Calibrate Model
Category: Estimation · Primary agent: bayesian-dsge-estimation-specialist
Calibrates a model to targets: moments, micro evidence and published estimates, with sensitivity of targets to parameters.
Arguments: whatever the user wrote after the command name.
Purpose
Calibrate a model's parameters to data moments, micro evidence and published estimates in a way that is transparent and testable: every parameter has a source, the mapping from targets to parameters is understood, and the model is judged on moments it was not calibrated to match. The output is a calibration sheet that a reviewer can audit line by line.
Use it when a model is not estimated (or only partly), when estimation is weakly informative, or when steady-state ratios must match national accounts.
Do not use it when full-information estimation is feasible and planned (/estimate-dsge), or when the parameter plan itself has not been agreed (/calibration-plan).
Before you start
- Check required inputs. For each input below record
FOUNDorABSENT(never 'assumed'):- Calibration plan
- Target data
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
bayesian-dsge-estimation-specialist— primary agent; coordinates the work and integrates resultsemde-lic-dsge-specialist— Adapts structural models to emerging, developing and low-income economiessensitivity-uncertainty-specialist— Quantifies uncertainty and sensitivity
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 |
| Target sample | full sample, recent regime, excluding crises | Steady-state ratios and volatilities |
| Method | exact matching, minimum distance with weights | Fit versus robustness |
| Micro evidence | household and firm studies, meta-analyses | Discipline on behavioral parameters |
| Untargeted checks | second moments, IRFs from VARs, distributional facts | Validation strength |
Workflow
- Compute target moments from data with the data's uncertainty
- Bootstrap or HAC standard errors for moments; note sample choices
- Choose parameters by matching or by minimum distance
- Assess which parameters are pinned down by which targets
- Jacobian of moments with respect to parameters; flag weakly pinned parameters
- Record the calibration sheet with sources
- Value, source, target, sensitivity for each parameter; label assumptions
- Report moment fit and untargeted moments
Checkpoints with the user
- After target moments: confirm the sample and targets
- After matching: review weakly pinned parameters and their assumptions
Common pitfalls
- Targets from a non-representative period without saying so
- Parameters borrowed from studies of different economies or horizons
- Claiming fit on targeted moments as validation
- Many parameters loosely pinned by few targets
Output
docs/models/<name>/calibration-sheet.md; calibration code in models/<family>/<name>/
The calibration sheet lists every parameter with value, source, target and sensitivity, and reports targeted and untargeted fit. Every run saves its results to output/<run-id>/ in the model folder, with a run log (.claude/rules/model-code.md).
Gate / verdict
- Untargeted moments reported
- Every parameter sourced
- Weakly pinned parameters are flagged with sensitivity results
- Target-sample choices are documented
Suggested next steps
/validate-model/sensitivity-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.

