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 Literature Positioning

ASecurity

Use when positioning an American Political Science Review (APSR) manuscript against the literature so it reads as a discipline-wide contribution. APSR readers span subfields, so the paper must engage the literatures they expect and avoid the desk-rejection trigger of "failure to engage the relevant literatures." Stakes the contribution; it does not write the lit review.

1,052 stars
0 votes
0 copies
2 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-literature-positioning --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Apsr Literature Positioning?

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

Security grade badge for Apsr Literature Positioning
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/brycewang-stanford-apsr-literature-positioning/badge)](https://www.skillsdirectory.com/skills/brycewang-stanford-apsr-literature-positioning)

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

Download with Pro
Files
SKILL.md
---
name: apsr-literature-positioning
description: Use when positioning an American Political Science Review (APSR) manuscript against the literature so it reads as a discipline-wide contribution. APSR readers span subfields, so the paper must engage the literatures they expect and avoid the desk-rejection trigger of "failure to engage the relevant literatures." Stakes the contribution; it does not write the lit review.
---

# Literature Positioning (apsr-literature-positioning)

APSR's peer-review policy lists **"failure to engage the relevant literature(s)"** as an explicit
**desk-rejection** ground. Positioning is therefore not throat-clearing — it is survival. The goal is
to place the paper where a **general** political-science audience can see the gap and the move.

## When to trigger

- Drafting or revising the introduction and the "contribution" paragraph
- A reviewer said you "missed obvious work" or "don't engage the debate"
- Your subfield literature is solid but the paper doesn't connect to the broader discipline
- You need to distinguish your contribution from the closest prior papers

## How APSR wants the literature engaged

1. **Engage the debate, not a pile of citations.** Identify the live disagreement or open question
   your paper speaks to. Cite the works that *define* it, including across subfields where relevant.
2. **Two audiences at once.** Satisfy specialists (you know the frontier) *and* generalists (why it
   matters). The intro should make a comparativist care about an Americanist paper and vice versa.
3. **Name the gap precisely.** Not "little is known" — say what is contested, mismeasured,
   under-theorized, or untested, and why resolving it advances the field.
4. **Position the contribution as a move in the debate.** "Prior work argues X via mechanism M; we
   show M fails / is conditional on C / is better explained by M′."
5. **Pre-empt the obvious objection.** APSR reviewers are expert; acknowledge the strongest rival
   account and say how your design adjudicates it (hand off to `apsr-research-design`).

## Cross-subfield engagement (a distinctive APSR demand)

| If your paper is… | also engage… |
|-------------------|--------------|
| an empirical test of an institutional claim | the formal/theoretical literature generating the claim |
| a country/region case | the general comparative theory it speaks to |
| a measurement contribution | the substantive literatures that will use the measure |
| normative/theoretical | the empirical work the argument bears on, where applicable |

## Anti-patterns

- A "literature dump" with no organizing debate
- Engaging only your own subfield (a top APSR rejection reason)
- Strawmanning prior work, or hiding the closest competitor paper
- Self-citation that breaks anonymity (APSR is double-anonymous — see `apsr-submission`)
- Claiming "first to study" when the contribution is incremental

## Output format

```
【Debate】the live disagreement / open question
【Key works】the 3-6 that define it (incl. cross-subfield)
【Gap】what is contested / mismeasured / untested
【Move】how this paper changes the debate
【Strongest rival】and how the design will adjudicate it
【Next】apsr-theory-building
```

## Supplementary resources

- [`../../resources/official-source-map.md`](../../resources/official-source-map.md) — desk-rejection grounds incl. literature engagement

Attribution

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

Know which skills are safe — weekly.

Best new skills + every skill we flagged as malicious. From the team that scanned 103,619.

Join free

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

Know which skills are safe — weekly.

Best new skills + every skill we flagged as malicious. From the team that scanned 103,619.

Join free

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".

1074701 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', ...

693161 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.

691 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 →