Skip to content
Productivity
Skill

/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

From plugin
claude-code-recipes
3936 skills

Claude Code

$ npx -y skills add sgharlow/claude-code-recipes --skill research-synthesis --agent claude-code

SKILL.md

research-synthesis.SKILL.md
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`.

Read more
@sgharlow
Ships withclaude-code-recipes

Claude Code artifacts graded by Skill Crossroads — click the badge for the evidence-cited scorecard. Your Complete Guide to AI-Powered Productivity

Stars on GitHub

Momentum

stars in total
393
Star history of sgharlow/claude-code-recipes on GitHub, a chart by star-history.com

Other skills on claude-code-recipes.

More skills from other plugins.

i-have-adhd

i-have-adhd

Shape output for a reader with ADHD: lead with the next action, number multi-step work, restate state across turns, suppress…

@ayghri@ayghriInstall Skill
ab-test-analysis

ab-test-analysis

Analyze A/B test results with statistical significance, sample size validation, confidence intervals, and ship/extend/stop…

@phuryn@phurynInstall Skill
distilly

distilly

Set up the owner profile so a personal agent knows who it works for (first-run setup, \"get to know me\"), or distill colleague,…

Questions about research-synthesis.

Which coding agents can use research-synthesis?
research-synthesis installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.