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

Restud Rebuttal

ASecurity

Use when a referee report or R&R has arrived for a The Review of Economic Studies (REStud) manuscript and a point-by-point response letter plus aligned manuscript revisions are needed. Structures the revision and the letter; does not redo the science from scratch.

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

Works with

cli

Security Analysis

A100/100

Scanned 6/6/2026

Install to Claude Code

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

Installs into .claude/skills of the current project.

Are you the author of Restud Rebuttal?

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

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

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

Download with Pro
Files
SKILL.md
---
name: restud-rebuttal
description: Use when a referee report or R&R has arrived for a The Review of Economic Studies (REStud) manuscript and a point-by-point response letter plus aligned manuscript revisions are needed. Structures the revision and the letter; does not redo the science from scratch.
---

# REStud Rebuttal (restud-rebuttal)

## When to trigger

- A decision letter with referee reports has arrived (R&R, or reject-and-resubmit)
- The user has a revised draft and needs the response letter
- The user is unsure which comments to concede, clarify, or push back on
- Multiple referees disagree and the response must reconcile them without contradiction

## REStud revision philosophy

REStud is known for **developing strong papers across rounds** with demanding referees. Treat the R&R as a collaboration, not a defense: the editor wants the paper to become publishable. The strongest response **revises the manuscript first, then writes the letter against the revised version** — never the other way around. Two REStud-specific facts to plan for: (1) review is **double-anonymous**, so address "Referee 2" by number and keep replies anonymizable; (2) acceptance is conditional on the **Data Editor's pre-publication reproducibility check** (AEA DCAS, Zenodo deposit — see `restud-replication-package`), so a revision that adds empirical results must keep the replication package in lockstep — do not promise a number you cannot regenerate from the deposit. Push new proofs and bulky robustness into the **online appendix** and point to them from the letter.

## Triage every comment

Classify each referee point into one of four actions:

1. **Concede + fix.** The referee is right; make the change and say so plainly. Most comments are this. Conceding gracefully builds credibility for the few points you contest.
2. **Clarify.** The referee misread because the text was unclear. Fix the text so the *next* reader does not misread, then explain the clarification. Do not just say "the referee misunderstood" — that blames the reader.
3. **Push back (rarely).** The referee is wrong on substance. Push back only with evidence — a citation, a new result, a proof — and only on points that matter. Pick these battles sparingly.
4. **Decline (rarely, with reason).** A request is out of scope or would change the paper into a different paper. Decline respectfully, explain why, and offer the smaller version of what they want if possible.

## The response letter

Structure:

- **Cover note to the editor.** Thank the editor, summarize the main changes in a short paragraph, and flag any place where referees disagreed and how you reconciled them.
- **Per-referee sections.** For each referee, restate each comment (quoted or paraphrased faithfully), then the response: the action taken and **the exact location in the revised manuscript** (section, page, table number).
- **Tone:** professional, specific, non-defensive. Every "we have done X" must point to where.

Format each response as:

```
Comment R2.3: "[faithful quote of the referee's point]"
Response: We agree / We have clarified / We respectfully note ...
Change: [what changed] — see Section 4.2, p. 14, and new Table 5.
```

## Reconciling conflicting referees

When two referees want opposite things, do not silently satisfy one and ignore the other. State the tension to the editor, choose the resolution that serves the paper, and explain the choice. The editor adjudicates — give them what they need to back you.

## Checklist

- [ ] Manuscript revised *before* the letter was written
- [ ] Every comment triaged (concede / clarify / push back / decline)
- [ ] Each response cites the exact revised location (section, page, exhibit)
- [ ] Push-backs are evidence-backed and few
- [ ] Declines are respectful and offer a smaller alternative
- [ ] Conflicting referee requests reconciled explicitly for the editor
- [ ] Tone professional and non-defensive throughout

## Anti-patterns

- Writing the letter against the old draft, so "see p. 14" points to the wrong place
- "The referee misunderstood" with no text fix — blaming the reader
- Pushing back on many points; it reads as unwillingness to revise
- Conceding a point in the letter but not actually changing the manuscript
- Silently ignoring one of two conflicting referees
- A letter that argues the paper's importance instead of answering the comments

## Output format

```
【DECISION TYPE】R&R | reject-and-resubmit | minor revision
【COMMENTS TRIAGED】concede X / clarify Y / push-back Z / decline W
【MANUSCRIPT REVISED FIRST】yes / no
【CONFLICTS RECONCILED】[...]/none
【LETTER STATUS】drafted with exact-location cites
【NEXT SKILL】restud-submission (resubmit) | restud-robustness (if new results needed)
```

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 →