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 Review Process

ASecurity

Use when you need to understand or set expectations for the Academy of Management Journal (AMJ) editorial and peer-review process — desk review, the developmental multi-round R&R culture, and reading a decision letter. Explains the process and how to read decisions; it does not draft the response letter (amj-rebuttal).

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

Security Analysis

A100/100

Scanned 6/4/2026

Install to Claude Code

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

Installs into .claude/skills of the current project.

Are you the author of Amj Review Process?

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

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

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

Download with Pro
Files
SKILL.md
---
name: amj-review-process
description: Use when you need to understand or set expectations for the Academy of Management Journal (AMJ) editorial and peer-review process — desk review, the developmental multi-round R&R culture, and reading a decision letter. Explains the process and how to read decisions; it does not draft the response letter (amj-rebuttal).
---

# Understanding the Review Process (amj-review-process)

## When to trigger

- Before submitting, to calibrate expectations about timeline and decision types
- A decision letter arrived and you need to interpret it (R&R vs. reject; major vs. minor)
- You are unsure how much weight reviewers vs. the action editor carry
- You want to plan a revision strategy before drafting the response (then go to `amj-rebuttal`)

> Editorial structure, named editors, and exact timelines change. Verify the current editorial team, policies, and turnaround on the official AMJ site; the norms below are durable. As of 2026-05-30: AMJ uses **blind review**, targets constructive **developmental feedback to authors within ~60 days**, and the incoming Editor-in-Chief is **Gary A. Ballinger (University of Virginia)**, whose team began receiving submissions on 1 July 2025.

## How AMJ review works (durable norms)

1. **Submission & routing.** The editor (or an associate/action editor) screens the manuscript and routes it to an action editor in the relevant division. Submission is via ScholarOne (mc.manuscriptcentral.com/AMJ) with all author identifiers removed for blind review.
2. **Desk decision.** Manuscripts that are off-fit, atheoretical, fatally underpowered, or that miss one of AMJ's three criteria (empirical contribution, theoretical contribution, practical relevance) may be desk-rejected without external review. A clear theoretical contribution and appropriate design are what get a paper past the desk.
3. **External peer review.** Typically several (often three) reviewers in the focal conversation evaluate the theoretical contribution, design rigor, and analysis; AMJ aims to return developmental feedback within roughly 60 days.
4. **Action editor synthesis.** The action editor weighs the reviews, forms an independent judgment, and writes the decision letter. The editor's letter — not a vote count — drives the outcome.
5. **Decision.** Common outcomes: reject; reject with encouragement to resubmit as new; major revision (R&R); minor revision; (rarely) accept. A first-round acceptance is essentially unheard of.

## AMJ is developmental and multi-round

AMJ's culture is **developmental**: an R&R is an invitation to improve the paper over (often) multiple rounds. Reviewers and the action editor push hard on the **theoretical contribution** and the **method** — expect requests to deepen theory, add a study, strengthen identification, or address common-method/endogeneity concerns. Treat an R&R as a serious opportunity, not a near-acceptance, and not a rejection.

## Reading the decision letter

- **Find the editor's priorities first.** The action editor's letter signals which reviewer points are essential vs. optional. Address the editor's framing above all.
- **Distinguish "fatal" from "fixable."** If a core identification or theory concern is fatal and unaddressable, an honest reframe (or a different paper) beats a doomed revision.
- **Gauge encouragement.** Language like "we see promise" + a major revision signals a real path; "does not fit our developmental model" signals reject.
- **Count the asks.** Map every reviewer point to: theory / method / analysis / framing / writing — this becomes the revision plan that feeds `amj-rebuttal`.

## Planning the revision

- Decide whether you can satisfy the **theoretical-contribution** demands; if not, the revision will not succeed regardless of method fixes.
- Scope the new analyses/data the reviewers imply and whether they are feasible in the revision window.
- Identify points where reviewers conflict; plan to surface the conflict for the editor rather than silently siding with one.

## Checklist

- [ ] Decision type identified (R&R major/minor, reject-resubmit, reject)
- [ ] The action editor's priorities extracted and ranked above individual reviewer asks
- [ ] Every reviewer comment categorized (theory / method / analysis / framing / writing)
- [ ] Fatal vs. fixable concerns separated honestly
- [ ] Feasibility of demanded new theory/data/analyses assessed against the deadline
- [ ] Reviewer conflicts noted for the editor's attention

## Anti-patterns

- Treating an R&R as a near-acceptance and making only cosmetic changes.
- Treating an R&R as a rejection and walking away from a viable path.
- Counting reviewer votes instead of reading the action editor's letter.
- Ignoring the editor's stated priorities while over-investing in a minor reviewer point.
- Starting to write the response letter before mapping and planning the revision.

## Output format

```
【Decision type】R&R(major/minor) / reject-resubmit / reject
【Editor's priorities】1... 2... 3...
【Comment map】theory:[...] method:[...] analysis:[...] framing:[...] writing:[...]
【Fatal vs. fixable】...
【New work needed】theory / data / analysis — feasible? ...
【Reviewer conflicts】...
【Next step】amj-rebuttal (plan revisions, then draft response)
```

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 →