build-causal-ml
Skill4 starsChanged 6 days agoMITView on GitHub
Builds a causal machine-learning analysis (double ML, causal forests) with identification argument and sensitivity 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-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
- 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
9 rules. About 0 are common, 7 are distinctive, and 2 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.
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 47
Write the identification argument and assumptions before touching the data
- Distinctive: line 50
Check overlap; trim if needed and report what was trimmed
- Distinctive: line 53
Run sensitivity to unobserved confounding and specification
- Distinctive: line 54
Write the result in terms of what the evidence supports and what it does not
- Distinctive: line 58
After the identification note: confirm assumptions are acceptable
- Distinctive: line 59
After the main estimate: confirm the estimand before heterogeneity work
- Distinctive: line 60
Before reporting heterogeneity: confirm which subgroups are policy-relevant
≈ “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-causal-ml/SKILL.md by tools/sync_agents.py. Edit the source, then run the script. -->/build-causal-ml — Build Causal ML
Category: Build (AI) · Primary agent: causal-ml-specialist
Builds a causal machine-learning analysis (double ML, causal forests) with identification argument and sensitivity checks.
Arguments: whatever the user wrote after the command name.
Purpose
Build a causal machine-learning analysis that estimates treatment effects, and how they vary across units, with double/debiased ML or causal forests, while keeping identification explicit. The output is an estimate whose identifying assumptions are written down before estimation, compared with a conventional econometric estimate, and tested for sensitivity to unobserved confounding.
Use it when there are many potential controls, heterogeneity of effects matters for targeting, or flexible functional forms are needed for nuisance functions in an otherwise well-identified design.
Do not use it when there is no credible identification strategy (ML will not create one), or a standard panel or quasi-experimental design answers the question directly (/local-projections, /policy-simulation).
Before you start
- Check required inputs. For each input below record
FOUNDorABSENT(never 'assumed'):- Data sheet
- Identification argument
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
causal-ml-specialist— primary agent; coordinates the work and integrates resultspanel-causal-inference-specialist— Panel econometrics and causal inferenceinterpretable-ml-specialist— Makes AI models explainable
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 |
| Identification | selection on observables, IV, difference-in-differences with ML controls | Credibility of the estimate |
| Estimand | ATE, ATT, CATE, policy value | What is reported |
| Learners | lasso, random forests, boosting, neural networks, ensembles | Nuisance-function quality |
| Heterogeneity method | causal forests, best linear predictor, sorted group effects | Reliability of subgroup findings |
| Sensitivity | omitted-variable-bias bounds, placebo tests | Robustness statement |
Workflow
- Write the identification argument and assumptions before touching the data
- Draw the causal diagram; list confounders and why unobserved ones are unlikely to matter
- Implement with cross-fitting; compare to a standard econometric estimate
- Check overlap; trim if needed and report what was trimmed
- Estimate heterogeneous effects and test stability
- Validate heterogeneity on held-out data; avoid data-mined subgroups
- Run sensitivity to unobserved confounding and specification
- Write the result in terms of what the evidence supports and what it does not
- 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 identification note: confirm assumptions are acceptable
- After the main estimate: confirm the estimand before heterogeneity work
- Before reporting heterogeneity: confirm which subgroups are policy-relevant
Common pitfalls
- ML flexibility presented as identification
- No cross-fitting
- Poor overlap ignored
- Heterogeneity found by search reported as fact
Output
models/ai/<name>-causal/ (+ model.lego.json)
The folder holds the identification note, estimation code with cross-fitting, overlap diagnostics, heterogeneity analysis, sensitivity results 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
- Identification assumptions stated
- Comparison with a conventional estimate
- Sensitivity analysis present
- Lego manifest passes
python tools/lego.py check - Cross-fitting and overlap diagnostics are documented
- Heterogeneity results are validated out of sample
Suggested next steps
/validate-model/technical-note/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.

