pubar-writing-style
Use when drafting or polishing a Public Administration Review (PAR) manuscript so it reads for scholars AND practitioners, carries strong Evidence for Practice, and fits the limits (≤ 8,000 words incl. abstract/endnotes/references; abstract ≤ 150 words). Tightens prose and format; it does not invent content.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill pubar-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 (pubar-writing-style) A PAR paper must be readable by a public-management scholar outside its niche **and** speak to a reflective practitioner. The journal's defining feature is the **research-and-practice bridge**: every article carries **Evidence for Practice** points. This skill is about reaching both audiences and respecting the format — not about generating claims. ## When to trigger - Drafting the introduction, framing the contribution, or final polish - Writing or tightening the **Evidence for Practice** takeaways - Over the word cap and needing to cut without losing the argument - Writing the **≤ 150-word abstract** or aligning citations to APA style ## Reach scholars and practitioners 1. **Front-load the contribution and the stake.** By the end of the introduction the reader knows the question, the argument, the evidence, and **why a public manager should care.** Don't make either audience dig for the "so what." 2. **Write the Evidence for Practice honestly.** 3–5 sentence-length takeaways that distill what the findings mean for practice — specific enough to inform a managerial decision, never over-claimed beyond what the analysis supports. (Encouraged at s
- When to trigger
- Reach scholars and practitioners
- Evidence for Practice calibration
- Dual-reader paragraph test
- Format (APA author–date; confirm current edition)
- Word-budget triage for PAR
- Abstract and title-page pass
- Anti-patterns
- Output format
- Supplementary resources
What does the pubar-writing-style skill do?
Use when drafting or polishing a Public Administration Review (PAR) manuscript so it reads for scholars AND practitioners, carries strong Evidence for Practice, and fits the limits (≤ 8,000 words incl. abstract/endnotes/references; abstract ≤ 150 words). Tightens prose and format; it does not invent content.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill pubar-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.