Agent skill · Testing & QA

jpart-workflow

Use as the entry point for any Journal of Public Administration Research and Theory (JPART) manuscript. Routes to the right JPART sub-skill based on the lifecycle stage and forces the journal's defining test — a public-management theory contribution, not a bare empirical finding. It dispatches; it does not draft content.

brycew6m878★ · +32/wk · 1 repos on radarProfile →
claude-codeMIT
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jpart-workflow --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 6 KB
Bundled scripts: none
Path: Journal-of-Public-Administration-Research-and-Theory-Skills/skills/jpart-workflow/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

# JPART Workflow Router (jpart-workflow) The orchestrator for a JPART submission. Figure out the stage, then send the user to the matching skill. JPART is the **theory-and-research flagship of public administration** — the owning society is the **Public Management Research Association (PMRA)** and the publisher is **Oxford University Press**. The router's first job is to make sure the paper *builds or tests public-management theory*, not just report an estimate. ## When to trigger - Starting a new JPART paper and unsure where to begin - Mid-project and unsure which skill applies next - A reviewer or co-author said the paper is "atheoretical" or "reads like a policy report" - Returning with a decision letter (route to `jpart-rebuttal`) ## First question: is there a theoretical contribution? JPART rejects strong empirics with no theory. Before routing anywhere, force this gate: | Symptom | What it means | Route to | |---------|---------------|----------| | Clean estimate, thin "so what" | finding without a theory move | `jpart-theory-building` | | "We test X in setting Y" only | descriptive, no mechanism | `jpart-topic-selection` | | Strong PA theory, weak identification | claim outr

What's inside
Steps it walks through
  1. When to trigger
  2. First question: is there a theoretical contribution?
  3. Routing map (stage → skill)
  4. Default order
  5. Router stop conditions
  6. Sibling-journal routing check (do not misfile)
  7. Anti-patterns
  8. Output format
  9. Supplementary resources
More from Awesome-Journal-Skills
All skills →
About this skill
What does the jpart-workflow skill do?

Use as the entry point for any Journal of Public Administration Research and Theory (JPART) manuscript. Routes to the right JPART sub-skill based on the lifecycle stage and forces the journal's defining test — a public-management theory contribution, not a bare empirical finding. It dispatches; it does not draft content.

How do I install it?

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