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 Rebuttal

ASecurity

Use when writing the response to an American Political Science Review (APSR) revise-and-resubmit. APSR reserves R&R for papers close to publishable, and decisions weigh strong support from all or nearly all reviewers, so the response must convert each reviewer without alienating the editor. Structures the response letter; it does not fabricate new results.

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

Works with

api

Security Analysis

A100/100

Scanned 6/4/2026

Install to Claude Code

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

Installs into .claude/skills of the current project.

Are you the author of Apsr Rebuttal?

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

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

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

Download with Pro
Files
SKILL.md
---
name: apsr-rebuttal
description: Use when writing the response to an American Political Science Review (APSR) revise-and-resubmit. APSR reserves R&R for papers close to publishable, and decisions weigh strong support from all or nearly all reviewers, so the response must convert each reviewer without alienating the editor. Structures the response letter; it does not fabricate new results.
---

# R&R Rebuttal (apsr-rebuttal)

An APSR **R&R is a strong signal** — it is "reserved for papers very close to publishable quality."
But publication generally needs **strong support from all or nearly all reviewers**, and the call is
the **editor's discretion**. So the response letter must move *every* reviewer toward yes while
keeping the editor confident the revision is convergent.

## When to trigger

- An R&R decision arrived and you are planning the revision + response letter
- Reviewers disagree with each other and you must reconcile their demands
- A reviewer requests analyses that would change the paper's claims
- Writing the cover note to the editor summarizing the revision

## Strategy

1. **Read the editor's letter as the rubric.** The editor signals which points are decisive. Solve
   those first and foremost; the editor adjudicates disagreements among reviewers.
2. **One point-by-point response, every comment addressed.** Quote each comment, then respond. Never
   skip one — silence reads as non-compliance.
3. **Concede or rebut explicitly, with evidence.** For each: did what was asked (say where, with the
   new text/table number), or push back **respectfully with a reason** (theory, design, or evidence).
   Editors respect a well-argued disagreement more than a hollow capitulation that weakens the paper.
4. **Reconcile conflicting reviewers openly.** When R2 wants the opposite of R3, say so, choose a
   principled path, and explain the tradeoff to the editor. Don't silently satisfy one and ignore the
   other.
5. **Protect the contribution.** Add robustness and clarifications; resist changes that dilute the
   general-significance claim that earned the R&R. Defend scope conditions rather than over-claiming.
6. **Keep anonymity intact** in the revised manuscript (still double-anonymous), and **update the
   reproducibility package** so new tables/figures remain reproducible (see
   `apsr-transparency-and-data-policy`).

## Response-letter format

For each reviewer comment:

```
> [Quoted reviewer comment]

Response: [What we did / why we respectfully disagree].
Change: [Section/page/table-figure number where the revision appears].
```

Open with a short **summary of the main changes** to the editor; group by reviewer; end the per-comment
entries with the location of every change so the editor can verify quickly.

## Anti-patterns

- Ignoring or merging away a comment without a visible response
- Capitulating to a request that breaks the paper's logic just to please a reviewer
- Defensive or dismissive tone toward reviewers
- "We thank the reviewer" with no actual change or argued reason
- Adding analyses that quietly contradict the original claim without acknowledging it
- Letting the revised manuscript or new exhibits drift out of sync with the deposited package

## Output format

```
【Editor's decisive points】addressed first? [list]
【Coverage】every reviewer comment answered? [Y/N]
【Concede vs rebut】each tagged with evidence + change location
【Reviewer conflicts】reconciled and explained to editor? [Y/N]
【Contribution protected】no dilution of general significance? [Y/N]
【Anonymity + package updated】[Y/N]
【Next】resubmit via Editorial Manager
```

## Supplementary resources

- [`../../resources/official-source-map.md`](../../resources/official-source-map.md) — R&R/decision categories and editor-discretion policy

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 →