/research-synthesis
Synthesize multiple sources — articles, reports, notes, transcripts — into one structured brief with themes, agreements, contradictions, and gaps. Use when the user says "synthesize this research", "combine these sources", "what do these articles agree on", or has a folder of
$ npx -y skills add sgharlow/claude-code-recipes --skill research-synthesis --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/research-synthesis
Context preview
The summary Claude sees to decide when to auto-load this skill.
Synthesize multiple sources — articles, reports, notes, transcripts — into one structured brief with themes, agreements, contradictions, and gaps. Use when the user says "synthesize this research", "combine these sources", "what do these articles agree on", or has a folder of
SKILL.md
research-synthesis.SKILL.mdname: research-synthesis
description: Synthesize multiple sources — articles, reports, notes, transcripts — into one structured brief with themes, agreements, contradictions, and gaps. Use when the user says "synthesize this research", "combine these sources", "what do these articles agree on", or has a folder of collected material and needs one coherent picture.
Research Synthesis
Merge a pile of sources into a single brief that shows where the sources agree, where they conflict, and what none of them answer. Synthesis is cross-source structure — not a stack of per-source summaries.
Steps
1. Inventory the sources: list every file or link the user provides with a one-line description and its type (primary data, reporting, opinion, marketing). Confirm the research question the synthesis must answer — without one, ask before reading further. 2. Read each source, capturing per source: its main claims, the evidence offered, its date, and any obvious bias or interest. 3. Build the synthesis across sources:
- **Themes** — 3–6 recurring threads, each citing which sources support it.
- **Consensus** — claims multiple independent sources agree on (note when "agreement"
is really one origin quoted many times).
- **Contradictions** — where sources conflict, shown side by side with each side's
evidence; do not silently resolve a conflict by picking a winner.
- **Gaps** — what the research question needs that no source answers.
- **Bottom line** — 3–5 sentences answering the research question, at the confidence
the evidence actually supports. 4. Verify: every claim in the brief carries a source attribution; any claim traceable to only one source is marked `single-source`. If two sources' dates differ by years, flag which may be stale rather than averaging them.
Constraints
- Never pad thin evidence into a confident conclusion — "the sources don't establish this"
is a valid and often the correct bottom line.
- Keep the brief under two pages; the per-source inventory goes in an appendix, not the body.
Full walkthrough, examples, and variations: `recipes/Recipe-007-Research-Synthesis.md`.
Read more
name: research-synthesis description: Synthesize multiple sources — articles, reports, notes, transcripts — into one structured brief with themes, agreements, contradictions, and gaps. Use when the user says "synthesize this research", "combine these sources", "what do these articles agree on", or has a folder of collected material and needs one coherent picture.
Research Synthesis
Merge a pile of sources into a single brief that shows where the sources agree, where they conflict, and what none of them answer. Synthesis is cross-source structure — not a stack of per-source summaries.
Steps
1. Inventory the sources: list every file or link the user provides with a one-line description and its type (primary data, reporting, opinion, marketing). Confirm the research question the synthesis must answer — without one, ask before reading further. 2. Read each source, capturing per source: its main claims, the evidence offered, its date, and any obvious bias or interest. 3. Build the synthesis across sources:
- **Themes** — 3–6 recurring threads, each citing which sources support it.
- **Consensus** — claims multiple independent sources agree on (note when "agreement"
is really one origin quoted many times).
- **Contradictions** — where sources conflict, shown side by side with each side's
evidence; do not silently resolve a conflict by picking a winner.
- **Gaps** — what the research question needs that no source answers.
- **Bottom line** — 3–5 sentences answering the research question, at the confidence
the evidence actually supports. 4. Verify: every claim in the brief carries a source attribution; any claim traceable to only one source is marked `single-source`. If two sources' dates differ by years, flag which may be stale rather than averaging them.
Constraints
- Never pad thin evidence into a confident conclusion — "the sources don't establish this"
is a valid and often the correct bottom line.
- Keep the brief under two pages; the per-source inventory goes in an appendix, not the body.
Full walkthrough, examples, and variations: `recipes/Recipe-007-Research-Synthesis.md`.
Claude Code artifacts graded by Skill Crossroads — click the badge for the evidence-cited scorecard. Your Complete Guide to AI-Powered Productivity
Repo: sgharlow/claude-code-recipes
Other skills on claude-code-recipes.
- /data-cleanup
Clean and standardize messy tabular data (CSV, spreadsheet paste, system exports) into an analysis-ready dataset — consistent dates and names, typed columns, duplicates identified, missing values handled explicitly. Use when the user says "clean this data", "standardize this
Open skill - /meeting-notes-to-actions
Turn raw meeting notes into a shareable summary, an action-item table with owners and deadlines, and follow-up email drafts. Use when the user says "process my meeting notes", "extract action items", "who owns what from this meeting", or "draft the follow-ups" — or pastes messy
Open skill - /qc-checklist
Turn a process description into an operational quality-control checklist — binary pass/fail checks, acceptance criteria, critical-vs-routine tiers, and failure modes with catch-points. Use when the user says "build a QC checklist", "standardize how we review X", "acceptance
Open skill - /summarize-document
Summarize a long document into an executive summary, key points, and role-specific implications. Use when the user says "summarize this document", "give me the key points", "do I need to read this?", or drops a long PDF, report, or contract and asks what matters in it.
Open skill - /weekly-status-report
Turn scattered weekly updates (notes, emails, task exports, meeting notes) into a structured status report with highlights, progress, severity-rated blockers, and next-week priorities. Use when the user says "write my status report", "weekly update", "summarize my week for my
Open skill

