Agent skill · Documentation

jpart-writing-style

Use when drafting or polishing a Journal of Public Administration Research and Theory (JPART) manuscript so it reads as theory-plus-rigor, follows OUP author-date style, and fits the ~12,000-word cap that includes the abstract, tables, and references. Tightens prose and format; it does not invent content.

brycew6m878★ · +32/wk · 1 repos on radarProfile →
claude-codeMIT
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jpart-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: 5 KB
Bundled scripts: none
Path: Journal-of-Public-Administration-Research-and-Theory-Skills/skills/jpart-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 (jpart-writing-style) A JPART paper must read as a **public-management theory contribution carried by rigorous evidence**, formatted to the journal's OUP author-date style, and disciplined to the word cap. JPART's own guidance asks the abstract to state the **theoretical approach, method and data, results, and implications for theory** — the paper should follow the same arc. ## When to trigger - Drafting the introduction, framing the contribution, or final polish - Over the word cap and needing to cut without losing the argument - Writing the abstract (theory → method/data → results → implications for theory) - Aligning citations/headings/format to OUP author-date style before submission ## Lead with theory, support with rigor 1. **Front-load the theoretical contribution.** By the end of the introduction the reader knows the PA theory at stake, the mechanism, the design, the headline result, and what it means *for theory*. 2. **Name the mechanism in plain language.** Don't make the reader infer why the relationship holds — state the public-management logic (incentives, motivation, identity, institutions). 3. **Argument-first prose.** Lead with claims about the theor

What's inside
Steps it walks through
  1. When to trigger
  2. Lead with theory, support with rigor
  3. Format to JPART / OUP style
  4. Abstract stress test
  5. Fit the word cap (~12,000 words including abstract, tables, references)
  6. Anti-patterns
  7. Output format
  8. Supplementary resources
More from Awesome-Journal-Skills
All skills →
About this skill
What does the jpart-writing-style skill do?

Use when drafting or polishing a Journal of Public Administration Research and Theory (JPART) manuscript so it reads as theory-plus-rigor, follows OUP author-date style, and fits the ~12,000-word cap that includes the abstract, tables, and references. Tightens prose and format; it does not invent content.

How do I install it?

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