/aeri-identification
Use when the identification argument is the bottleneck for an American Economic Review: Insights (AER: Insights) short-format manuscript — causal identification in an empirical design, parameter identification in a structural model, or treatment-effect identification in an
$ npx -y skills add brycewang-stanford/Awesome-Journal-Skills --skill aeri-identification --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/aeri-identification
Context preview
The summary Claude sees to decide when to auto-load this skill.
Use when the identification argument is the bottleneck for an American Economic Review: Insights (AER: Insights) short-format manuscript — causal identification in an empirical design, parameter identification in a structural model, or treatment-effect identification in an
SKILL.md
aeri-identification.SKILL.mdname: aeri-identification
description: Use when the identification argument is the bottleneck for an American Economic Review: Insights (AER: Insights) short-format manuscript — causal identification in an empirical design, parameter identification in a structural model, or treatment-effect identification in an experiment. Stress-tests the strategy so it is clean enough to defend in a few pages, before exhibits are finalized.
Identification — Clean Enough to Defend Short (aeri-identification)
When to trigger
- The single headline result rests on OLS + controls, or TWFE on staggered timing
- A structural parameter is estimated but it is unclear *what in the data* identifies it
- An experiment's estimand or assumptions are not pinned down
- You are unsure the identification is clean enough to carry a *short* paper
The AER: Insights identification bar
A short paper has **no room to rescue a weak design** with pages of robustness. The identification must be **clean, transparent, and self-contained** — the central exhibit and one or two sentences should make a non-specialist believe the headline number. Because AER: Insights papers are one insight at AER-level importance, the design is held to AER credibility but expressed with extreme economy: state the **data-to-object mapping in one sentence**, show the **single most convincing diagnostic in-text**, and move the rest to the Supplemental Appendix. AEA house style: report **standard errors / confidence sets**, not significance asterisks, and make everything reproducible for the AEA Data Editor.
Branch paths
Branch A: Empirical causal design (the most common AER: Insights paper)
- **DiD / event study:** with staggered adoption move beyond TWFE (Callaway–Sant'Anna, Sun–Abraham, de Chaisemartin–D'Haultfœuille); the **single event-study figure with clean leads** is often the paper's central exhibit.
- **RDD:** density test (Cattaneo–Jansson–Ma), optimal bandwidth, covariate smoothness, bias-corrected CIs; one well-made RD plot can be the whole identification.
- **IV:** strong first stage; weak-IV-robust inference (Anderson–Rubin) if needed; defend the exclusion restriction in one tight paragraph.
- Inference clustered at the assignment level; few-cluster fixes (wild-cluster bootstrap).
Branch B: Experiment (own data)
- Pre-registration in a recognized registry; report deviations.
- Randomization balance, attrition (Lee bounds if differential), pre-specified primary estimand, multiple-hypothesis control if more than one outcome.
- The headline is one pre-registered effect — resist reporting every arm in-text.
Branch C: Structural / parameter identification
- **Name what identifies the key parameter** from a specific data moment, in one sentence — a short paper cannot hide behind "the likelihood."
- Report the sensitivity of the headline parameter to the moment that moves it; Monte Carlo recovery in the appendix.
- Keep the model minimal ([`aeri-theory-model`](../aeri-theory-model/SKILL.md)) — only what the single insight needs.
Branch D: New fact / measurement
- Documented construction; show the fact is not a measurement artifact with the one most threatening alternative addressed in-text, others in the appendix.
Choosing the single in-text diagnostic
You have **at most five exhibits total** and the identification competes with the result for that budget. Pick the **one diagnostic** that most directly defends the design (the event-study leads, the RD plot, the first-stage, the balance table) for in-text; everything else (placebo cuts, alternative bandwidths, all balance rows) goes to the appendix.
Execution bridge (StatsPAI / Stata MCP)
Estimate and audit the identification claim, don't only argue it. Full map: [`execution-with-mcp`](../../../shared-resources/empirical-methods/execution-with-mcp.md). AER: Insights is a short format built around one decisive result, so the body/appendix split is even tighter — run the design cleanly the first time.
1. `detect_design` → `recommend` → fit with `as_handle=true` → `audit_result` to list the checks the design still owes. 2. **Staggered DiD:** `callaway_santanna` / `sun_abraham` + `bacon_decomposition` + `honest_did_from_result` (the pre-trend test is low-power, Roth 2022). 3. **IV:** `effective_f_test` + an `anderson_rubin_ci` (valid under weak instruments), not a 2SLS t-stat alone. 4. **RDD:** `rdrobust` (bias-corrected) + `rddensity` / `mccrary_test` for manipulation. 5. **OVB:** `oster_delta` / `sensemakr` — how strong a confounder would have to be.
Report the economic magnitude; route the full battery to the appendix; keep every number reproducible. A run end-to-end (synthetic data, real returns) is in the [JF execution walkthrough](../../../Journal-of-Finance-Skills/resources/worked-examples/02-execution-walkthrough.md). If StatsPAI/Stata are not connected, adapt the vendored `resources/code/` skeleton and flag any unverified number.
Checklist
- [ ] Branch chosen; **data-to-object mapping stated in one sentence**
- [ ] The single most convincing diagnostic is identified for in-text placement
- [ ] Empirical: modern estimator where TWFE would bias; design diagnostic shown
- [ ] Experiment: pre-registered; primary estimand pre-specified; balance/attrition handled
- [ ] Structural: key parameter tied to an identifying moment; sensitivity reported
- [ ] Inference as SEs / confidence sets (no asterisks); clustering level correct
- [ ] The headline claim never exceeds what the identification supports
Anti-patterns
- Relying on a wall of robustness to compensate for a weak core design (no room for it)
- TWFE on staggered treatment with no heterogeneity-bias discussion
- Reporting every experimental arm/heterogeneity split in-text instead of one estimand
- "The estimator converged" presented as identification (structural)
- Significance asterisks instead of standard errors / confidence sets
Referee pushback mapped to the fix
-
Read more
name: aeri-identification description: Use when the identification argument is the bottleneck for an American Economic Review: Insights (AER: Insights) short-format manuscript — causal identification in an empirical design, parameter identification in a structural model, or treatment-effect identification in an experiment. Stress-tests the strategy so it is clean enough to defend in a few pages, before exhibits are finalized.
Identification — Clean Enough to Defend Short (aeri-identification)
When to trigger
- The single headline result rests on OLS + controls, or TWFE on staggered timing
- A structural parameter is estimated but it is unclear *what in the data* identifies it
- An experiment's estimand or assumptions are not pinned down
- You are unsure the identification is clean enough to carry a *short* paper
The AER: Insights identification bar
A short paper has **no room to rescue a weak design** with pages of robustness. The identification must be **clean, transparent, and self-contained** — the central exhibit and one or two sentences should make a non-specialist believe the headline number. Because AER: Insights papers are one insight at AER-level importance, the design is held to AER credibility but expressed with extreme economy: state the **data-to-object mapping in one sentence**, show the **single most convincing diagnostic in-text**, and move the rest to the Supplemental Appendix. AEA house style: report **standard errors / confidence sets**, not significance asterisks, and make everything reproducible for the AEA Data Editor.
Branch paths
Branch A: Empirical causal design (the most common AER: Insights paper)
- **DiD / event study:** with staggered adoption move beyond TWFE (Callaway–Sant'Anna, Sun–Abraham, de Chaisemartin–D'Haultfœuille); the **single event-study figure with clean leads** is often the paper's central exhibit.
- **RDD:** density test (Cattaneo–Jansson–Ma), optimal bandwidth, covariate smoothness, bias-corrected CIs; one well-made RD plot can be the whole identification.
- **IV:** strong first stage; weak-IV-robust inference (Anderson–Rubin) if needed; defend the exclusion restriction in one tight paragraph.
- Inference clustered at the assignment level; few-cluster fixes (wild-cluster bootstrap).
Branch B: Experiment (own data)
- Pre-registration in a recognized registry; report deviations.
- Randomization balance, attrition (Lee bounds if differential), pre-specified primary estimand, multiple-hypothesis control if more than one outcome.
- The headline is one pre-registered effect — resist reporting every arm in-text.
Branch C: Structural / parameter identification
- **Name what identifies the key parameter** from a specific data moment, in one sentence — a short paper cannot hide behind "the likelihood."
- Report the sensitivity of the headline parameter to the moment that moves it; Monte Carlo recovery in the appendix.
- Keep the model minimal ([`aeri-theory-model`](../aeri-theory-model/SKILL.md)) — only what the single insight needs.
Branch D: New fact / measurement
- Documented construction; show the fact is not a measurement artifact with the one most threatening alternative addressed in-text, others in the appendix.
Choosing the single in-text diagnostic
You have **at most five exhibits total** and the identification competes with the result for that budget. Pick the **one diagnostic** that most directly defends the design (the event-study leads, the RD plot, the first-stage, the balance table) for in-text; everything else (placebo cuts, alternative bandwidths, all balance rows) goes to the appendix.
Execution bridge (StatsPAI / Stata MCP)
Estimate and audit the identification claim, don't only argue it. Full map: [`execution-with-mcp`](../../../shared-resources/empirical-methods/execution-with-mcp.md). AER: Insights is a short format built around one decisive result, so the body/appendix split is even tighter — run the design cleanly the first time.
1. `detect_design` → `recommend` → fit with `as_handle=true` → `audit_result` to list the checks the design still owes. 2. **Staggered DiD:** `callaway_santanna` / `sun_abraham` + `bacon_decomposition` + `honest_did_from_result` (the pre-trend test is low-power, Roth 2022). 3. **IV:** `effective_f_test` + an `anderson_rubin_ci` (valid under weak instruments), not a 2SLS t-stat alone. 4. **RDD:** `rdrobust` (bias-corrected) + `rddensity` / `mccrary_test` for manipulation. 5. **OVB:** `oster_delta` / `sensemakr` — how strong a confounder would have to be.
Report the economic magnitude; route the full battery to the appendix; keep every number reproducible. A run end-to-end (synthetic data, real returns) is in the [JF execution walkthrough](../../../Journal-of-Finance-Skills/resources/worked-examples/02-execution-walkthrough.md). If StatsPAI/Stata are not connected, adapt the vendored `resources/code/` skeleton and flag any unverified number.
Checklist
- [ ] Branch chosen; **data-to-object mapping stated in one sentence**
- [ ] The single most convincing diagnostic is identified for in-text placement
- [ ] Empirical: modern estimator where TWFE would bias; design diagnostic shown
- [ ] Experiment: pre-registered; primary estimand pre-specified; balance/attrition handled
- [ ] Structural: key parameter tied to an identifying moment; sensitivity reported
- [ ] Inference as SEs / confidence sets (no asterisks); clustering level correct
- [ ] The headline claim never exceeds what the identification supports
Anti-patterns
- Relying on a wall of robustness to compensate for a weak core design (no room for it)
- TWFE on staggered treatment with no heterogeneity-bias discussion
- Reporting every experimental arm/heterogeneity split in-text instead of one estimand
- "The estimator converged" presented as identification (structural)
- Significance asterisks instead of standard errors / confidence sets
Referee pushback mapped to the fix
-
Stanford REAP × CoPaper.AI · 由斯坦福实证方法论团队精选与维护 访问 copaper.ai 微信:CoPaper.AI 按 11 个主流学科板块覆盖 经管与商科 社会科学 人文学科 数学与物理科学 生命科学 医学与健康 工程与技术 计算机科学与 AI 体育科学 点击任一学科名可跳转到对应说明;每类下的代表子领域在正文总览中完整列出。下方封面墙按 venue 导航,完整分类见覆盖一览。 🧭 布局指南 · 📚 Skill Pack 一览 · ⚡ 如何使用 · 🧪 自动实证
Other skills on awesome-journal-skills.
- /aaai-artifact-evaluation
Use when packaging AAAI code, data, multimedia appendices, technical appendices, reproducibility evidence, and post-acceptance artifact releases without violating double-blind or immutable-supplement rules.
Open skill - /aaai-author-response
Use when drafting an AAAI author response (rebuttal) under the single short character-limited author-feedback window, the no-URL rule, no-new-results guidance, AI-generated-review handling, and the AAAI two-phase review process where Phase-2 papers receive one feedback round
Open skill - /aaai-camera-ready
Use when preparing an accepted AAAI paper for camera-ready source submission to AAAI Press, including proceedings page limits, two-column template compliance, copyright transfer, purchased extra technical pages, deanonymization, registration, oral or poster presentation, and
Open skill - /aaai-experiments
Use when designing or auditing AAAI experiments for the broad-AI program committee, including baselines, ablations, statistical significance, robustness, human evaluation, AI-for-Social-Impact and alignment/safety evidence, compute and cost reporting, and
Open skill - /aaai-related-work
Use when positioning an AAAI paper's novelty against archival work, contemporaneous arXiv or workshop papers, and AAAI/IJCAI/NeurIPS/ICML/ICLR neighbors across the broad AI scope, while staying inside AAAI's dual-submission and AI-as-source policy constraints and writing a
Open skill - /aaai-reproducibility
Use when strengthening an AAAI paper's reproducibility checklist (placed after references), experimental traceability, seed and hyperparameter reporting, compute and cost disclosure, dataset access and licensing, code/data ZIP readiness, and the claim-to-evidence map that
Open skill

