Agent skill · Code Review & Quality

wber-rebuttal

Use when a The World Bank Economic Review (WBER) decision letter has arrived (R&R or reject-with-encouragement) and you need the response-letter strategy — triaging editor vs. referee asks, sequencing new analysis, and writing point-by-point replies for the identification and policy referee archetypes. Plans the revision; it does not run the new analysis.

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

# Rebuttal Strategy (wber-rebuttal) ## When to trigger - A WBER decision letter arrived (R&R, major/minor revision, or reject-with-encouragement) - You need to triage which referee asks are deal-breakers vs. optional - The two referees disagree, or one is identification-focused and the other policy-focused - You are deciding what new analysis is worth running before resubmitting - You need to draft the point-by-point response letter ## Read the letter through the WBER lens WBER revisions almost always hit the journal's two-part bar: the **identification referee** wants the design hardened; the **policy referee** wants relevance, external validity, and cost. The editor's letter is the binding document — **the editor's synthesis outranks any single referee**, and the editor will signal which concerns are essential. Read the editor's framing first, then map each referee point to a referee archetype so your tone and evidence fit the reader. Single-anonymized review means the referees know who you are; engage them as informed colleagues, not adversaries. ## Triage every point | Tier | What it is | How to handle | |------|-----------|----------------| | **Deal-breaker** | The editor or a

What's inside
Steps it walks through
  1. When to trigger
  2. Read the letter through the WBER lens
  3. Triage every point
  4. Writing the response letter
  5. Sequencing the revision work
  6. Checklist
  7. Anti-patterns
  8. Tone and the single-anonymized referee
  9. Worked vignette (illustrative)
  10. Output format
More from Awesome-Journal-Skills
All skills →
About this skill
What does the wber-rebuttal skill do?

Use when a The World Bank Economic Review (WBER) decision letter has arrived (R&R or reject-with-encouragement) and you need the response-letter strategy — triaging editor vs. referee asks, sequencing new analysis, and writing point-by-point replies for the identification and policy referee archetypes. Plans the revision; it does not run the new analysis.

How do I install it?

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