Agent skill · Security

ecopol-robustness

Use when an Economic Policy (EP) manuscript's results may be specification-, sample-, or inference-fragile, especially ahead of the two-discussant panel. Organizes robustness by the threat a discussant will raise; 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 ecopol-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: Economic-Policy-Skills/skills/ecopol-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 Strategy (ecopol-robustness) ## When to trigger - The headline policy magnitude moves under plausible alternative specifications - A discussant could attribute the result to one sample, period, or country - Inference rests on few clusters / few treated units (common in policy evaluations) - The result is statistically significant but the **magnitude** — the part a policymaker uses — is imprecise - You are pre-empting the academic discussant's "have you tried…" before the conference ## Robustness is discussant-proofing, not a checklist dump At EP, robustness has a specific purpose: the paper will be debated live by **two invited discussants** who act as the referees, and the academic one will arrive with a list of fragility tests. So organize robustness **by the threat each test neutralizes**, not as a mechanical appendix of "alternative specifications." A reader (and the policy discussant) should see, for each test, *which way of being wrong it rules out*. Because EP papers carry a recommendation, the central object to defend is the **magnitude and its confidence interval**, not just the sign. ## The threat-to-test map (build the robustness section from this) | Threat

What's inside
Steps it walks through
  1. When to trigger
  2. Robustness is discussant-proofing, not a checklist dump
  3. The threat-to-test map (build the robustness section from this)
  4. Craft moves
  5. Execution bridge (StatsPAI / Stata MCP)
  6. Checklist
  7. Anti-patterns
  8. Output format
More from Awesome-Journal-Skills
All skills →
About this skill
What does the ecopol-robustness skill do?

Use when an Economic Policy (EP) manuscript's results may be specification-, sample-, or inference-fragile, especially ahead of the two-discussant panel. Organizes robustness by the threat a discussant will raise; it does not invent evidence or citations.

How do I install it?

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