Agent skill · Code Review & Quality

worlddev-referee-strategy

Use when anticipating the objections a World Development (WD) manuscript will draw under double-anonymized, multidisciplinary review. Pre-empts referee pushback before submission; 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-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: 5 KB
Bundled scripts: none
Path: World-Development-Skills/skills/worlddev-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 (worlddev-referee-strategy) ## When to trigger - Before submitting, to war-game the reports the paper will draw - The paper sits between disciplines and could face one economist and one non-economist referee with incompatible standards - A previous WD or sibling-journal rejection cited objections that were never addressed - The development relevance is implicit and a referee could read the paper as "just an applied estimate" - You need to decide what to fix now vs. what to defend in the response letter ## The WD review reality WD review is **double-anonymized**: at least two independent referees, who cannot see who you are (and you cannot see them). Because WD is multidisciplinary, the referee pool is **heterogeneous in method and standard** — a single paper may be read by an applied economist who wants tighter identification and a development sociologist who wants richer context and reflexivity. The strategic implication: **a WD paper must satisfy more than one evidentiary culture at once.** A paper that is bulletproof to one referee community but illegible or naive to the other is the classic WD split-decision that stalls. Anonymize hard, too — WD's double-blin

What's inside
Steps it walks through
  1. When to trigger
  2. The WD review reality
  3. War-gaming the two referee archetypes
  4. Predictable WD objections and the fix
  5. Suggesting reviewers (where the portal allows)
  6. Checklist
  7. Anti-patterns
  8. Output format
More from Awesome-Journal-Skills
All skills →
About this skill
What does the worlddev-referee-strategy skill do?

Use when anticipating the objections a World Development (WD) manuscript will draw under double-anonymized, multidisciplinary review. Pre-empts referee pushback before submission; it does not invent evidence or citations.

How do I install it?

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