finman-robustness
Use when deciding which robustness checks a Financial Management (FM) paper actually needs — FM explicitly puts "less weight on trivial robustness tests," so the craft is selecting threat-targeted checks and demoting busywork. Curates the robustness layer; it does not establish identification (finman-identification) or format exhibits (finman-tables-figures).
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill finman-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 Strategy (finman-robustness) ## When to trigger - The paper has a wall of robustness tables and you cannot say which threat each one answers - A coauthor wants to add "a few more specifications to be safe" before submission - A referee asked whether the result survives an *alternative explanation*, not just an alternative specification - You are unsure which checks belong in the main text vs. the internet appendix ## The FM robustness philosophy (this is the distinctive part) Most journals reward more robustness tables; **FM explicitly does not.** The editors state they put **less weight on trivial robustness tests** and more on **new ideas** and **whether the result is interesting and credible.** This inverts the usual instinct: at FM, a robustness section that mechanically re-runs the regression with five winsorization thresholds and three control sets signals *weak ideas hiding behind volume*. The skill here is **subtraction, then precision** — cut the busywork, then run the small number of checks that each defuse a *named alternative explanation* a smart referee would actually raise. One check that kills the leading confounder is worth more than ten that vary nothi
- When to trigger
- The FM robustness philosophy (this is the distinctive part)
- Threat-targeted robustness, not specification spraying
- Curation sequence
- What "less weight on trivial robustness" does NOT mean
- Execution bridge (StatsPAI / Stata MCP)
- Checklist
- Anti-patterns
- Worked vignette (illustrative)
- Subfield-specific robustness that is never trivial
- Output format
What does the finman-robustness skill do?
Use when deciding which robustness checks a Financial Management (FM) paper actually needs — FM explicitly puts "less weight on trivial robustness tests," so the craft is selecting threat-targeted checks and demoting busywork. Curates the robustness layer; it does not establish identification (finman-identification) or format exhibits (finman-tables-figures).
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill finman-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.