jpube-writing-style
Use when polishing prose for a Journal of Public Economics (JPubE / JPubEc) manuscript — a 250-word abstract stating purpose, results, and policy conclusion; an intro that lands the government-role question; author-date references; and clear translation of estimates into welfare terms. Late-stage polish; it does not change the analysis.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jpube-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 (jpube-writing-style) ## When to trigger - The abstract exceeds 250 words or buries the policy finding - The intro recites results before stating the public-economics question - Estimates are reported without translation into welfare / revenue terms - References are not in author-date format ## JPubE house style JPubE is an Elsevier field journal read by public-finance specialists internationally, and its conventions are concrete. Match them: - **Abstract: 250 words maximum.** Write a concise, factual abstract stating the purpose, the principal results (with the key number), and the major policy conclusion. No literature, no equations. - **References: author-date (name-and-year)** in-text, per Elsevier's economics formatting; reference list alphabetical by surname. Numbered/footnote citation styles read as off-template. - **Source files.** Supply editable files: Word in **single-column** layout, or LaTeX (`.tex`) — double-column is permitted only for LaTeX submissions. Keep the manuscript in an editable format, not a flattened PDF only. - **AI disclosure.** If generative AI assisted manuscript preparation, it must be **declared at submission**; AI may support but no
- When to trigger
- JPubE house style
- Prose moves specific to public economics
- Checklist
- Anti-patterns
- Style execution pass for Journal of Public Economics
- Output format
What does the jpube-writing-style skill do?
Use when polishing prose for a Journal of Public Economics (JPubE / JPubEc) manuscript — a 250-word abstract stating purpose, results, and policy conclusion; an intro that lands the government-role question; author-date references; and clear translation of estimates into welfare terms. Late-stage polish; it does not change the analysis.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jpube-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.