Agent Skills
› brycewang-stanford/Awesome-Journal-Skills
› jpart-writing-style
jpart-writing-style
GitHub用于撰写或润色《公共行政研究与理论》(JPART) 稿件，确保符合OUP作者-日期格式、双盲评审要求及12000字限制。重点强化理论贡献的呈现、机制阐述及摘要结构，优化行文逻辑与引用规范，不虚构内容。
Trigger Scenarios
起草引言或进行最终润色
超字数需精简而不失论点
撰写强调理论到政策启示的摘要
对齐OUP格式以准备投稿
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jpart-writing-style -g -y
SKILL.md
Frontmatter
{
"name": "jpart-writing-style",
"description": "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."
}
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
- 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.
- 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).
- Argument-first prose. Lead with claims about the theory; use evidence to support them. Avoid "the data show…" without saying what they show and why it matters for public management.
- Signpost lightly. Clear structure, but no seven-section roadmap padding the word count.
Format to JPART / OUP style
- Citations: author-date in text, alphabetical reference list with DOIs; keep one consistent style (manage with Zotero/BibTeX).
- Keywords: 3–5; the first three should signal theory, research theme, and method (JPART convention).
- Abstract: state theoretical approach → method and data → results → implications for theory.
- Anonymize: JPART is double-blind — omit your name and funding from the manuscript, cite your own work in the third person, and keep acknowledgments/funding on the cover sheet only.
Abstract stress test
Draft the abstract as four disciplined sentences before polishing the manuscript:
- Theory: What public-management theory or mechanism is at stake?
- Method/data: What design, case, sample, and data identify or illuminate the mechanism?
- Result: What is the directional, substantive finding in units a reader can understand?
- Implication for theory: What should the field believe, qualify, or test differently?
If sentence 1 could describe any public-sector setting, the paper is not framed tightly enough. If
sentence 4 says only "policy implications," route back to jpart-topic-selection or
jpart-theory-building.
Fit the word cap (~12,000 words including abstract, tables, references)
- Move balance tables, full specs, and extended robustness to the online supplement.
- Cut throat-clearing and literature dumps; engage the conversation, not every paper (see
jpart-literature-positioning). - Because the cap counts references, prune citation padding; keep the works that constitute the debate.
- Prefer one decisive marginal-effects figure to three redundant tables.
Cut in this order when over budget:
- Generic PA throat-clearing that does not define the mechanism.
- Literature paragraphs with no role in the contribution claim.
- Redundant robustness prose already visible in tables or supplement.
- Repeated method description across text, exhibit notes, and appendix.
- Secondary mechanisms that cannot be adjudicated by the design.
Do not cut the theory contribution, scope conditions, or design limits; those are what make the paper reviewable at JPART.
Anti-patterns
- An empirics-first intro that never states the theoretical contribution (reads atheoretical)
- Burying the mechanism and the "implications for theory" in the conclusion
- An abstract that reports results but never names the theoretical approach
- Mixed citation styles; acknowledgments or self-references that break double-blind anonymity
- Forgetting that the word cap counts the abstract, tables, and references
Output format
【Theory stated by end of intro?】[Y/N]
【Mechanism named in plain language?】[Y/N]
【Abstract】theory → method/data → results → implications for theory? [Y/N]
【Cut order used】generic setup / unused literature / redundant robustness / repeated methods / secondary mechanisms
【Word count】≤ ~12,000 incl. abstract/tables/references? [Y/N]
【OUP author-date + 3-5 keywords + anonymized】[Y/N]
【Next】jpart-transparency-and-data
Supplementary resources
../../resources/worked-examples/01-introduction.md— before→after JPART-style introduction../../resources/official-source-map.md— word limit, abstract template, keyword convention, anonymity
Version History
- 1839142 Current 2026-07-05 13:55
