From wber-skills
Plans defenses before submitting to WBER by pre-empting referee objections (external validity, identification, data quality, policy relevance) and writing the cover letter.
How this skill is triggered — by the user, by Claude, or both
Slash command
/wber-skills:wber-referee-strategyThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
- The paper is near submission and you want to surface objections before a referee does
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:
A paper that satisfies only one archetype is the canonical WBER R&R-or-reject. Pre-empt both.
| Likely objection | Pre-emption to build in before submitting |
|---|---|
| "This is a project report, not general-interest" | Frame around a transferable mechanism; state external validity explicitly (wber-topic-selection, wber-identification) |
| "Identification rests on an untested assumption" | Show the diagnostic that could have failed; report design-specific sensitivity (wber-identification, wber-robustness) |
| "Developing-country data quality is suspect" | Measurement-error and coverage checks against an alternative source (wber-robustness) |
| "The LATE won't survive scale-up" | Discuss complier-vs-population, GE channels, fiscal cost (wber-identification) |
| "Why WBER and not JDE / World Development?" | One intro sentence on the policy-audience contribution (wber-literature-positioning) |
| "Not reproducible" | Have the data/code package and DOI-linked DAS ready (wber-replication-package) |
Not every check belongs in the submitted paper. Decide deliberately:
The judgment call: anything a competent referee would certainly ask goes in the paper; anything they might ask is held, code-ready, for the response letter.
Because WBER review is single-anonymized, referees can see who you are — so the usual double-blind tricks do not apply and can backfire. Do not over-cite yourself to signal authority; do not strip your own relevant prior work to feign novelty (a referee who knows your record will notice). Cite your prior work where it is genuinely the right reference, in the third person, and let the contribution stand on the new result. Treat the referees as informed colleagues who may well know your earlier papers better than you expect.
Before submitting an RD evaluation of a subsidy, the authors war-game two reports. The identification referee will challenge manipulation at the eligibility score; they pre-load a Cattaneo–Jansson–Ma density test and a donut check. The policy referee will ask whether a local-at-cutoff effect justifies a national change; they add a paragraph on the complier population and a back-of-envelope fiscal cost at scale. The cover letter opens: "Governments spend billions on means-tested subsidies but lack credible estimates of marginal effects; using [country]'s eligibility threshold we estimate a 5pp enrollment gain at $90 per enrollee." Both archetypes are answered before review begins.
【Identification referee】top objection + pre-emption in paper
【Policy referee】top objection + pre-emption in paper
【External validity / cost】in the paper? [Y/N]
【Why-WBER sentence】in intro AND cover letter? [Y/N]
【Package readiness】data/code + DOI DAS ready? [Y/N]
【Cover letter】names policy decision + magnitude in opening? [Y/N]
【Next step】wber-submission
npx claudepluginhub brycewang-stanford/awesome-journal-skills --plugin wber-skillsRoutes manuscript work for The World Bank Economic Review (WBER) submissions, directing to the appropriate wber-* sub-skill based on current stage or bottleneck.
Evaluates manuscript fit for the World Bank Economic Review, covering scope, method bar, house style, and desk-reject risks for development economics papers.
Anticipates objections from European Economic Review referees and maps them to in-paper fixes before submission. Reduces desk-screen risk and pre-empts predictable pushback.