Agent skill · Code Review & Quality

wber-writing-style

Use when the prose for a The World Bank Economic Review (WBER) manuscript buries the development-policy contribution — abstract, introduction, and the bridge from estimate to policy lesson. Sharpens the writing for a mixed economist + policymaker audience; it does not run analysis or build exhibits.

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

# Writing Style (wber-writing-style) ## When to trigger - The abstract states a topic, not a result, and never names the policy stake - The introduction takes three pages to reach the question - The paper reads either as a dry econometrics exercise or as an advocacy brief — not the WBER middle - The bridge from "we estimate X" to "so development policy should consider Y" is missing - A coauthor says the writing does not sound like a WBER paper ## The WBER voice WBER writing serves a **dual audience**: economists who demand precision and policymakers/practitioners who demand relevance. The house voice is **rigorous but legible** — technically exact, jargon-controlled, and always closing the loop to a development-policy implication. Two failure modes bracket it: prose so technical that a finance-ministry reader gives up, and prose so policy-breathless that an economist distrusts it. Aim for the middle: state the credible result plainly, then say what it means for a development decision *without* overclaiming and *without* implying alignment with any World Bank position (editorial independence is explicit). Write the body first; write the abstract and introduction last, once the resul

What's inside
Steps it walks through
  1. When to trigger
  2. The WBER voice
  3. The introduction recipe (WBER variant)
  4. The abstract
  5. Prose discipline
  6. Checklist
  7. Anti-patterns
  8. Worked vignette (illustrative)
  9. Calibrating the technical register
  10. Output format
More from Awesome-Journal-Skills
All skills →
About this skill
What does the wber-writing-style skill do?

Use when the prose for a The World Bank Economic Review (WBER) manuscript buries the development-policy contribution — abstract, introduction, and the bridge from estimate to policy lesson. Sharpens the writing for a mixed economist + policymaker audience; it does not run analysis or build exhibits.

How do I install it?

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