amr-review-process
Use when you need to understand the Academy of Management Review (AMR) developmental, multi-round review and interpret a decision letter focused on theoretical novelty and logical soundness. Explains the process and decision types; it does NOT draft the response document (that is amr-rebuttal).
Install / Use
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill amr-review-processInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Content & MediaSupported Platforms
Our assessment of amr-review-process
amr-review-process scores 85/100 on our quality scale, 816th of 1,156 Content & Media skills we index.
Its SKILL.md is 5.4 KB long, well organised into 9 sections with 1 code example: 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.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so amr-review-process is actively maintained.
- Our last check on 2026-11-05 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 foundOur 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-review-process compared with similar skills
All 4 of these similar skills score higher than amr-review-process; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| amr-review-process (this skill)by brycewang-stanford | 85 | 1.2k | 2mo ago | SKILL.md |
| Claude-Code-Game-Studiosby Donchitos | 100 | 39.9k | 8d ago | CLAUDE.md |
| siyuanby siyuan-note | 100 | 47.3k | today | MCP Server |
| x402by browser-use | 100 | 121.0k | 4d ago | SKILL.md |
| algorithmic-artby anthropics | 100 | 177.9k | 56d ago | SKILL.md |
Frequently asked questions
- How do I install amr-review-process?
- Run
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill amr-review-process. The install tabs above show the steps for each supported agent. - Which AI agents does amr-review-process 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-review-process 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-review-process still maintained?
- The repository was last updated about 2 months ago, so amr-review-process is actively maintained.
Skill content
View source on GitHubname: amr-review-process description: Use when you need to understand the Academy of Management Review (AMR) developmental, multi-round review and interpret a decision letter focused on theoretical novelty and logical soundness. Explains the process and decision types; it does NOT draft the response document (that is amr-rebuttal).
Understanding AMR's Developmental Review (amr-review-process)
When to trigger
- You just received an AMR decision letter and need to interpret it
- You do not know what "developmental review" means or what is expected of you
- You are deciding whether an R&R is worth pursuing and how to read the editor's signals
- You need to triage reviewer comments by what AMR actually weights
What AMR review is (durable norms)
AMR uses a double-anonymous, multi-round, developmental review. "Developmental" is the operative word: the goal is to help promising theory papers become stronger, so reviews are detailed and the bar rises across rounds. Verify current specifics on the official page, but the durable shape is:
- A handling editor (the Editor-in-Chief — currently Kris Byron (Georgia State University), AMR EIC succeeding Sherry M. B. Thatcher; three-year term runs through the end of 2026 (1 July 2023 transition start), still sitting as of 2026-06-23 with no successor yet announced; verify the current slate on the AOM AMR editorial-leadership page — or an action editor) assigns the paper to reviewers expert in your conversation. AOM's public author page says designated reviewers advise the editor and that revisions may continue through multiple rounds; it does not publish an exact AMR reviewer count or acceptance rate, so do not quote one unless AOM publishes it.
- Reviews focus on the things AMR exists to protect: a genuine theoretical contribution (Whetten's What/How/Why/Who-Where-When, AMR 1989, DOI 10.5465/amr.1989.4308371), construct clarity (Suddaby, AMR 2010, DOI 10.5465/amr.2010.0419), and the logical soundness of the argument — not data (there is none). Reviewers do not ask about identification, sample size, robustness, or measurement validity; those are AMJ/ASQ/SMJ criteria.
- Decisions are commonly: Reject; Reject & Resubmit (encouraged to rebuild, treated as a fresh submission); Major Revision (R&R); less often Minor Revision; rarely an immediate Accept.
- An R&R is an invitation, not a promise. Multiple rounds are normal at AMR.
Desk-reject triggers specific to AMR
The editor screens for fit and contribution before sending a paper out. Most common AMR desk rejects: (1) "this is an empirical paper"; (2) incremental theory; (3) a literature review with no original move; (4) construct proliferation (relabeling); (5) untestable-in-principle or tautological propositions; (6) poor fit/scope or anonymization failures.
Reading the decision letter
| Signal in the letter | What it usually means | Your move |
|----------------------|-----------------------|-----------|
| "Promising but the contribution is not yet clear" | Theory may be sound but under-differentiated | Re-run amr-contribution-framing |
| "Propositions are not well supported by the argument" | Logic gaps between premises and propositions | Re-run amr-data-analysis, then amr-theory-development |
| "Reads as a review of the literature" | No real theoretical move | Re-run amr-literature-positioning + amr-writing-style |
| "Constructs overlap existing ones" | Construct distinctiveness challenged | Re-run amr-theory-development (domain/distinction) |
| "Scope/level inconsistency" | Level-of-theory confusion | Re-run amr-methods (cross-level) |
| Editor highlights specific reviewer points as essential | The editor's priorities | Address these first and most fully |
Triaging reviewer comments
- Read the editor's letter as the master key. When reviewers disagree, the editor's framing tells you which issues are decision-critical.
- Separate theory-substance comments from presentation comments. Substance (a missing mechanism, an undefended proposition) outranks wording.
- Distinguish "must change the theory" from "must explain better." Some comments mean the theory is wrong; others mean the prose hid a sound argument.
- Note conflicts between reviewers and plan to adjudicate them transparently in the
response (handled in
amr-rebuttal).
Checklist
- [ ] Decision type identified (Reject / R&R / Reject & Resubmit / Minor)
- [ ] The editor's stated priorities are extracted and ranked
- [ ] Each reviewer comment tagged: theory-substance vs. presentation
- [ ] Comments mapped to the skill that addresses them (theory / logic / positioning / contribution)
- [ ] Reviewer conflicts identified for transparent adjudication
- [ ] Realistic judgment made on whether the revision can meet the raised bar
Anti-patterns
- Treating an R&R as acceptance and making only cosmetic changes
- Ignoring the editor's letter and responding only to reviewers
- Reading "developmental" as "the reviewers will fix it for me"
- Promising in a rebuttal to add data — AMR neither wants nor accepts data
- Underestimating the number of rounds and over-claiming the revision is final
Output format
【Decision type】Reject / Reject & Resubmit / Major (R&R) / Minor
【Editor's priorities】ranked list
【Comment triage】substance: [...] | presentation: [...]
【Skill mapping】comment → amr-* skill
【Reviewer conflicts】[...]
【Go / no-go】pursue revision? rationale
【Next step】amr-rebuttal
Related Skills
Claude-Code-Game-Studios
39.9kTurn Claude Code into a full game dev studio — 49 AI agents, 75 workflow skills, and a complete coordination system mirroring real studio hierarchy.
siyuan
47.3kAn open-source, privacy-first, self-hosted knowledge workspace where humans and AI agents work together 开源、隐私优先、自托管的知识工作空间,让人与智能体在此协作
x402
121.0kSet up Browser Use Cloud payments with x402 — pay per request from a crypto wallet (USDC on Base mainnet), no signup or API key.
algorithmic-art
177.9kCreating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
