wber-robustness
Use when results for a The World Bank Economic Review (WBER) manuscript may be sensitive to specification, sample, measurement, or inference choices — and you need a threat-organized robustness plan rather than an appendix dump. Organizes checks by identifying threat and by data-quality risks specific to developing-country data; it does not run the estimation.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill wber-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 (wber-robustness) ## When to trigger - The headline result moves under reasonable alternative specifications - A referee could question measurement quality (survey error, recall, attrition, undercoverage) - Inference is shaky: few clusters, spatial correlation, multiple outcomes - The robustness appendix is a long mechanical list with no logic - You need to know which checks are load-bearing before submission ## The WBER robustness philosophy WBER referees are sophisticated about *both* econometric threats *and* the realities of **developing-country data** — surveys with recall and measurement error, administrative records with coverage gaps, sampling frames that miss the informal sector, attrition in panels. So robustness here has two axes: the standard **identification-threat** axis (does the estimate survive plausible violations of the design's key assumption?) and a **data-quality** axis (does the result survive how the data were actually constructed and measured?). Organize the section by *threat*, not by a checklist; each check should answer "if a skeptic believed X, would my conclusion change?" ## Organize by threat, not by appendix | Threat the referee
- When to trigger
- The WBER robustness philosophy
- Organize by threat, not by appendix
- Data-quality robustness (the development-specific layer)
- Sequencing the robustness section
- Execution bridge (StatsPAI / Stata MCP)
- Checklist
- Anti-patterns
- Worked vignette (illustrative)
- Distinguishing robustness from a sensitivity analysis
- Output format
What does the wber-robustness skill do?
Use when results for a The World Bank Economic Review (WBER) manuscript may be sensitive to specification, sample, measurement, or inference choices — and you need a threat-organized robustness plan rather than an appendix dump. Organizes checks by identifying threat and by data-quality risks specific to developing-country data; it does not run the estimation.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill wber-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.