Agent skill · Security

worlddev-robustness

Use when results may be sensitive — to specification, sample, measurement, or inference for quantitative work, or to interpretation and triangulation for qualitative work — in a World Development (WD) manuscript. Organizes checks by threat; it does not invent evidence or citations.

brycew6m878★ · +32/wk · 1 repos on radarProfile →
claude-codeMIT
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill worlddev-robustness --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 6 KB
Bundled scripts: none
Path: World-Development-Skills/skills/worlddev-robustness/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 909 · +31 this week
Language: Stata
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Robustness & Trustworthiness (worlddev-robustness) ## When to trigger - The headline result moves under plausible alternative specifications - A referee suspects the finding is driven by one region, one wave, or one measurement choice - Development data are messy (recall error, measurement in informal economies, attrition) and this is unaddressed - A qualitative finding rests on a few vivid quotes with no account of disconfirming evidence - The robustness section is a mechanical dump of appendix tables organized by table, not by threat ## Organize by threat, not by table The single biggest WD robustness failure is a wall of appendix tables with no logic. A WD referee — often from a different discipline than the author — wants to see that you **identified the threats to your specific claim and addressed each one**. Structure the robustness work as a short list of named threats, each with the check that retires it and a one-line verdict. For each threat: *what would break the claim, what test isolates it, what the test shows.* ### Quantitative threat map | Threat | Check | |--------|-------| | Specification dependence | Add/drop controls in a disciplined sequence (Oster-style δ/bou

What's inside
Steps it walks through
  1. When to trigger
  2. Organize by threat, not by table
  3. Quantitative threat map
  4. Qualitative trustworthiness map
  5. Mixed-methods
  6. Development-specific traps WD referees catch
  7. Execution bridge (StatsPAI / Stata MCP)
  8. Checklist
  9. Anti-patterns
  10. Output format
More from Awesome-Journal-Skills
All skills →
About this skill
What does the worlddev-robustness skill do?

Use when results may be sensitive — to specification, sample, measurement, or inference for quantitative work, or to interpretation and triangulation for qualitative work — in a World Development (WD) manuscript. Organizes checks by threat; it does not invent evidence or citations.

How do I install it?

Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill worlddev-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.

Keep going