Skip to content
FunCoding

Search

Search docs, Skills and MCP

amann-literature-synthesis

Use when systematically gathering, coding, and synthesizing a management/organization literature for an Academy of Management Annals (Annals) review — the search-and-coverage methodology and the choice of narrative vs. systematic vs. bibliometric integration. Builds the corpus and synthesis notes; it does not impose the organizing spine (amann-organizing-framework) or write prose.

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

Install

Send this to Claude Code, Codex or Cursor. The agent checks the Skill for safety first and installs it only after you confirm.

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

SKILL.md

Literature Synthesis Methodology (amann-literature-synthesis)

When to trigger

  • The proposal was invited and it is time to read the field thoroughly and transparently
  • Reading feels unsystematic; you fear missing streams a referee could name
  • You have many papers but no way to code, compare, or reconcile them
  • You must decide whether this review is narrative, systematic, or bibliometric in method

At Annals you synthesize — you do not run primary research

The folder name says "data analysis," but an Annals review reports no data of its own. Your "analysis" is the systematic appraisal and integration of a literature. The credibility of the whole review rests on the reader's belief that you read everything that matters and coded it consistently. Build coverage as a transparent process, not from memory.

Choose the integration method first

MethodWhat it doesBest when
Narrative / integrative reviewreads, interprets, and reorganizes the literature into a new frameworkthe contribution is conceptual integration (Annals' core mode)
Systematic reviewa pre-specified, reproducible search-and-screen protocol; transparent inclusionthe field is large and you must prove comprehensive, unbiased coverage
Bibliometric / meta-analyticco-citation, co-word, or quantitative effect-size synthesisthe contribution is structural (intellectual map) or a cumulative magnitude estimate

Most Annals reviews are integrative narrative with a systematic backbone: a transparent search establishes coverage, and the narrative does the reorganizing. Bibliometrics can support the framework but rarely replaces the interpretive contribution.

Building coverage to saturation

  1. Seed set. Start from the proposal's key references and the field's canonical pieces.
  2. Transparent search. Search the major databases (Web of Science, Scopus, EBSCO/Business Source, Google Scholar) by topic keywords; record terms, databases, dates, and counts so the "Review scope and process" claims are auditable.
  3. Forward + backward snowball. Backward: each paper's reference list. Forward: who cites the seeds. Iterate until new searches stop turning up unseen important work (saturation).
  4. Inclusion / exclusion logic, stated. Define what is in and out (time window, journal tier, theoretical vs. empirical, allied fields) and apply it consistently — referees ask "why did you omit X?"
  5. Working papers + adjacent literatures. A current review must reach recent work and the bordering fields (organizational psychology, sociology) the literature draws on, or it reads stale or siloed.
  6. Saturation log. Record when each search stopped yielding new must-cite work — this is your evidence of comprehensiveness for amann-evidence-standards and the referees.

From reading to synthesis (a coding matrix, not a summary)

Summarizing restates each paper; synthesizing makes papers talk to each other. Code the corpus as you read:

ColumnWhat to capture
Studyauthor–year; the contribution you cite it for
Construct / questionexactly what it theorizes or measures (so incommensurable work is not pooled)
Theory basethe lens it uses (so you can map streams and detect silos)
Method / contextdesign, sample, setting (so you can weight credibility)
Finding / claimdirection + magnitude or the conceptual move
Tensionwhich work it agrees/conflicts with, and why

This matrix feeds the organizing framework, the synthesis tables, and the even-handed treatment of debates. You appraise the studies (you are the field's reviewer-of-record); you do not re-run or "correct" them.

Checklist

  • Integration method chosen and justified (narrative-integrative / systematic / bibliometric)
  • Seed set drawn from canonical pieces + proposal references
  • Search terms, databases, dates, and counts recorded for the "scope and process" account
  • Forward and backward snowball iterated to saturation
  • Inclusion/exclusion logic stated and applied consistently
  • Recent working papers and adjacent literatures included (no staleness, no silo)
  • Saturation log records where searches stopped yielding new must-cites
  • Coding matrix captures construct + theory base + method + finding + tensions
  • Incommensurable constructs flagged (not pooled into a false "the literature finds…")
  • No major author/stream whose omission a referee could name

Anti-patterns

  • Reviewing from a personal reading list (predictable coverage gaps a referee will spot)
  • Summarizing paper-by-paper instead of synthesizing across the corpus
  • Pooling studies that theorize different constructs into one "the field shows…" claim
  • An undocumented search with no terms, databases, or counts — coverage claims become unfalsifiable
  • Ignoring working papers (stale) or adjacent literatures (siloed)
  • Re-estimating or "fixing" primary studies — an Annals review appraises, it does not re-run

Output format

【Method】narrative-integrative / systematic / bibliometric — and why
【Seed set】<canonical + proposal references>
【Search record】terms / databases / dates / counts logged? Y/N
【Snowball】backward+forward iterated to saturation? Y/N
【Inclusion logic】stated and consistently applied? Y/N
【Frontier + adjacency】recent WPs + bordering fields included? Y/N
【Saturation evidence】<where searches stopped yielding new must-cites>
【Coding matrix】construct/theory/method/finding/tension rows ready? Y/N
【Coverage risks】<any author/stream an omission referee could name>
【Next skill】→ amann-organizing-framework (impose the integrative spine on the matrix)

Similar Skills

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.

Docs & office

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.

Docs & office

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.

Docs & office

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.

Docs & office

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.

Docs & office

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.

Docs & office