Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsCommunityBlog
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Apsr Review Process

ASecurity

Use to understand how the American Political Science Review (APSR) evaluates a manuscript — double-anonymous review, desk-rejection screening (remit / ethics / substance), the reject / accept / revise-and-resubmit decision categories, editor discretion, and the Registered Reports route. Sets expectations and shapes the paper to survive review; it does not contact editors.

1,052 stars
0 votes
0 copies
0 views
Added 6/4/2026
ai-agentsgo

Security Analysis

A100/100

Scanned 6/4/2026

Install to Claude Code

$npx -y skills add brycewang-stanford/Awesome-Journal-Skills --skill apsr-review-process --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Apsr Review Process?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Apsr Review Process
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/brycewang-stanford-apsr-review-process/badge)](https://www.skillsdirectory.com/skills/brycewang-stanford-apsr-review-process)

More formats (shields.io, HTML) on the badges page.

Download with Pro
Files
SKILL.md
---
name: apsr-review-process
description: Use to understand how the American Political Science Review (APSR) evaluates a manuscript — double-anonymous review, desk-rejection screening (remit / ethics / substance), the reject / accept / revise-and-resubmit decision categories, editor discretion, and the Registered Reports route. Sets expectations and shapes the paper to survive review; it does not contact editors.
---

# Review Process (apsr-review-process)

Knowing how APSR screens and decides lets you pre-empt the failure modes before submitting. APSR is
**double-anonymous** and screens hard at the desk before external review.

## When to trigger

- Before submitting, to stress-test against desk-rejection grounds
- Deciding whether to use the **Registered Reports** (Stage 1) route
- Interpreting a decision letter and setting expectations
- Understanding what reviewers are instructed to weigh

## How APSR review works

1. **Double-anonymous.** Reviewers do not know the authors and authors do not know reviewers.
   Anonymize the manuscript accordingly (see `apsr-submission`).
2. **Desk screening first.** Every paper is considered for **desk rejection** on three grounds:
   - **Remit** — not research, not political science, out of scope, or not in adequate English.
   - **Ethics** — plagiarized/unattributed text, or research based on unethical procedures.
   - **Substance** — missing a key element of an article, insufficiently significant findings, or
     **failure to engage the relevant literature(s)**.
   - *Substantive* desk rejections require **at least two editors** to agree.
3. **External review.** Papers passing the desk are sent to expert reviewers.
4. **Decision categories**: **reject**, **accept**, or **revise and resubmit** — where **R&R is
   reserved for papers very close to publishable quality**. Strong support from **all or nearly all**
   reviewers is generally necessary, but the decision is **at the editor's discretion**.
5. **Review transfer.** Anonymized manuscripts/reviews may be forwarded only to journals that also use
   double-anonymous protocols (an opt-in initiative).

## Registered Reports route (prospective designs)

- Submit a **Stage 1** package — theory, design, and analysis plan — that is reviewed **before** data
  collection/analysis. In-principle acceptance commits the journal to publish regardless of results if
  you execute the plan. Choose this **before** you have results (see `apsr-topic-selection`).

## Shape the paper to pass

- Make general significance explicit (avoids "insufficiently significant" desk rejection).
- Engage the relevant literatures, including across subfields (avoids the literature desk-rejection).
- Clear ethics/IRB and human-subjects compliance up front.
- Write to expert reviewers: anticipate the strongest objection and answer it in the design.

## Anti-patterns

- Submitting a subfield-only paper to a discipline-wide journal (substance desk rejection)
- Ignoring an obvious related literature (explicit desk-rejection ground)
- Expecting an R&R for a paper that is far from publishable — R&R is for near-ready papers
- Choosing Registered Reports after results exist

## Output format

```
【Desk-rejection check】remit / ethics / substance — any red flags?
【Significance】general enough to clear "insufficiently significant"? [Y/N]
【Literature engaged】incl. cross-subfield? [Y/N]
【Track】standard vs Registered Reports (Stage 1)
【Realistic outcome】reject / R&R / (rare) accept
【Next】apsr-submission (or apsr-rebuttal if decided)
```

## Supplementary resources

- [`../../resources/official-source-map.md`](../../resources/official-source-map.md) — peer-review policy, desk-rejection grounds, decision categories, Registered Reports

Attribution

brycewang-stanfordbrycewang-stanford
View sourceMore from brycewang-stanford →
SSkills DirectorySkills Directory

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

Related Skills

Caveman

Ultra-compressed communication mode that cuts output tokens while keeping technical accuracy. Levels: lite, full, ultra and the wenyan variants. Use for /caveman, "caveman mode", "talk like caveman", "be brief" or "less tokens".

1066601 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

686011 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3351 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

651 votes

math-skill

A comprehensive mathematical reasoning skill for AI assistants — handles arithmetic to research-level problems with rigorous step-by-step reasoning, systematic verification, and transparent uncertainty handling

381 votes
View all in ai-agents →