Individual skill
amann-editor-strategy
Use when working with the Associate Editor and Editor of an Academy of Management Annals (Annals) review — scope alignment after a proposal is invited, what review-article referees evaluate, and revision expectations. Plans the interaction; it does not run the portal preflight (amann-submission) or draft the response letter (amann-revision).
Academy-of-Management-Annals-Skills/skills/amann-editor-strategy/SKILL.md
Source commit 932eb23331721b16e967c59f093781be1928b498
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Network or broad shell
- Last checked
- Nov 9, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 1,404
- Repository last updated
- Sep 27, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- academic-writing Repository topic
- agent-skills Repository topic
- journal Repository topic
- academic-research Repository topic
- ai-agents Repository topic
- anthropic Repository topic
- awesome-list Repository topic
- claude Repository topic
- claude-code Repository topic
- economics Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 5,686 bytes
Read excerpt
# Editor & Referee Strategy for a Review (amann-editor-strategy)
## When to trigger
- A proposal was invited and you are aligning the full review's scope with the editor
- You want to anticipate what Annals referees of a *review* push on (different from a paper)
- The editor has asked you to expand, cut, sharpen the framework, or rebalance coverage
- You are calibrating revision depth and the twice-yearly cadence
## The editor relationship at Annals is unusually direct
Annals' process makes the editor your central partner — more than at most journals. The proposal is reviewed double-blind by the Associate Editors, but once invited, the **full review forgoes double-blind and is developed primarily with the Associate Editor and Editor** (检索于 2026-06;以官网为准). You are effectively co-developing the review with an expert editor who already endorsed the idea. Use that:
- **The proposal *is* the scope contract.** The four headings you committed to (Focus / Related reviews / Review scope and process / New insights) define what was invited. Departing from them silently is the fastest way to lose editor confidence — renegotiate explicitly if the literature pushes you elsewhere.