Agent skill · Code Review & Quality

restud-robustness

Use when the main results of a The Review of Economic Studies (REStud) manuscript exist but referee-anticipating checks — robustness, heterogeneity, mechanism, placebo, alternative specifications — are missing or fragile. Hardens the result against demanding referees; does not redesign identification.

brycew6m878★ · +32/wk · 1 repos on radarProfile →
claude-codeMIT
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill restud-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: Review-of-Economic-Studies-Skills/skills/restud-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

# REStud Robustness (restud-robustness) ## When to trigger - The main result rests on a single specification - No placebo / falsification evidence exists - A referee will say "the effect is driven by X" and you have no pre-empting check - The result is statistically marginal and sensitivity is undocumented - Heterogeneity or mechanism evidence is absent and the channel is asserted, not shown ## The REStud standard REStud referees are demanding and the journal is known for *developing strong papers across rounds*. A robust REStud result is one that **does not hinge on one fragile specification**. The goal of this stage is to find the weak point before a referee does, and either fix it or report it honestly. Robustness is not a wall of extra tables — it is targeted evidence against the most plausible alternative explanations. Two REStud-specific facts shape how you stage it: (1) bulk robustness belongs in the **online appendix / supplementary file**, with only the decisive checks in the main text; (2) for an *accepted* empirical paper, every robustness number must be reproducible, because the **Data Editor (Miklós Koren) reruns your code before publication** under the AEA DCAS standa

What's inside
Steps it walks through
  1. When to trigger
  2. The REStud standard
  3. Priority of checks
  4. Calibrating effort
  5. Reporting discipline
  6. The honest-fragility test
  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 restud-robustness skill do?

Use when the main results of a The Review of Economic Studies (REStud) manuscript exist but referee-anticipating checks — robustness, heterogeneity, mechanism, placebo, alternative specifications — are missing or fragile. Hardens the result against demanding referees; does not redesign identification.

How do I install it?

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