Agent skill · Code Review & Quality

io-review-process

Use to understand how International Organization (IO) evaluates a manuscript — double-blind peer review, expert IR referees, anonymous reviews returned to the author, the decision and revise-and-resubmit process, and IO's distinctive verification of quantitative results and formal proofs before final acceptance. Sets expectations and shapes the paper to survive review; it does not contact editors.

brycew6m878★ · +32/wk · 1 repos on radarProfile →
claude-codeMIT
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill io-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: 6 KB
Bundled scripts: none
Path: International-Organization-Skills/skills/io-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 (io-review-process) Knowing how IO screens, reviews, and verifies lets you pre-empt the failure modes before submitting. IO is **double-blind**, reviewed by expert international-relations referees, and — distinctively — **verifies your quantitative results and formal-model proofs before final acceptance**. ## When to trigger - Before submitting, to stress-test against the likely IR objections - Interpreting a decision letter and setting expectations - Understanding what happens between conditional and final acceptance (verification) - Planning the revision timeline around the verification step ## How IO review works 1. **Double-blind.** Reviewers do not know the authors and authors do not know reviewers. Anonymize the manuscript and use **third-person self-citation** (see `io-submission`). 2. **Editorial screening.** Editors assess fit first: is the international/cross-border phenomenon a **major cause or effect**, and does the paper offer a **generalizable IR theory**? Papers that are really domestic-politics, or descriptive single-case accounts, are at risk early. 3. **Expert IR review.** Manuscripts go to expert referees (commonly two or more); their **reviews a

What's inside
Steps it walks through
  1. When to trigger
  2. How IO review works
  3. Shape the paper to pass
  4. Desk-screen failure patterns (where IO papers die first)
  5. What an expert IR referee actually scores
  6. Anti-patterns
  7. Output format
  8. Supplementary resources
More from Awesome-Journal-Skills
All skills →
About this skill
What does the io-review-process skill do?

Use to understand how International Organization (IO) evaluates a manuscript — double-blind peer review, expert IR referees, anonymous reviews returned to the author, the decision and revise-and-resubmit process, and IO's distinctive verification of quantitative results and formal proofs before final acceptance. 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 io-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