跳到正文
FunCoding

搜索

搜索文档、Skill 和 MCP

amann-proposal-framing

Use when writing the short proposal that gates an Academy of Management Annals (Annals) review — the ≤5-page, four-heading proposal submitted under the twice-yearly deadlines before any full review is invited. Builds the proposal; it does not gather the literature (amann-literature-synthesis) or run the portal preflight (amann-submission).

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

安装

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

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

SKILL.md

Proposal Framing — the Gate (amann-proposal-framing)

When to trigger

  • The literature passed amann-topic-selection and you are ready to approach Annals
  • You need to know exactly what the proposal must contain and how long it can be
  • You are about to write a full review — stop: at Annals the proposal is mandatory and comes first
  • An April 1 / October 1 deadline is approaching and the proposal is the deliverable

How Annals intake actually works (检索于 2026-06;以官网为准)

Annals uses a two-step, proposal-first process. You do not submit a full review cold; you submit a short proposal, and only an accepted proposal is invited to develop into a full article.

  • Proposal length. No longer than 5 pages, single-spaced, 1-inch margins, 12-point font; references and visual elements do not count toward the limit.
  • Four required sections, with these exact headings:
    1. Focus of the review — the literature and the animating problem.
    2. Related reviews — what reviews already exist and why yours is not redundant.
    3. Review scope and process — boundaries, inclusion logic, how you will gather and synthesize the corpus.
    4. New insights — the integrative contribution, the "attitude," and the agenda the review will produce.
  • Deadlines. Proposals are accepted on a twice-yearly cycle — April 1 and October 1. Submissions are not reviewed until the deadline passes; decision letters arrive ~6 weeks after the deadline.
  • Who reviews the proposal. Proposals are double-blind peer-reviewed by the Associate Editors. (The invited full review later forgoes double-blind and is read only by the AE and Editor — see amann-review-process.)
  • Portal. Submit via Manuscript Central: https://mc.manuscriptcentral.com/aomannals. A current CV may be requested for the editors' eyes only — confirm at submission time (待核实).

The ≤5-page proposal is the single most consequential document in the Annals lifecycle: it is the gate. A strong proposal earns an invitation before you sink months into reading and drafting; a weak one ends the project regardless of how good the eventual review would have been. Treat it as a high-stakes argument, not an outline.

What each heading must accomplish

HeadingWhat it must doCommon failure
Focus of the reviewName the literature and the problem with the field (from amann-topic-selection), not just the topicA topic label ("a review of X") with no problem
Related reviewsShow command of prior reviews and stake the delta — what yours does that none didClaiming "no review exists" instead of differentiating from the ones that do
Review scope and processState boundaries, inclusion/exclusion logic, databases, and the synthesis method (narrative / systematic / bibliometric)Vague "we will read the literature" with no transparent process
New insightsLead with the integrative framework and the agenda — the new way of seeing the field, with attitudeA promise of "comprehensive coverage" and no new organizing idea

The center of gravity is New insights: Associate Editors are deciding whether this review will reorganize the field, not whether it will summarize it. A proposal that nails coverage but offers no framework is the most common proposal-stage reject.

Checklist

  • Proposal is ≤5 pages, single-spaced, 1-inch margins, 12pt (refs/visuals excluded)
  • Uses the four required headings verbatim: Focus / Related reviews / Review scope and process / New insights
  • "Focus" states a problem with the field, not a topic label
  • "Related reviews" differentiates from existing reviews (delta), not "none exists"
  • "Review scope and process" names boundaries, inclusion logic, databases, and synthesis method
  • "New insights" leads with the integrative framework + agenda + the critical "attitude"
  • Targeted at the correct April 1 / October 1 window
  • Balance addressed if you are a contributor to the literature
  • Portal, CV requirement, and any current specifics re-confirmed (检索于 2026-06;以官网为准 / 待核实)

Anti-patterns

  • Writing the full ~50-page review and trying to submit it — Annals invites full reviews only after proposal acceptance
  • A proposal that is a chapter outline with no integrative idea under "New insights"
  • "Related reviews" that asserts novelty by ignoring the reviews that already exist (reviewers will name them)
  • A "Review scope and process" section with no inclusion logic or named databases (looks unsystematic)
  • Promising comprehensive coverage as if coverage alone were the contribution
  • Missing the deadline and assuming rolling intake

Output format

【Focus of the review】<literature + animating problem, one sentence>
【Related reviews】<existing reviews + the delta yours provides>
【Review scope and process】<boundaries / inclusion logic / databases / synthesis method>
【New insights】<integrative framework + agenda + the critical attitude>
【Length check】≤5pp single-spaced, 1-in margins, 12pt (refs/visuals excluded)? Y/N
【Deadline】targeting April 1 / October 1? <which>
【Balance note】<how author's own work is handled, if a contributor>
【Open verifications】portal / CV / specifics re-confirmed on official page? Y/N
【Next skill】→ amann-literature-synthesis (begin systematic reading) after invitation

相似的 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.

文档与办公