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

Aerj Rebuttal

ASecurity

Use when writing the response to an American Educational Research Journal (AERJ) revise-and-resubmit. AERJ R&Rs come back through the section editor (SIA or TLHD) and multiple masked reviewers, so the response must convert each reviewer while keeping the editor confident the revision is convergent. 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 aerj-rebuttal --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Aerj Rebuttal?

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

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

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

Download with Pro
Files
SKILL.md
---
name: aerj-rebuttal
description: Use when writing the response to an American Educational Research Journal (AERJ) revise-and-resubmit. AERJ R&Rs come back through the section editor (SIA or TLHD) and multiple masked reviewers, so the response must convert each reviewer while keeping the editor confident the revision is convergent. Structures the response letter; it does not fabricate new results.
---

# R&R Rebuttal (aerj-rebuttal)

An AERJ **R&R is a strong signal** — but acceptance generally needs the **section editor** satisfied
and the **reviewers** moved toward yes. The response letter must address every comment, defend the
contribution, and keep the revision coherent. The editor adjudicates; reviewers advise.

## 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 or reframing that would change the paper's claims
- Writing the cover note to the section editor summarizing the revision

## Strategy

1. **Read the editor's letter as the rubric.** The section editor (SIA or TLHD) 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 number), or push back **respectfully with a reason** (framework, 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. Don't silently satisfy one and ignore the
   other.
5. **Protect the contribution.** Add robustness, clarify scope, strengthen the framework — but resist
   changes that dilute the broad-significance claim that earned the R&R. Defend scope conditions rather
   than over-claiming.
6. **Keep masking and standards intact.** The revised manuscript stays **anonymized**; update analyses,
   exhibits, and the data/reporting materials so everything remains reproducible and standards-compliant
   (see `aerj-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 section editor; group by reviewer; end each
per-comment entry 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 exhibits drift out of sync with the data/reporting materials, or
  reintroducing identifying details that break masking

## 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 the section editor? [Y/N]
【Contribution protected】no dilution of broad significance? [Y/N]
【Masking + materials updated】[Y/N]
【Next】resubmit via ScholarOne Manuscript Central
```

## Supplementary resources

- [`../../resources/official-source-map.md`](../../resources/official-source-map.md) — masked review, sections, and decision categories
- [`../../resources/external_tools.md`](../../resources/external_tools.md) — reporting standards and reproducibility tooling for the revision

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 →