eer-robustness
Use when a European Economic Review (EER) result must be shown to survive specification, sample, measurement, and inference changes — the robustness battery referees demand. Builds the stress tests and organizes them; it does not establish the core identification or write the prose.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill eer-robustness --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.
# Robustness & Sensitivity (eer-robustness) ## When to trigger - The headline estimate exists but its fragility has not been probed - A referee (or co-author) suspects the result is driven by one sample/spec choice - Inference assumptions (clustering, dependence, multiple testing) are unexamined - A structural/quantitative result's sensitivity to parameters is not shown ## The EER robustness bar A general-interest result must be **believable beyond the authors' favorite specification**. EER referees — methods-aware under single-anonymized review — expect a **disciplined battery**, not a scattershot appendix: vary the things that *could plausibly overturn the result*, report them transparently, and say which (if any) move the estimate. The goal is a result that is **robust where it matters and honest where it is fragile**. Robustness is not infinite specification mining; choose tests with a *reason*. ## The robustness battery (choose by design) | Dimension | Test | Why it matters | |-----------|------|----------------| | Specification | add/drop controls; alternative functional form; FE structure | shows the estimate is not a control artifact | | Sample | leave-one-out (unit/region/
- When to trigger
- The EER robustness bar
- The robustness battery (choose by design)
- How to organize it
- Execution bridge (StatsPAI / Stata MCP)
- Checklist
- Anti-patterns
- Worked vignette (illustrative)
- Output format
What does the eer-robustness skill do?
Use when a European Economic Review (EER) result must be shown to survive specification, sample, measurement, and inference changes — the robustness battery referees demand. Builds the stress tests and organizes them; it does not establish the core identification or write the prose.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill eer-robustness --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.