ecopol-writing-style
Use when an Economic Policy (EP) manuscript's prose reads like a technical report instead of accessible policy writing. Rewrites for the EP dual audience — non-technical main text, rigor in the appendix; it does not invent evidence or citations.
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ecopol-writing-style --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Writing Style (ecopol-writing-style) ## When to trigger - The introduction opens with the econometric specification instead of the policy question - A policymaker would stop reading at the third paragraph because of jargon or notation - The main text is dense with equations a policy reader cannot follow - The abstract states what you did, not what a policymaker should now think - The paper has rigor but not the accessible voice EP is known for ## EP's defining house style: accessible main text, rigorous appendix This is the most distinctive EP craft skill, because EP's whole identity is **rigorous analysis written accessibly for economists and policymakers together**. The discipline is a *split*: the **main text is non-technical and policy-first**; the **technical machinery — proofs, full estimators, derivations — lives in the appendix**. A reader from a finance ministry should be able to read the main text start to finish and come away with the policy conclusion and the reasoning; an economist should be able to verify everything in the appendix. Write the main text as if explaining to a smart non-specialist, not dumbing down — making the logic legible without notation. This is a
- When to trigger
- EP's defining house style: accessible main text, rigorous appendix
- The EP intro structure (write it in this order)
- Sentence- and section-level moves
- Checklist
- Anti-patterns
- Output format
What does the ecopol-writing-style skill do?
Use when an Economic Policy (EP) manuscript's prose reads like a technical report instead of accessible policy writing. Rewrites for the EP dual audience — non-technical main text, rigor in the appendix; it does not invent evidence or citations.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ecopol-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.