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).
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.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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
- When to trigger
- How Research Policy review actually works
- What RP referees reward vs. punish
- Reading the decision letter and planning the cycle
- When to consider a sibling instead
- Checklist
- Anti-patterns
- Output format
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.