Skip to content
Content
Skill

/amj-rebuttal

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

From plugin
awesome-journal-skills
965200 skills
Install
$ npx -y skills add brycewang-stanford/Awesome-Journal-Skills --skill amj-rebuttal --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/amj-rebuttal

Context preview

The summary Claude sees to decide when to auto-load this skill.

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

SKILL.md

amj-rebuttal.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
Read more
Ships withawesome-journal-skills

Stanford REAP × CoPaper.AI · 由斯坦福实证方法论团队精选与维护 访问 copaper.ai 微信:CoPaper.AI 按 11 个主流学科板块覆盖 经管与商科 社会科学 人文学科 数学与物理科学 生命科学 医学与健康 工程与技术 计算机科学与 AI 体育科学 点击任一学科名可跳转到对应说明;每类下的代表子领域在正文总览中完整列出。下方封面墙按 venue 导航,完整分类见覆盖一览。 🧭 布局指南 · 📚 Skill Pack 一览 · ⚡ 如何使用 · 🧪 自动实证

Get the whole plugin
Stats
965
Stars
121
Forks
Active
Maintenance
Stata
Language
MIT
License
13h ago
Last commit
2mo ago
Created

Repo: brycewang-stanford/Awesome-Journal-Skills

Other skills on awesome-journal-skills.