Video Understand
calesthio/OpenMontage
Understand video content locally using ffmpeg frame extraction and Whisper transcription.
A skill your agent uses 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 /…
MITAuto-check passed
Install Pubar Review Process
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill pubar-review-process -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills pubar-review-process --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/Public-Administration-Review-Skills/skills/pubar-review-process .claude/skills/pubar-review-process && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "pubar-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Public-Administration-Review-Skills/skills/pubar-review-process into .claude/skills/pubar-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pubar-review-process", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Public-Administration-Review-Skills/skills/pubar-review-processType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill pubar-review-process -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills pubar-review-process --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/Public-Administration-Review-Skills/skills/pubar-review-process .agents/skills/pubar-review-process && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "pubar-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Public-Administration-Review-Skills/skills/pubar-review-process into .agents/skills/pubar-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pubar-review-process", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill pubar-review-process -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills pubar-review-process --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/Public-Administration-Review-Skills/skills/pubar-review-process .cursor/skills/pubar-review-process && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "pubar-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Public-Administration-Review-Skills/skills/pubar-review-process into .cursor/skills/pubar-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pubar-review-process", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/brycewang-stanford/Awesome-Journal-Skills.git --path Public-Administration-Review-Skills/skills/pubar-review-process--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill pubar-review-process -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills pubar-review-process --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/Public-Administration-Review-Skills/skills/pubar-review-process .gemini/skills/pubar-review-process && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "pubar-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Public-Administration-Review-Skills/skills/pubar-review-process into .gemini/skills/pubar-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pubar-review-process", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills pubar-review-processInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill pubar-review-process -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/Public-Administration-Review-Skills/skills/pubar-review-process .github/skills/pubar-review-process && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "pubar-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Public-Administration-Review-Skills/skills/pubar-review-process into .github/skills/pubar-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pubar-review-process", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill pubar-review-process -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills pubar-review-process --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/Public-Administration-Review-Skills/skills/pubar-review-process .opencode/skills/pubar-review-process && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "pubar-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Public-Administration-Review-Skills/skills/pubar-review-process into .opencode/skills/pubar-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pubar-review-process", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
pubar-review-process- GitHub stars
- 1.2k
- Token cost
- ~1.4k tokens
- SKILL.md length
- 598 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses 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 /…
- Works in 5 steps: Double-blind. Reviewers do not know the… → Editorial desk screening first. The… → External review. Papers passing the desk… → …
- You need to understand how Public Administration Review (PAR) evaluates a manuscript — double-blind review
- SKILL.md covers When to trigger, How PAR review works (verify…, Shape the paper to pass and Anti-patterns, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Pubar Review Process is an agent skill from brycewang-stanford/Awesome-Journal-Skills. 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.
Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: Journal-specific Claude Code/Codex skill packs covering mainstream journals — AER, QJE, Nature, Cell, 管理世界, 经济研究 & 200+ more — your fast track to getting published. ｜ 覆盖主流期刊的… The licence is MIT.
When your agent uses it
- 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
Example prompts
- “/pubar-review-process”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Double-blind. Reviewers do not know the authors and authors do not know reviewers. Anonymize the
- Editorial desk screening first. The editorial team screens for fit and scope (is it public
- External review. Papers passing the desk go to expert public-management reviewers.
- Decision spectrum: typically reject / major revision / minor revision / accept. The handling
- Article-type routing. Scholarly Takes, Conceptualizing PA, Early Career Intel, and Practically
What it can do on your machine
Read from SKILL.md and the folder at commit 932eb23. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Pubar Review Process loads about 1.4k tokens when it runs. Until then it costs about 97 tokens; SKILL.md has 598 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from brycewang-stanford/Awesome-Journal-Skills at commit 932eb23, republished under its MIT licence (© brycewang-stanford). 598 words, ~1,370 tokens.
Download SKILL.mdSave it as
.claude/skills/pubar-review-process/SKILL.md (or your agent's skills folder).- name
- pubar-review-process
- description
- 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.
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 against desk-rejection grounds
- Choosing the right article type for the route through review
- Interpreting a decision letter and setting expectations
- Understanding what reviewers are instructed to weigh
How PAR review works (verify current specifics on the official page)
- Double-blind. Reviewers do not know the authors and authors do not know reviewers. Anonymize the
manuscript accordingly (see
pubar-submission). - Editorial desk screening first. The editorial team screens for fit and scope (is it public administration, broadly significant, and does it bridge to practice?), basic rigor, and completeness (incl. an abstract ≤ 150 words and, by revision, Evidence for Practice). Off-fit or niche papers can be returned without external review.
- External review. Papers passing the desk go to expert public-management reviewers.
- Decision spectrum: typically reject / major revision / minor revision / accept. The handling editor weighs reviews; the bar is a credible scholarly contribution and a defensible practitioner takeaway.
- Article-type routing. Scholarly Takes, Conceptualizing PA, Early Career Intel, and Practically Speaking pieces are evaluated against the expectations of their type.
Shape the paper to pass
- Make field-wide PA significance explicit (avoids the "too niche for the flagship" screen).
- Make the practitioner so-what real, not decorative — the Evidence for Practice must follow from the analysis.
- Confirm the paper is PAR-shaped, not JPART/JPAM-shaped (broad + practice-bridging, not pure theory or policy analysis).
- Clear ethics/IRB and human-subjects compliance up front; prepare TOP transparency materials early.
- Write to expert reviewers: anticipate the strongest objection and answer it in the design.
Anti-patterns
- Submitting a pure-theory paper to a practice-bridging flagship (fit screen; try JPART)
- Submitting a policy cost-benefit analysis with no administration contribution (try JPAM)
- A niche study with no field-level significance or honest practitioner stake
- Treating Evidence for Practice as optional boilerplate
Output format
【Desk-screen check】fit / scope / practice-relevance — any red flags?
【Significance】field-wide PA, not niche? [Y/N]
【Practitioner so-what】honest and analysis-backed? [Y/N]
【Article type】Scholarly Take / Conceptualizing PA / Early Career Intel / Practically Speaking
【Realistic outcome】reject / major / minor / (rare) accept
【Next】pubar-submission (or pubar-rebuttal if decided)Show full SKILL.md (257 more words)Show less
What PAR reviewers weigh, by question type
The handling editor and reviewers read each submission against the expectations of its article type and against PAR's research-and-practice mission. Calibrate to whichever lens is decisive, but expect both the scholarly and the practitioner lens to be in the room.
| What the paper claims | The check a PAR referee runs first | The fix that earns the benefit of the doubt |
|---|---|---|
| A causal effect of a reform | Does the design license the causal word — and the policy advice? | State estimand + assumption; sensitivity analysis; scope the takeaway |
| A behavioral effect (experiment) | Is it pre-registered, powered, and realistic for public servants/citizens? | Pre-registered estimand, MDE, realistic task, randomization inference |
| A new construct / measure | Is it valid, reliable, and distinct from neighbors? | Construct validation, reliability, discriminant evidence |
| A conceptual reframing | Does it change what empirical scholars must now account for? | A portable concept with observable implications, not a relabel |
| A practitioner takeaway | Does the Evidence for Practice follow from the analysis? | Tie each point to a confirmatory estimate, not an exploratory one |
Calibration anchors (hedged)
- The bar is field-wide PA significance plus honest practice relevance; a niche result with no practitioner stake rarely clears the desk at the field's flagship.
- PAR practices methodological breadth — a rigorous qualitative or mixed-methods study is not second-class to a regression. Match the inference standard to the design.
- Exact decision-category language, desk-screen criteria, and the editorial team can change — confirm against the journal's current guidelines before relying on them (检索于 2026-06；以官网为准).
Supplementary resources
../../resources/official-source-map.md— peer-review model, article types, editorial team
© brycewang-stanford, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in Public-Administration-Review-Skills/skills/pubar-review-process of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Pubar Review Process next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Pubar Review Process this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.4k | Automated safety check: Pass | MIT | |
| Video Understandcalesthio/OpenMontage | 66k | — | ~841 | Automated safety check: Pass | AGPL-3.0 | |
| Understand ExplainEgonex-AI/Understand-Anything | 86k | — | ~1.3k | Automated safety check: Pass | MIT | |
| Understanding by Design PlannerTHU-MAIC/OpenMAIC | 40k | — | ~548 | Automated safety check: Pass | MIT | |
| Understand Diff AnalysisEgonex-AI/Understand-Anything | 86k | — | ~1.4k | Automated safety check: Pass | MIT | |
| Understand Issuemastra-ai/mastra | 29k | — | ~3.1k | Automated safety check: Pass | Custom licence |
Similar skills
Understand Explain
Egonex-AI/Understand-Anything
Gives an in-depth explanation of one file, function or module by reading the project's knowledge graph and checking that the graph is still fresh.
Understanding by Design Planner
THU-MAIC/OpenMAIC
Plans an OpenMAIC lesson or course series by backward design: enduring understandings and essential questions first, then performance evidence, then learning activities.
Understand Diff Analysis
Egonex-AI/Understand-Anything
Reads your git changes or a pull request against a prebuilt knowledge graph of the project to explain what changed, which components are affected and what is risky.
Understand Issue
mastra-ai/mastra
Investigate a GitHub issue or reported bug the way a seasoned maintainer would — form an independent model before reading the thread's theories, trace the mechanism and history, verify the…
Understand PR
mastra-ai/mastra
Review a PR the way a seasoned maintainer would — build an independent model before seeing the diff, investigate the implementation and history, verify material claims, and return a concise briefing.
More from brycewang-stanford/Awesome-Journal-Skills
All 2,387 skills in this repoAaag Data Analysis
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when running and reporting the analysis for an Annals of the American Association of Geographers manuscript — spatial statistics and modeling, remote-sensing accuracy, or…
Aaag Literature Positioning
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when positioning an Annals of the American Association of Geographers manuscript in the literature — engaging geographic scholarship across the relevant area and the…
Aaag Rebuttal
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when responding to an Annals of the American Association of Geographers decision letter (major/minor revision) — building a point-by-point response to the subject editor and…
Aaag Research Design
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when defending the research design of an Annals of the American Association of Geographers manuscript — spatial/quantitative analysis and GIScience, remote-sensing and…
Aaag Review Process
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when you need to understand how the Annals of the American Association of Geographers evaluates a manuscript — double-anonymous review routed through a subject editor by…
Aaag Submission
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when running the final pre-submission preflight for the Annals of the American Association of Geographers via ScholarOne Manuscripts — area/article-type selection…
Questions about Pubar Review Process
What does Pubar Review Process do?
A skill your agent uses 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 /…. Pubar Review Process is an agent skill from brycewang-stanford/Awesome-Journal-Skills. 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.
When should I use Pubar Review Process?
Pubar Review Process fits situations like: 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.
How do I install Pubar Review Process in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill pubar-review-process -a claude-code`. Or copy the skill folder (Public-Administration-Review-Skills/skills/pubar-review-process in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/pubar-review-process in your project. Claude Code loads it when a task matches its description.
How do I install Pubar Review Process in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill pubar-review-process -a codex`. Or copy the skill folder (Public-Administration-Review-Skills/skills/pubar-review-process in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/pubar-review-process in your project. Codex loads it when a task matches its description.
Can I use Pubar Review Process in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill pubar-review-process -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/pubar-review-process, .gemini/skills/pubar-review-process, .github/skills/pubar-review-process and .opencode/skills/pubar-review-process in your project.
What does Pubar Review Process need to run?
SKILL.md names no scripts, command-line tools or credentials: Pubar Review Process is instructions for the agent only.
Does Pubar Review Process access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Pubar Review Process safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Pubar Review Process use?
Pubar Review Process is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Pubar Review Process use?
About 1.4k tokens (SKILL.md is roughly 5.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Pubar Review Process?
Skills that share tags, products or a category with Pubar Review Process: Video Understand (calesthio/OpenMontage, 66k stars), Understand Explain (Egonex-AI/Understand-Anything, 86k stars), Understanding by Design Planner (THU-MAIC/OpenMAIC, 40k stars) and Understand Diff Analysis (Egonex-AI/Understand-Anything, 86k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Pubar Review Process?
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,228 GitHub stars. The repository holds 2,387 skills in this directory. The repository was last updated on September 27, 2026.
Source: brycewang-stanford/Awesome-Journal-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.