Causal Inference logo

Causal Inference

CommunityPopular
brycewang-stanford
causal-inference

This skill covers causal inference methods in observational and quasi-experimental settings. Use when the user is implementing, choosing between, or debugging causal identification strategies — including instrumental variables, difference-in-differences, regression discontinuity, synthetic control, or matching estimators. Triggers on "causal effect", "identification strategy", "instrumental variable", "2SLS", "GMM", "difference-in-differences", "DiD", "staggered treatment", "regression discontinuity", "RDD", "synthetic control", "matching", "propensity score", "IPW", "AIPW", "doubly robust", "LATE", "ATT", "ATE", "parallel trends", "exclusion restriction", "first stage", "weak instruments", or "endogeneity".

Overview

Publisherbrycewang-stanford
RepositoryAuto-Empirical-Research-Skills
Skill namecausal-inference
Stars
3.8K
Forks
479
Bundled files
3
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 3 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by brycewang-stanford on GitHub. Read the source before you install it.

Installation

Install the Causal Inference AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/brycewang-stanford/Auto-Empirical-Research-Skills.git /tmp/Auto-Empirical-Research-Skills
mkdir -p .claude/skills
cp -r /tmp/Auto-Empirical-Research-Skills/skills/11-James-Traina-compound-science/skills/causal-inference .claude/skills/causal-inference
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Causal Inference in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Causal Inference on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Causal Inference is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Causal Inference

Reference for implementing causal inference methods: from identification strategy to estimation to diagnostics and robustness. Covers the major quasi-experimental and observational methods used in applied economics and quantitative social science.

When to Use This Skill

Use when the user is:

  • Choosing an identification strategy for a causal question
  • Implementing IV/2SLS, DiD, RDD, synthetic control, or matching
  • Debugging specification issues (weak instruments, parallel trends violations, bandwidth sensitivity)
  • Running robustness checks or falsification tests
  • Working with modern DiD methods for staggered treatment timing

Skip when:

  • The task is structural estimation (use structural-modeling skill)
  • The task is pure prediction/ML (no causal question)
  • The user needs simulation design (use numerical-auditor agent)

Where to Start

  • Choosing a method? Jump to Method Selection Guide at the end
  • Implementing a specific method? Go directly to that method's section below
  • Need full code? See references/method-implementations.md for complete implementations

Frameworks

Two complementary frameworks underpin all causal inference:

Potential Outcomes (Rubin): Define Y(1), Y(0) as potential outcomes under treatment and control. The causal effect is τ = Y(1) - Y(0). The fundamental problem: we never observe both for the same unit. All methods are strategies for constructing valid counterfactuals.

DAGs (Pearl): Graphical models encoding conditional independence assumptions. Use d-separation to determine what must be conditioned on (and what must NOT be conditioned on) to identify causal effects. Particularly useful for reasoning about bad controls (colliders, mediators), overcontrol bias, and which instruments satisfy the exclusion restriction.

Quick Reference: Methods at a Glance

MethodKey AssumptionTarget ParameterKey Package
IV/2SLSExclusion restriction, monotonicityLATElinearmodels (Py), fixest (R), ivregress (Stata)
DiDParallel trendsATTfixest (R), reghdfe (Stata), linearmodels (Py)
RDDNo manipulation, local continuityLATE at cutoffrdrobust (all)
Synthetic ControlWeights reproduce pre-treatment trendsATT (single unit)Synth/augsynth (R)
Matching/AIPWSelection on observablesATE or ATTeconml (Py), MatchIt/WeightIt (R)

Target Parameters

Be precise about what parameter you are estimating:

ParameterDefinitionEstimated by
ATEE[Y(1) - Y(0)]Randomized experiment, IPW, AIPW
ATTE[Y(1) - Y(0) | D=1]DiD, matching, selection-on-observables
LATEE[Y(1) - Y(0) | compliers]IV/2SLS (Imbens-Angrist 1994)
ATT(g,t)Group-time specific treatment effectStaggered DiD (Callaway-Sant'Anna)

Common mistake: IV estimates LATE, not ATE. DiD estimates ATT, not ATE. This matters for policy interpretation.

Instrumental Variables (IV/2SLS)

Key idea: Find a variable Z that shifts D (first stage) but affects Y only through D (exclusion restriction).

python
from linearmodels.iv import IV2SLS

result = IV2SLS.from_formula(
    'lwage ~ 1 + exper + expersq + [educ ~ nearc4 + nearc2]',
    data=df
).fit(cov_type='robust')

# Always check first-stage F > 10; report LIML as robustness with weak instruments

For R/Stata implementations, weak instrument corrections (LIML, Anderson-Rubin), and overidentification tests, see references/method-implementations.md.

IV Diagnostics Checklist:

  • First-stage F > 10 (or Olea-Pflueger effective F for robust inference)
  • Exclusion restriction argued substantively (not testable)
  • Monotonicity for LATE interpretation (no defiers)
  • Reduced form significant (regress Y directly on Z)
  • Overidentification test reported if over-identified
  • Compare OLS vs 2SLS — direction and magnitude as expected?
  • Report LATE interpretation — who are the compliers?

Difference-in-Differences (DiD)

Key idea: Compare changes over time between treated and control groups, assuming they would have followed parallel trends absent treatment.

python
import statsmodels.formula.api as smf

# Standard 2x2 DiD
result = smf.ols('y ~ treated + post + treated:post', data=df).fit(
    cov_type='cluster', cov_kwds={'groups': df['state']}
)
# Coefficient on treated:post is the DiD estimate

Staggered treatment timing: With staggered adoption, TWFE can produce sign-reversed estimates due to negative weights. Use:

  • Callaway-Sant'Anna (did R package): Most flexible aggregation, doubly robust
  • Sun-Abraham (fixest::sunab): Integrates directly into feols; simpler for event studies
  • Bacon decomposition (bacondecomp R): Diagnose how much weight TWFE puts on contaminated comparisons

For full staggered DiD code (C-SA, Sun-Abraham, BJS24, de Chaisemartin-D'H), see references/staggered-did.md. For event study code and HonestDiD pre-trend sensitivity, see references/method-implementations.md.

DiD Diagnostics Checklist:

  • Pre-trends: Event study shows no significant pre-treatment coefficients
  • Parallel trends sensitivity: Rambachan-Roth or similar analysis
  • Staggered timing: If varies, use C-SA or S-A — NOT naive TWFE
  • Clustering at level of treatment assignment (typically state/county)
  • Anticipation: Check period just before treatment
  • Bacon decomposition if using TWFE

Regression Discontinuity (RDD)

Key idea: Units just above and below a threshold are locally comparable; the jump at the threshold identifies the causal effect.

python
from rdrobust import rdrobust, rdbwselect, rdplot

# Basic sharp RD with bias-corrected robust CI
result = rdrobust(y=df['outcome'], x=df['running_var'], c=0)
# Reports: point estimate, robust CI, MSE-optimal bandwidth, N left/right

# Density test for manipulation
from rddensity import rddensity
density_test = rddensity(X=df['running_var'], c=0)

For fuzzy RDD, bandwidth sensitivity tables, and R/Stata implementations, see references/method-implementations.md.

RDD Diagnostics Checklist:

  • McCrary density test: No manipulation of running variable at cutoff
  • Covariate balance: Run RD on predetermined covariates as placebo outcomes
  • Bandwidth sensitivity: Results stable across 0.5×, 0.75×, 1×, 1.5×, 2× optimal
  • Local linear (p=1) is standard — avoid high-order polynomials
  • Donut hole: Drop observations very close to cutoff
  • Placebo cutoffs: Run RD where no effect should exist

Synthetic Control

When to use: Single or very few treated units, long pre-treatment series, no obvious comparison group. SC constructs a synthetic counterfactual as a weighted average of donor units.

Key packages: R: Synth, tidysynth, augsynth; Python: SparseSC, SyntheticControlMethods

Diagnostics: Pre-treatment RMSPE (fit quality), permutation/placebo tests across donor units, leave-one-out stability, time placebo at earlier date.

For full implementation (Synth setup, augsynth, permutation tests), see references/synthetic-control.md and references/method-implementations.md. The identification-critic agent can evaluate SC identification assumptions.

Matching and Weighting

Key idea: Reweight control group to match treated group on observed characteristics. Only valid under selection-on-observables (no unobserved confounders).

AIPW (doubly robust) is the recommended default — consistent if either the propensity score model or the outcome model is correctly specified.

python
from econml.dr import LinearDRLearner
from sklearn.ensemble import GradientBoostingRegressor, GradientBoostingClassifier

# Doubly robust learner
dr = LinearDRLearner(
    model_regression=GradientBoostingRegressor(),
    model_propensity=GradientBoostingClassifier()
)
dr.fit(Y=df['y'], T=df['treatment'], X=df[covariates], W=None)
ate = dr.ate(df[covariates])

For propensity score estimation, IPW/Hajek estimators, and manual AIPW implementation, see references/method-implementations.md.

Matching Diagnostics Checklist:

  • Covariate balance: Standardized mean differences < 0.1 after weighting
  • Common support: Substantial overlap in propensity score distributions
  • Sensitivity analysis: Rosenbaum bounds
  • No post-treatment covariates in the propensity model
  • Trim if propensity scores near 0 or 1

Method Selection Guide

ScenarioRecommended MethodKey Assumption
Random assignment with imperfect complianceIV/2SLSExclusion restriction, monotonicity
Policy change at a thresholdRDDNo manipulation, local continuity
Policy change at a time point, treated and control groupsDiDParallel trends
Staggered policy adoption across unitsStaggered DiD (C-SA, S-A)Parallel trends (conditional)
Single treated unit, long pre-periodSynthetic controlWeights reproduce pre-treatment
Treatment assignment based on observablesMatching/IPW/AIPWSelection on observables

Decision heuristic:

  1. Is there a sharp threshold? → RDD
  2. Is there an instrument? → IV
  3. Is there a clean pre/post + treated/control? → DiD
  4. Only one treated unit? → Synthetic control
  5. Rich observables, selection on observables plausible? → AIPW
  6. None of the above → structural model may be needed

Common Anti-Patterns

Anti-PatternProblemBetter Approach
TWFE with staggered timing and heterogeneous effectsNegative weights, biased estimatesUse Callaway-Sant'Anna or Sun-Abraham
Reporting 2SLS without first-stage FReader cannot assess instrument strengthAlways report first-stage F (and LIML as robustness)
High-order polynomial in RDDOverfitting, poor boundary propertiesUse local linear (p=1) with rdrobust
Matching on post-treatment variablesConditioning on outcome of treatmentOnly match on pre-treatment covariates
Claiming parallel trends hold because pre-event coefficients are insignificantLow power; absence of evidence ≠ evidence of absenceUse Rambachan-Roth sensitivity analysis
IPW with extreme propensity scores (near 0 or 1)Huge variance, unstable estimatesTrim, use normalized/Hajek weights, or switch to AIPW
Reporting only one bandwidth in RDDCherry-picking concernShow results across bandwidth range
Cluster-robust SEs with few clusters (< 30-40)Poor finite-sample coverageWild cluster bootstrap (Cameron, Gelbach, Miller 2008)

Integration with compound-science

  • econometric-reviewer — Reviews identification strategy, standard errors, and asymptotic properties
  • identification-critic — Evaluates exclusion restrictions, support conditions, and identification completeness
  • identification-critic agent / identification-proofs skill — Formalize an identification argument end-to-end
  • /estimate — Run a full estimation pipeline with diagnostics
  • empirical-playbook skill (sensitivity-analysis.md) — Oster bounds, specification curve, breakdown frontier for robustness

Additional References

  • references/method-implementations.md — Full IV/2SLS, DiD event study, RDD, and matching/AIPW implementation code
  • references/staggered-did.md — Full implementation code for Callaway-Sant'Anna, Sun-Abraham, BJS24, de Chaisemartin-D'Haultfoeuille, and Bacon decomposition
  • references/synthetic-control.md — Standard SC optimizer, permutation/placebo test code, augmented SC, diagnostics checklist

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Causal Inference AI skill do?

This skill covers causal inference methods in observational and quasi-experimental settings. Use when the user is implementing, choosing between, or debugging causal identification strategies — including instrumental variables, difference-in-differences, regression discontinuity, synthetic control, or matching estimators. Triggers on "causal effect", "identification strategy", "instrumental variable", "2SLS", "GMM", "difference-in-differences", "DiD", "staggered treatment", "regression discontinuity", "RDD", "synthetic control", "matching", "propensity score", "IPW", "AIPW", "doubly robust"...

Why use Causal Inference on TypingMind?

Because you install it once and use it with any model. Causal Inference is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Causal Inference in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/brycewang-stanford/Auto-Empirical-Research-Skills/tree/main/skills/11-James-Traina-compound-science/skills/causal-inference. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Causal Inference?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Causal Inference?

As many as you like. As long as a model supports skills, you can use Causal Inference with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Causal Inference AI skill free?

It is published on GitHub by brycewang-stanford. Check the repository for licensing terms. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇