Agent skill · Data & Analytics

wber-referee-strategy

Use when anticipating referee and editor objections before submitting to The World Bank Economic Review (WBER) — pre-empting the predictable development-economics pushbacks (external validity, identification, data quality, policy relevance) and writing the cover letter. Plans defenses; it does not run new analysis.

brycew6m4,252★ · +31/wk · 3 repos on radarProfile →
claude-codeMIT
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill wber-referee-strategy --agent claude-code

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

Facts
Files in the skill folder: 1
SKILL.md size: 7 KB
Bundled scripts: none
Path: World-Bank-Economic-Review-Skills/skills/wber-referee-strategy/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

# Referee Strategy (wber-referee-strategy) ## When to trigger - The paper is near submission and you want to surface objections before a referee does - You are writing the cover letter and choosing how to frame the contribution to the editor - You suspect one referee will be a hard-identification economist and another a policy reader - You want to decide which robustness checks to pre-load in the paper vs. hold for the response - You are unsure whether the framing will survive the "is this a World Bank paper?" reflex ## Who referees WBER — and what they punish WBER's review is **single-anonymized** (referees are anonymous; your name is on the title page), and editors (Eric Edmonds and Nina Pavcnik, Dartmouth, 检索于 2026-06;以官网为准) draw on a development-economics referee pool that overlaps heavily with JDE, AEJ: Applied, and the AEA journals. Expect **two referee archetypes** and write for both: - **The identification referee** — sophisticated about staggered-DiD bias, weak IV, RD manipulation, attrition, spillovers. Punishes asserted exclusion restrictions, TWFE on staggered timing, and overreach beyond the estimand. - **The policy/development referee** — asks "so what for development

What's inside
Steps it walks through
  1. When to trigger
  2. Who referees WBER — and what they punish
  3. The predictable WBER objections (pre-empt in the paper)
  4. The cover letter
  5. Pre-load vs. hold in reserve
  6. Checklist
  7. Anti-patterns
  8. Self-citation and the single-anonymized reality
  9. Worked vignette (illustrative)
  10. Output format
More from Awesome-Journal-Skills
All skills →
About this skill
What does the wber-referee-strategy skill do?

Use when anticipating referee and editor objections before submitting to The World Bank Economic Review (WBER) — pre-empting the predictable development-economics pushbacks (external validity, identification, data quality, policy relevance) and writing the cover letter. Plans defenses; it does not run new analysis.

How do I install it?

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