Cold Outbound Optimizer
ericosiu/ai-marketing-skills
Design, analyze, and optimize cold outbound email campaigns for Instantly.
A skill your agent uses when planning around the two-step proposal→invited-review process of the Academy of Management Annals (Annals) — the twice-yearly proposal cadence, double-blind proposal…
Install Amann Review Process
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill amann-review-process -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills amann-review-process --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/Academy-of-Management-Annals-Skills/skills/amann-review-process .claude/skills/amann-review-process && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "amann-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Academy-of-Management-Annals-Skills/skills/amann-review-process into .claude/skills/amann-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "amann-review-process", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Academy-of-Management-Annals-Skills/skills/amann-review-processType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill amann-review-process -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills amann-review-process --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/Academy-of-Management-Annals-Skills/skills/amann-review-process .agents/skills/amann-review-process && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "amann-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Academy-of-Management-Annals-Skills/skills/amann-review-process into .agents/skills/amann-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "amann-review-process", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill amann-review-process -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills amann-review-process --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/Academy-of-Management-Annals-Skills/skills/amann-review-process .cursor/skills/amann-review-process && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "amann-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Academy-of-Management-Annals-Skills/skills/amann-review-process into .cursor/skills/amann-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "amann-review-process", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/brycewang-stanford/Awesome-Journal-Skills.git --path Academy-of-Management-Annals-Skills/skills/amann-review-process--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill amann-review-process -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills amann-review-process --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/Academy-of-Management-Annals-Skills/skills/amann-review-process .gemini/skills/amann-review-process && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "amann-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Academy-of-Management-Annals-Skills/skills/amann-review-process into .gemini/skills/amann-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "amann-review-process", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills amann-review-processInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill amann-review-process -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/Academy-of-Management-Annals-Skills/skills/amann-review-process .github/skills/amann-review-process && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "amann-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Academy-of-Management-Annals-Skills/skills/amann-review-process into .github/skills/amann-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "amann-review-process", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill amann-review-process -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills amann-review-process --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/Academy-of-Management-Annals-Skills/skills/amann-review-process .opencode/skills/amann-review-process && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "amann-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Academy-of-Management-Annals-Skills/skills/amann-review-process into .opencode/skills/amann-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "amann-review-process", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
amann-review-process- GitHub stars
- 1.2k
- Token cost
- ~1.3k tokens
- SKILL.md length
- 555 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when planning around the two-step proposal→invited-review process of the Academy of Management Annals (Annals) — the twice-yearly proposal cadence, double-blind proposal…
- Works in 5 steps: Pick the deadline first. Decide which… → Do not over-invest before invitation.… → On invitation, ramp the systematic… → …
- Double-blind proposal review
- SKILL.md covers When to trigger, The two-step process is the…, The cadence and Planning the timeline, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Amann Review Process is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when planning around the two-step proposal→invited-review process of the Academy of Management Annals (Annals) — the twice-yearly proposal cadence, double-blind proposal review, the editor-only full-review development, and timelines. Explains the process; it does not write the proposal (amann-proposal-framing) or run the portal preflight (amann-submission).
Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Sales & Support. The repository describes itself as: Journal-specific Claude Code/Codex skill packs covering mainstream journals — AER, QJE, Nature, Cell, 管理世界, 经济研究 & 200+ more — your fast track to getting published. ｜ 覆盖主流期刊的… The licence is MIT.
When your agent uses it
- Double-blind proposal review
- The editor-only full-review development
Example prompts
- “/amann-review-process”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Pick the deadline first. Decide which April 1 / October 1 window the proposal targets, and back-plan the proposal-writing from there.
- Do not over-invest before invitation. The proposal is the gate; do enough reading to write a credible "Review scope and process" and "New…
- On invitation, ramp the systematic search (amann-literature-synthesis) — full coverage to saturation is now required.
- Treat the editor as a partner through the editor-only full-review stage (amann-editor-strategy); expect substantive revision rounds.
- Re-confirm every volatile date and rule on the official pages before relying on them.
What it can do on your machine
Read from SKILL.md and the folder at commit 932eb23. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Amann Review Process loads about 1.3k tokens when it runs. Until then it costs about 96 tokens; SKILL.md has 555 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from brycewang-stanford/Awesome-Journal-Skills at commit 932eb23, republished under its MIT licence (© brycewang-stanford). 555 words, ~1,260 tokens.
Download SKILL.mdSave it as
.claude/skills/amann-review-process/SKILL.md (or your agent's skills folder).- name
- amann-review-process
- description
- Use when planning around the two-step proposal→invited-review process of the Academy of Management Annals (Annals) — the twice-yearly proposal cadence, double-blind proposal review, the editor-only full-review development, and timelines. Explains the process; it does not write the proposal (amann-proposal-framing) or run the portal preflight (amann-submission).
The Annals Review Process (amann-review-process)
When to trigger
- You are deciding whether to start now or wait for the next deadline
- You need to understand who reviews what, when, and how blinding changes between stages
- You are planning a realistic timeline from proposal to published review
- A coauthor assumes Annals works like a normal journal (it does not)
The two-step process is the defining feature
Annals does not accept full reviews cold. Intake is a gated, two-step process (检索于 2026-06；以官网为准):
| Stage | What happens | Blinding & reviewers | Output |
|---|---|---|---|
| 1. Proposal | Submit a ≤5-page proposal (four headings) at a deadline | Double-blind, reviewed by the Associate Editors | Invitation to develop the full review, or decline |
| 2. Invited full review | Develop the ~50-page review with editorial guidance | Forgoes double-blind; read by the Associate Editor and Editor | Conditional acceptance / revisions / decline |
The consequences are large: most of the gatekeeping happens at the lightweight proposal stage, and most of the development happens collaboratively with an editor who already endorsed the idea. This is closer to commissioning than to ordinary peer review — you are co-building an invited piece, not throwing a finished manuscript over the wall.
The cadence
- Deadlines: April 1 and October 1. Proposals are not reviewed until the deadline passes, so submitting early gains nothing on timing — but submitting late means waiting six months.
- Proposal decision: ~6 weeks after the deadline.
- Two issues per year (January and July). Plan the full-review development and revision around this rhythm.
- Full-review development is substantial. Budget months for reading, drafting, and likely multi-round revision with the editor — not a quick turnaround.
Planning the timeline
- Pick the deadline first. Decide which April 1 / October 1 window the proposal targets, and back-plan the proposal-writing from there.
- Do not over-invest before invitation. The proposal is the gate; do enough reading to write a credible "Review scope and process" and "New insights," but do not draft the full review before you are invited.
- On invitation, ramp the systematic search (
amann-literature-synthesis) — full coverage to saturation is now required. - Treat the editor as a partner through the editor-only full-review stage (
amann-editor-strategy); expect substantive revision rounds. - Re-confirm every volatile date and rule on the official pages before relying on them.
Strategic implication: because the proposal is cheap to write and the full review is expensive, the highest-leverage move is a great proposal. Failing fast at the proposal stage saves months; over-building before invitation wastes them.
Show full SKILL.md (152 more words)Show less
Checklist
- Understood that full reviews are submitted only after a proposal is invited (no cold full submissions)
- Target deadline (April 1 / October 1) chosen and proposal back-planned
- Aware proposals are double-blind (Associate Editors); invited full review is editor-only (AE + Editor)
- ~6-week proposal decision and Jan/Jul publishing rhythm factored into the plan
- No full-review drafting before invitation (proposal is the gate)
- Substantive, multi-round full-review revision budgeted (not a light turnaround)
- All volatile dates/rules re-confirmed on the official AOM/Annals pages (检索于 2026-06)
Anti-patterns
- Treating Annals like a rolling-submission journal and submitting a full review cold
- Submitting the proposal early expecting a faster decision (review starts only after the deadline)
- Drafting the entire ~50-page review before the proposal is invited
- Expecting double-blind anonymity at the full-review stage (it forgoes double-blind)
- Underestimating revision depth and the six-month deadline gap if you miss a window
- Asserting current deadlines/timelines from memory rather than the live pages
Output format
【Stage】proposal (double-blind, AEs) / invited full review (editor-only, AE+Editor)
【Target deadline】April 1 / October 1 → <which>; proposal back-planned? Y/N
【Pre-invitation discipline】no full-review drafting before invitation? Y/N
【Timeline】~6-week proposal decision + Jan/Jul rhythm factored in? Y/N
【Revision budget】substantive multi-round development planned? Y/N
【Volatile re-confirms】deadlines / blinding / timelines checked on official pages? Y/N
【Next skill】→ amann-submission (preflight) or amann-revision (after a decision)© brycewang-stanford, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in Academy-of-Management-Annals-Skills/skills/amann-review-process of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Amann Review Process next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Amann Review Process this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.3k | Automated safety check: Pass | MIT | |
| Cold Outbound Optimizerericosiu/ai-marketing-skills | 3.6k | 1 repos | ~1.7k | Automated safety check: Pass | MIT | |
| Doc Coauthoringaws-samples/sample-strands-agent-with-agentcore | 195 | 40 repos | ~3.2k | Automated safety check: Pass | MIT | |
| Amazon Buy Box Monitorbrowser-act/skills | 6.1k | 1 repos | ~1.6k | Automated safety check: Pass | MIT | |
| Review Analysisliangdabiao/amazon-sorftime-research-MCP-skill | 959 | 1 repos | ~2.5k | Automated safety check: Pass | None | |
| Deskcomm Extensaomelgarafael/DeskcommCRM | 4.5k | — | ~2.7k | Automated safety check: Pass | MIT |
Similar skills
- Official
Doc Coauthoring
aws-samples/sample-strands-agent-with-agentcore
Guide users through a structured workflow for co-authoring documentation.
Amazon Buy Box Monitor
browser-act/skills
Pulls Amazon product details, competing seller prices and seller ratings for a given ASIN through the BrowserAct API, without browser automation.
Review Analysis
liangdabiao/amazon-sorftime-research-MCP-skill
对亚马逊商品评论进行深度分析，自动识别产品痛点、分析退货原因，生成改进建议和客服回复模板。Invoke when user uses /review-analysis command with a product ASIN.
Deskcomm Extensao
melgarafael/DeskcommCRM
Guia para criar uma extensão do DeskcommCRM — o pacote declarativo — em vez de abrir um PR no núcleo.
Tourmind Booking
tourmind-com/Tourmind-Booking-Skills
MUST USE for any hotel or accommodation intent in any language, including hotel search, hotel recommendations, nearby accommodation, hostels, guesthouses, resorts, where-to-stay questions, room…
More from brycewang-stanford/Awesome-Journal-Skills
All 2,387 skills in this repoAaag Data Analysis
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when running and reporting the analysis for an Annals of the American Association of Geographers manuscript — spatial statistics and modeling, remote-sensing accuracy, or…
Aaag Literature Positioning
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when positioning an Annals of the American Association of Geographers manuscript in the literature — engaging geographic scholarship across the relevant area and the…
Aaag Rebuttal
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when responding to an Annals of the American Association of Geographers decision letter (major/minor revision) — building a point-by-point response to the subject editor and…
Aaag Research Design
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when defending the research design of an Annals of the American Association of Geographers manuscript — spatial/quantitative analysis and GIScience, remote-sensing and…
Aaag Review Process
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when you need to understand how the Annals of the American Association of Geographers evaluates a manuscript — double-anonymous review routed through a subject editor by…
Aaag Submission
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when running the final pre-submission preflight for the Annals of the American Association of Geographers via ScholarOne Manuscripts — area/article-type selection…
Related
Categories
Questions about Amann Review Process
What does Amann Review Process do?
A skill your agent uses when planning around the two-step proposal→invited-review process of the Academy of Management Annals (Annals) — the twice-yearly proposal cadence, double-blind proposal…. Amann Review Process is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when planning around the two-step proposal→invited-review process of the Academy of Management Annals (Annals) — the twice-yearly proposal cadence, double-blind proposal review, the editor-only full-review development, and timelines.
When should I use Amann Review Process?
Amann Review Process fits situations like: double-blind proposal review; the editor-only full-review development.
How do I install Amann Review Process in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill amann-review-process -a claude-code`. Or copy the skill folder (Academy-of-Management-Annals-Skills/skills/amann-review-process in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/amann-review-process in your project. Claude Code loads it when a task matches its description.
How do I install Amann Review Process in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill amann-review-process -a codex`. Or copy the skill folder (Academy-of-Management-Annals-Skills/skills/amann-review-process in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/amann-review-process in your project. Codex loads it when a task matches its description.
Can I use Amann Review Process in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill amann-review-process -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/amann-review-process, .gemini/skills/amann-review-process, .github/skills/amann-review-process and .opencode/skills/amann-review-process in your project.
What does Amann Review Process need to run?
SKILL.md names no scripts, command-line tools or credentials: Amann Review Process is instructions for the agent only.
Does Amann Review Process access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Amann Review Process safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Amann Review Process use?
Amann Review Process is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Amann Review Process use?
About 1.3k tokens (SKILL.md is roughly 5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Amann Review Process?
Skills that share tags, products or a category with Amann Review Process: Cold Outbound Optimizer (ericosiu/ai-marketing-skills, 3.6k stars), Doc Coauthoring (aws-samples/sample-strands-agent-with-agentcore, 195 stars), Amazon Buy Box Monitor (browser-act/skills, 6.1k stars) and Review Analysis (liangdabiao/amazon-sorftime-research-MCP-skill, 959 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Amann Review Process?
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,231 GitHub stars. The repository holds 2,387 skills in this directory. The repository was last updated on September 27, 2026.
Source: brycewang-stanford/Awesome-Journal-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.