SkillAgentSearch skills...

amr-rebuttal

Use when writing the response document for an Academy of Management Review (AMR) Revise & Resubmit — structuring point-by-point replies that show the theory was genuinely strengthened, not just defended.

Install / Use

npx skills add brycewang-stanford/Awesome-Journal-Skills --skill amr-rebuttal

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

87/100

Supported Platforms

Universal

Our assessment of amr-rebuttal

amr-rebuttal scores 87/100 on our quality scale, 652nd of 1,156 Content & Media skills we index.

Its SKILL.md is 5.0 KB long, well organised into 8 sections with 2 code examples: a solid amount of guidance for an agent.

With 1,158 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
26/30
Structure
18/20
Description
15/15
Adoption
13/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so amr-rebuttal is actively maintained.
  • Our last check on 2026-10-11 found the source still online.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-10-04. Automated pattern scan on 2026-10-04. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

amr-rebuttal compared with similar skills

All 4 of these similar skills score higher than amr-rebuttal; compare them before choosing.

SkillScoreStarsUpdatedFormat
amr-rebuttal (this skill)by brycewang-stanford871.2k2mo agoSKILL.md
Claude-Code-Game-Studiosby Donchitos10039.9k8d agoCLAUDE.md
siyuanby siyuan-note10047.3ktodayMCP Server
x402by browser-use100121.0k4d agoSKILL.md
algorithmic-artby anthropics100177.9k56d agoSKILL.md

Frequently asked questions

How do I install amr-rebuttal?
Run npx skills add brycewang-stanford/Awesome-Journal-Skills --skill amr-rebuttal. The install tabs above show the steps for each supported agent.
Which AI agents does amr-rebuttal work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is amr-rebuttal safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is amr-rebuttal still maintained?
The repository was last updated about 2 months ago, so amr-rebuttal is actively maintained.

name: amr-rebuttal description: Use when writing the response document for an Academy of Management Review (AMR) Revise & Resubmit — structuring point-by-point replies that show the theory was genuinely strengthened, not just defended. Drafts the response; revise the manuscript's theory FIRST (amr-theory-development / amr-data-analysis) before writing the letter.

R&R Response Document (amr-rebuttal)

When to trigger

  • You have an AMR R&R (Major Revision) or a Reject & Resubmit you intend to pursue
  • The theory has been revised and you now need the response-to-reviewers document
  • You must adjudicate conflicting reviewer requests in writing

Revise the theory before you write the letter. A rebuttal that argues without changing the manuscript fails at AMR. Run amr-data-analysis and amr-theory-development first.

Structure of the response

  1. Opening to the editor. Thank the team; summarize the theoretical changes at a high level (new construct definitions, sharpened mechanism, added boundary conditions, clearer contribution). One short paragraph — substance, not flattery.
  2. Roadmap of major changes. A short list of the biggest theory moves you made, so the editor sees the revision's shape before the point-by-point.
  3. Point-by-point responses. For every reviewer comment, in order:
    • Restate the comment (verbatim or faithfully paraphrased).
    • State what you changed in the theory.
    • Quote or cite the revised manuscript location (section/proposition/page).
    • If you disagree, argue it on theoretical grounds — respectfully and with reasoning.
  4. Handling reviewer conflicts. When reviewers disagree, say so, explain your adjudication, and tie it to the editor's stated priorities.

How to respond well at AMR

  • Show, don't assert. "We strengthened the argument" is empty; point to the revised premise, the new mechanism, the added boundary condition.
  • Respond to theory comments with theory. The reviewers are theorists; a substance comment needs a substantive theoretical answer, not a wording tweak.
  • Never offer data. If a reviewer asks for "evidence," reframe within AMR's mission: strengthen the logical support, the mechanism, the boundary conditions, or the disconfirming-case treatment — not an empirical test.
  • Concede what is right. If a reviewer found a genuine logical gap, fix it and say so plainly. Graceful concession builds credibility for the points you do contest.
  • Defend the contribution explicitly if novelty was questioned — restate the before → after and the differentiation from the nearest prior theory, framed against Whetten's What/How/Why/Who-Where-When (AMR 1989, DOI 10.5465/amr.1989.4308371).
  • Sharpen constructs if distinctiveness was challenged — redefine with scope conditions per Suddaby's construct-clarity criteria (AMR 2010, DOI 10.5465/amr.2010.0419).
  • Keep the tone collegial. AMR review is developmental and typically runs multiple rounds, with the bar rising each round; the response should read as a conversation among theorists. (At AMR's empirical sibling AMJ, "we ran additional analyses and the result is robust" is a strong move; at AMR the equivalent strength comes from a tighter, more complete argument.)

Per-comment template

Comment R[n].[k]: [restated comment]
Response: [what changed in the theory + why]
Location: [Section X / Proposition Pn / p. Y]
[If contesting] Respectfully, we retain [X] because [theoretical reasoning].

Checklist

  • [ ] The manuscript's theory was actually revised before the letter was written
  • [ ] Every comment from every reviewer (and the editor) has a numbered response
  • [ ] Each response points to a concrete manuscript location
  • [ ] Theory-substance comments answered with theory, not wording
  • [ ] No response promises or adds empirical data
  • [ ] Reviewer conflicts adjudicated transparently and tied to the editor's priorities
  • [ ] Genuine concessions made where reviewers were right
  • [ ] Contribution re-defended if novelty was challenged
  • [ ] Tone collegial and developmental throughout

Anti-patterns

  • Arguing in the letter without changing the manuscript
  • "We thank the reviewer and have addressed this" with no concrete location or change
  • Answering a deep theoretical objection with a cosmetic edit
  • Promising data or "future empirical validation" as if it resolves a theory gap
  • Defensive or dismissive tone toward a reviewer's substantive point
  • Ignoring one reviewer to please another instead of adjudicating openly
  • Over-claiming the revision is "final" when AMR R&Rs typically run multiple rounds

Output format

【Decision being answered】R&R / Reject & Resubmit
【Theory revised first?】yes (summary of changes) / no → revise first
【Coverage】every editor+reviewer comment has a numbered response: yes/no
【Data offered?】must be: none
【Conflicts adjudicated】[...]
【Contribution re-defended】yes / n/a
【Next step】resubmit via ScholarOne → amr-review-process for the next round

Related Skills

View on GitHub
GitHub Stars1.2k
CategoryContent
Updated2mo ago
Forks153

Languages

Stata

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions