jmcb-robustness
Use when a Journal of Money, Credit and Banking (JMCB) result may be specification-, sample-, or inference-sensitive and you need to plan checks that each kill a specific threat. Builds a threat-mapped robustness suite; it does not re-run the core identification or write the prose.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jmcb-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 (jmcb-robustness) ## When to trigger - The headline (an IRF, an elasticity, a counterfactual welfare number) might flip under nearby choices - A referee will ask "is this the recursion ordering / lag length / sample window talking?" - Standard errors look too tight for a bank×time panel or for serially correlated macro data - The result depends on one regime (a crisis, the ZLB) and you have not shown sub-sample stability - You have a pile of "robustness" tables but cannot say which threat each one rules out ## The JMCB robustness logic JMCB referees do not reward a wall of additional regressions; they reward checks that are **mapped to a named threat to the specific identification**. A robustness suite is a list of "the result could be wrong because X — here is the check that rules out X." Given the journal's monetary/banking focus, the recurring threats are: shock contamination, specification dependence (lags, ordering, controls), inference understatement on panels and serially correlated series, and regime/sample instability around crises and policy transitions. ## Threat → check map (build yours from this) | Named threat | Diagnostic / check | |---|---| | S
- When to trigger
- The JMCB robustness logic
- Threat → check map (build yours from this)
- How to present it
- Inference deserves its own pass
- Crisis and regime stability is not optional for long samples
- Execution bridge (StatsPAI / Stata MCP)
- Checklist
- Anti-patterns
- Don't over-test: a focused suite beats an exhaustive one
- Worked vignette (illustrative)
- Output format
What does the jmcb-robustness skill do?
Use when a Journal of Money, Credit and Banking (JMCB) result may be specification-, sample-, or inference-sensitive and you need to plan checks that each kill a specific threat. Builds a threat-mapped robustness suite; it does not re-run the core identification or write the prose.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jmcb-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.