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

Amj Rebuttal

ASecurity

Use when drafting the revision and response letter after an Academy of Management Journal (AMJ) revise-and-resubmit — structuring point-by-point responses to the action editor and reviewers across a multi-round developmental process. Drafts the response after revisions; it does not interpret the decision letter (amj-review-process).

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

Works with

cli

Security Analysis

A100/100

Scanned 6/4/2026

Install to Claude Code

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

Installs into .claude/skills of the current project.

Are you the author of Amj Rebuttal?

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

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

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

Download with Pro
Files
SKILL.md
---
name: amj-rebuttal
description: Use when drafting the revision and response letter after an Academy of Management Journal (AMJ) revise-and-resubmit — structuring point-by-point responses to the action editor and reviewers across a multi-round developmental process. Drafts the response after revisions; it does not interpret the decision letter (amj-review-process).
---

# R&R Response & Rebuttal (amj-rebuttal)

## When to trigger

- You received an AMJ R&R and have planned the revision (via `amj-review-process`)
- You have actually made (or scoped) the manuscript changes and need to write the response document
- You must reconcile conflicting reviewer demands for the action editor
- A later-round decision asks you to defend or further revise prior changes

> Write the response letter **after** revising the manuscript, not before. The letter documents changes you have made, not promises. AMJ's process is developmental and typically multi-round; resubmit the revised manuscript and response document through ScholarOne (mc.manuscriptcentral.com/AMJ), keeping the same action editor across rounds where possible, and remember the revised main body still must respect the **40-page limit** (text + references + appendices).

## Response-document structure

1. **Opening letter to the action editor.** Thank the editor and reviewers; summarize the most important changes in 2–4 sentences; explicitly state how you addressed the editor's stated priorities. Note where reviewers conflicted and how you resolved it.
2. **Per-reviewer sections.** For each reviewer, restate every comment verbatim (or faithfully numbered), then respond.
3. **Point-by-point format** for each comment:
   - **Comment** (quoted/numbered)
   - **Response** (what you did and the theoretical/methodological reasoning)
   - **Location** (section/page/table where the change appears)
   - Quote the new manuscript text where helpful.

## How to respond to AMJ's signature demands

- **"Deepen the theoretical contribution."** Strengthen the mechanism and the contribution sentences; show what the field now learns. Do not just add citations — revise the argument (see `amj-theory-development`, `amj-contribution-framing`).
- **"Strengthen the method / address endogeneity."** Add the identification strategy, robustness, or a supplementary study; report it and explain why it resolves the concern (see `amj-methods`, `amj-data-analysis`).
- **"Common-method bias."** Provide designed or additional evidence; if you cannot collect new data, give the strongest available statistical evidence and acknowledge residual risk as a boundary.
- **"Add a study."** If feasible, an experiment or replication that nails the mechanism is often the decisive move in the developmental process — but watch the 40-page budget: heavy new material often lives in an online supplement so the main body stays within limit.

## Tone and tactics

- **Be respectful and substantive.** Reviewers are colleagues investing in your paper; thank them and engage seriously, even when disagreeing.
- **Concede gracefully** where they are right; make the change.
- **Disagree with evidence, not assertion.** If you decline a request, give a theoretical or empirical reason and, where possible, an alternative analysis showing robustness.
- **Address every point.** Silent omissions read as evasion; a non-trivial point left unanswered can sink a revision.
- **Surface conflicts to the editor.** When reviewers ask for opposite things, explain the trade-off and your chosen resolution for the editor to adjudicate.
- **Keep it self-contained.** A reviewer should not have to hunt the manuscript to see what changed.

## Checklist

- [ ] Manuscript actually revised before the letter was written
- [ ] Editor's priorities addressed first and explicitly in the opening letter
- [ ] Every reviewer comment restated and answered (none skipped)
- [ ] Each response names the location of the change and quotes new text where useful
- [ ] Theory-contribution and method/endogeneity demands met with real changes, not citations only
- [ ] Declined requests are justified with evidence and, where possible, an alternative test
- [ ] Reviewer conflicts surfaced and resolved for the editor
- [ ] Tone is collegial and confident throughout

## Anti-patterns

- Writing the response before making the changes.
- Skipping or burying an inconvenient comment.
- Responding "we have added a citation" to a "deepen the theory" request.
- Defensive or dismissive tone toward reviewers.
- Declining a request with assertion ("we believe this is fine") and no evidence.
- Silently siding with one reviewer when two conflict, leaving the editor to discover it.

## Output format

```
【Decision round】1st R&R / 2nd round / ...
【Editor priorities addressed】1... 2... 3...
【Per-reviewer coverage】R1: x/x comments, R2: x/x, R3: x/x — all answered? yes/no
【Major changes】theory: ... method/data: ... new study: ...
【Declined requests + justification】[...]
【Reviewer conflicts resolved】...
【Response letter status】drafted / final
【Next step】resubmit via ScholarOne; on next decision → amj-review-process
```

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

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

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.

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 →