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

Sf Rebuttal

ASecurity

Use when writing the response to a Social Forces (SF) revise-and-resubmit. SF reviewers prize methodological rigor and general significance, and most published papers go through at least one R&R, so the response must convert each reviewer without alienating the editor — all while keeping the revision within the reference-inclusive 10,000-word and 10-panel limits. Structures the response letter; it does not fabricate new results.

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

Works with

api

Security Analysis

A100/100

Scanned 6/6/2026

Install to Claude Code

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

Installs into .claude/skills of the current project.

Are you the author of Sf Rebuttal?

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

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

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

Download with Pro
Files
SKILL.md
---
name: sf-rebuttal
description: Use when writing the response to a Social Forces (SF) revise-and-resubmit. SF reviewers prize methodological rigor and general significance, and most published papers go through at least one R&R, so the response must convert each reviewer without alienating the editor — all while keeping the revision within the reference-inclusive 10,000-word and 10-panel limits. Structures the response letter; it does not fabricate new results.
---

# R&R Rebuttal (sf-rebuttal)

A Social Forces **R&R is the normal road to publication** — most accepted papers pass through one. The
response letter must move *every* reviewer toward yes while keeping the editor confident the revision is
convergent. The SF-specific twist: each new analysis or paragraph you add must still fit the
**10,000-word cap (references included)** and the **10 tables-and-figure-panels** limit, so you often
trade content rather than simply add it.

## 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 push you over the word or panel limits
- 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; 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/panel number), or push back **respectfully with a reason** (theory, design, or
   evidence). A well-argued disagreement beats 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.
5. **Mind the budget when you add.** New robustness tables count against the **10-panel** limit; new
   prose and citations count against the **reference-inclusive 10,000-word** cap. Move supporting
   material to the supplementary file (≤ 10 pages) and consolidate exhibits (see `sf-tables-figures`,
   `sf-writing-style`).
6. **Protect the contribution and the rigor.** Add checks that strengthen credibility; resist changes
   that dilute the general-significance claim that earned the R&R. Keep the revision **anonymized** and
   **update the data availability statement / materials** so new exhibits remain reproducible (see
   `sf-data-and-transparency`).

## Response-letter format

For each reviewer comment:

```
> [Quoted reviewer comment]

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

Open with a short **summary of the main changes** to the editor; group by reviewer; end each entry with
the location of every change so the editor can verify quickly. Note where added material went to the
supplement to stay within the word and panel caps.

## Anti-patterns

- Ignoring or merging away a comment without a visible response
- Adding so much that the revision blows the 10,000-word (incl. refs) or 10-panel limits
- Capitulating to a request that breaks the paper's logic just to please a reviewer
- Defensive or dismissive tone toward reviewers
- Letting the revised manuscript or new exhibits drift out of sync with the declared data/code

## 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]
【Budget after revision】≤ 10,000 words (incl. refs) and ≤ 10 panels? [Y/N]
【Anonymity + data statement updated】[Y/N]
【Next】resubmit via ScholarOne
```

## Supplementary resources

- [`../../resources/official-source-map.md`](../../resources/official-source-map.md) — review model, decision norms, and length/exhibit caps

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 →