pubar-review-process
Use when you need to understand how Public Administration Review (PAR) evaluates a manuscript — double-blind review, desk screening for fit/scope/practice-relevance, the reject / major / minor / accept decision spectrum, the role of Evidence for Practice, and the article types. Sets expectations and shapes the paper to survive review; it does not contact editors.
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill pubar-review-process --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.
# Review Process (pubar-review-process) Knowing how PAR screens and decides lets you pre-empt the failure modes before submitting. PAR is the **ASPA flagship**, edited by a team (Editors-in-Chief plus associate/handling editors), and runs **double-blind** peer review with a strong expectation that every article bridges research and practice. ## When to trigger - Before submitting, to stress-test a
What does the pubar-review-process skill do?
Use when you need to understand how Public Administration Review (PAR) evaluates a manuscript — double-blind review, desk screening for fit/scope/practice-relevance, the reject / major / minor / accept decision spectrum, the role of Evidence for Practice, and the article types. Sets expectations and shapes the paper to survive review; it does not contact editors.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill pubar-review-process --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.