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 experiment. Stress-tests the strategy so it is clean enough to defend in a few pages, before exhibits are finalized.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill aeri-identification --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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 (
- When to trigger
- The AER: Insights identification bar
- Branch paths
- Branch A: Empirical causal design (the most common AER: Insights paper)
- Branch B: Experiment (own data)
- Branch C: Structural / parameter identification
- Branch D: New fact / measurement
- Choosing the single in-text diagnostic
- Execution bridge (StatsPAI / Stata MCP)
- Checklist
- Anti-patterns
- Referee pushback mapped to the fix
- Output format
What does the aeri-identification skill do?
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.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill aeri-identification --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From brycewang-stanford/Awesome-Journal-Skills, a repository with 909 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.