Agent skill · Code Review & Quality

respol-review-process

Use when calibrating expectations and choreography for the Research Policy (RP) review cycle — the double-blind process, the out-of-scope desk screen, handling-editor routing, the Research Note option, and what RP referees reward versus reject. Sets expectations; it does not draft the response letter (respol-rebuttal).

brycew6m878★ · +32/wk · 1 repos on radarProfile →
claude-codeMIT
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill respol-review-process --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: Research-Policy-Skills/skills/respol-review-process/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

# Review Process (respol-review-process) ## When to trigger - You want realistic odds and timelines before or after submitting to RP - A desk reject arrived and you need to read whether it was scope, contribution, or fit - You are deciding whether to position the work as a full article or a Research Note - A decision letter arrived (reject / major / minor) and you need to plan, not yet write, the response - You are weighing transfer to a sibling (ICC, Technovation, JPIM) after an RP rejection ## How Research Policy review actually works RP runs a **double-blind** process (检索于 2026-06;以官网为准): the Editor-in-Chief routes a submission to a **Handling Editor** matched to its area (innovation systems, science/technology policy, entrepreneurship and innovation, university-industry interactions, R&D management, or innovation methodology), who manages the referees and the decision. Before referees, there is a **desk screen** that tests two things: whether the paper is genuinely innovation studies (the out-of-scope filter for econ/management-only papers) and whether the substantive contribution is plausible. Surviving that, expect a small number of expert referees and the standard reject / m

What's inside
Steps it walks through
  1. When to trigger
  2. How Research Policy review actually works
  3. What RP referees reward vs. punish
  4. Reading the decision letter and planning the cycle
  5. When to consider a sibling instead
  6. Checklist
  7. Anti-patterns
  8. Output format
More from Awesome-Journal-Skills
All skills →
About this skill
What does the respol-review-process skill do?

Use when calibrating expectations and choreography for the Research Policy (RP) review cycle — the double-blind process, the out-of-scope desk screen, handling-editor routing, the Research Note option, and what RP referees reward versus reject. Sets expectations; it does not draft the response letter (respol-rebuttal).

How do I install it?

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

Keep going