跳到正文
FunCoding

搜索

搜索文档、Skill 和 MCP

amann-review-process

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).

文档与办公1.2kAcademy-of-Management-Annals-Skills/skills/amann-review-process/SKILL.md

安装

把这段话发给 Claude Code、Codex 或 Cursor。智能体会先检查安全性,你确认后才安装。

读取 https://funcoding.ai/skills/brycewang-stanford/awesome-journal-skills/amann-review-process/install.md ,按里面的步骤帮我安装这个 Skill。

SKILL.md

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;以官网为准):

StageWhat happensBlinding & reviewersOutput
1. ProposalSubmit a ≤5-page proposal (four headings) at a deadlineDouble-blind, reviewed by the Associate EditorsInvitation to develop the full review, or decline
2. Invited full reviewDevelop the ~50-page review with editorial guidanceForgoes double-blind; read by the Associate Editor and EditorConditional 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

  1. Pick the deadline first. Decide which April 1 / October 1 window the proposal targets, and back-plan the proposal-writing from there.
  2. 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.
  3. On invitation, ramp the systematic search (amann-literature-synthesis) — full coverage to saturation is now required.
  4. Treat the editor as a partner through the editor-only full-review stage (amann-editor-strategy); expect substantive revision rounds.
  5. 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.

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)

相似的 Skill

pdf
anthropics/skills180k

pdf

Use this skill whenever the user wants to do anything with PDF files. This includes reading or extracting text/tables from PDFs, combining or merging multiple PDFs into one, splitting PDFs apart, rotating pages, adding watermarks, creating new PDFs, filling PDF forms, encrypting/decrypting PDFs, extracting images, and OCR on scanned PDFs to make them searchable. If the user mentions a .pdf file or asks to produce one, use this skill.

文档与办公

discernment-nudge
anthropics/skills180k

discernment-nudge

After you give a substantive answer or draft that the user may act on — advice or recommendations, drafted artifacts such as goals, plans, pitches, proposals, or emails, estimates or projections, analysis or interpretation of data, factual claims they may rely on, or a multi-step argument — invoke this skill BEFORE finalizing your reply and then, if it applies, append 2-3 short follow-up questions, each tied to something specific in what you just produced, that help the user check key facts, probe the reasoning or assumptions, and notice missing context. Do this at most once per conversation. Skip it when the user asked a trivial how-to or simple lookup, wants a purely educational explanation, asked you only to format, convert, or assemble a file from content they provided, is writing code they will run, is doing creative writing or casual chat, or already asked you to double-check, cite, or review — the skill file explains these boundaries and the exact output format.

文档与办公

doc-coauthoring
anthropics/skills180k

doc-coauthoring

Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.

文档与办公

docx
anthropics/skills180k

docx

Use this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files) or Word templates (.dotx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', '.dotx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx or .dotx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation.

文档与办公

pptx
anthropics/skills180k

pptx

Use this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an email or summary); editing, modifying, or updating existing presentations; combining or splitting slide files; working with templates (.potx), layouts, speaker notes, or comments. Trigger whenever the user mentions "deck," "slides," "presentation," or references a .pptx or .potx filename, regardless of what they plan to do with the content afterward. If a .pptx or .potx file needs to be opened, created, or touched, use this skill.

文档与办公

canvas-design
anthropics/skills180k

canvas-design

Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.

文档与办公