Individual skill
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.
World-Bank-Economic-Review-Skills/skills/wber-robustness/SKILL.md
Source commit 932eb23331721b16e967c59f093781be1928b498
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 9, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 1,405
- Repository last updated
- Sep 27, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- academic-writing Repository topic
- agent-skills Repository topic
- journal Repository topic
- academic-research Repository topic
- ai-agents Repository topic
- anthropic Repository topic
- awesome-list Repository topic
- claude Repository topic
- claude-code Repository topic
- economics Repository topic
- data Derived category
- security Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Read excerpt
# 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?"
