eer-identification
Use when the empirical causal-identification argument is the bottleneck for a European Economic Review (EER) manuscript — DiD/event-study, IV, RDD, or experiment. Stress-tests the design to EER's general-interest credibility bar before exhibits are finalized; it does not build the theory model or the robustness battery.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill eer-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 Strategy (eer-identification) ## When to trigger - A causal claim rests on OLS + controls, or TWFE on staggered timing - An IV's exclusion restriction or first-stage strength is contested - An RDD's continuity/manipulation assumptions are unexamined - An experiment's estimand, balance, or pre-registration is unclear - You are unsure the design clears EER's credibility bar for a general-interest readership ## The EER identification bar EER publishes broadly across empirical economics, so identification is judged on **credibility legible to a general reader**: the **mapping from variation in the data to the causal object** must be explicit, the key assumption stated, and the most obvious threat pre-empted. Because review is **single-anonymized**, the referee is often a methods expert in your exact design — modern, design-appropriate estimators and honest inference are expected. Report **standard errors and confidence intervals** (EER house style; do not lean on significance stars — see `eer-tables-figures`). Match the size of the causal claim to what the design supports. ## Branch paths ### Branch A: DiD / event study - With **staggered adoption**, move beyond TWFE (
- When to trigger
- The EER identification bar
- Branch paths
- Branch A: DiD / event study
- Branch B: IV
- Branch C: RDD
- Branch D: Experiment / behavioral
- Execution bridge (StatsPAI / Stata MCP)
- Checklist
- Anti-patterns
- Worked vignette (illustrative)
- Output format
What does the eer-identification skill do?
Use when the empirical causal-identification argument is the bottleneck for a European Economic Review (EER) manuscript — DiD/event-study, IV, RDD, or experiment. Stress-tests the design to EER's general-interest credibility bar before exhibits are finalized; it does not build the theory model or the robustness battery.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill eer-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.