jfe-robustness
Use when a Journal of Financial Economics (JFE) result needs the exhaustive robustness battery the journal is known for — alternative measures, subsamples, specifications, and falsification. Builds the stress-test plan; it does not choose the core estimator (jfe-empirical-design) or the identification design (jfe-identification).
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jfe-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 Battery (jfe-robustness) ## When to trigger - The result holds in the baseline but you have not tried obvious alternatives - A referee could ask "does this survive a different measure / sample / specification?" - You are unsure which robustness tests belong in the main text vs. the Internet Appendix - You suspect a result might be fragile and want to find out before a referee does ## Why robustness is JFE's signature JFE's referee culture rewards thoroughness: a result is credible only after it survives a wide battery of sensible alternatives, and reviewers expect *every* alternative explanation to be addressed, not merely the convenient ones. A fragile result that breaks under a routine variation is a classic JFE rejection. The headline tests live in the main text; the rest go to the Internet Appendix, which JFE asks you to append to the end of the main manuscript file (see `jfe-internet-appendix`). Because JFE mandates a **code + non-proprietary-data deposit** (Mendeley Data) at acceptance for post-2021 submissions, your robustness battery must be *runnable*, not just described — referees increasingly probe reproducibility after the field-wide concerns about non-repl
- When to trigger
- Why robustness is JFE's signature
- The robustness dimensions
- 1. Alternative measures
- 2. Alternative specifications
- 3. Alternative samples
- 4. Alternative inference
- 5. Falsification & placebos
- 6. Ruling out alternative explanations
- Execution bridge (StatsPAI / Stata MCP)
- Checklist
- Anti-patterns
- Output format
What does the jfe-robustness skill do?
Use when a Journal of Financial Economics (JFE) result needs the exhaustive robustness battery the journal is known for — alternative measures, subsamples, specifications, and falsification. Builds the stress-test plan; it does not choose the core estimator (jfe-empirical-design) or the identification design (jfe-identification).
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jfe-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.