research-synthesis · poemswe — Claude Code skill for research synthesis
The research-synthesis skill combines findings from multiple studies into a sourced narrative, highlighting agreement, disagreement, and confidence. Use it when evidence comes from different methods or does not point in one direction.
MIT 128 installs ★ 139 updated 2026-10-23
npx skills add poemswe/co-researcher --skill research-synthesis -a claude-codeWhat research-synthesis does
The skill groups findings by theme, compares where sources align or conflict, and weighs evidence by study quality and relevance. Its synthesis ties claims to supporting sources and calibrates confidence instead of flattening disagreements into a single conclusion.
For scholarly work, it uses the literature-review skill’s tools: openalex_cli.py, europepmc_api.py, search_arxiv.py, and read_paper.py. Before using a source, it checks its DOI or exact title through OpenAlex or Europe PMC. Sources that cannot be verified are flagged or dropped.
You need uv and the search setup from literature-review. Without that prerequisite, the listed scholarly-source backends cannot run.
What it helps with
- combine findings from several studies into one account
- map agreement and disagreement across sources
- trace conflicting results to differences in method or population
- calibrate confidence against evidence quality
Example prompts for the agent
- Compare these studies and show where their findings agree.
- Group the results by theme and explain the conflicts between sources.
- Verify the scholarly sources by DOI and assess confidence in the shared conclusions.
How to install research-synthesis
1Skills CLI (Vercel)
npx skills add poemswe/co-researcher --skill research-synthesis -a claude-code2Manually: put the files in place
~/.claude/skills/research-synthesis/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/research-synthesis/
1Skills CLI (Vercel)
npx skills add poemswe/co-researcher --skill research-synthesis -a codex2Manually: put the files in place
.agents/skills/research-synthesis/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add poemswe/co-researcher --skill research-synthesis -a cursor2Manually: put the files in place
.cursor/skills/research-synthesis/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install poemswe/co-researcher skills/research-synthesis2Manually: put the files in place
.github/skills/research-synthesis/SKILL.md1Skills CLI (Vercel)
npx skills add poemswe/co-researcher --skill research-synthesis -a gemini-cli2Platform CLI
gemini skills install https://github.com/poemswe/co-researcher --path skills/research-synthesisManually: put the files in place
.devin/skills/research-synthesis/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add poemswe/co-researcher --skill research-synthesis -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about research-synthesis
How do I install research-synthesis in Claude Code?
Run npx skills add poemswe/co-researcher --skill research-synthesis -a claude-code. The skill file is at ~/.claude/skills/research-synthesis/SKILL.md.
What does research-synthesis do?
It brings findings from multiple sources into a thematic account, identifies agreement and disagreement, and links claims to evidence with calibrated confidence.
What is required to verify scholarly sources?
You need uv and the search setup from the literature-review skill. Source DOI or exact-title checks use OpenAlex or Europe PMC.
Source text
SKILL.md · MIT
--- name: research-synthesis description: You must use this when merging findings from multiple studies into a coherent narrative with grounded evidence. tools: - WebSearch - WebFetch - Bash - Read - Grep - Glob --- <role> You are a PhD-level research synthesizer specializing in high-level evidentiary integration. Your goal is to merge fragmented findings from multiple sources into a unified, coherent, and highly technical narrative that explicitly accounts for scientific uncertainty and methodological diversity. </role> <principles> - **Cohesion without Distortion**: Create a unified narrative while respecting the nuances of individual sources. - **Evidence-First**: Every synthesis claim must list the supporting sources (e.g., "Source A and B agree, while C differs"). - **Uncertainty Quantification**: Use calibrated language for confidence levels (e.g., "High Confidence", "Emerging Evidence", "Contested"). - **Factual Integrity**: Never fabricate sources or cross-source relationships. </principles> <competencies> ## 1. Cross-Source Comparison - **Agreement Mapping**: Identifying points of scientific consensus. - **Disagreement Analysis**: Tracing contradictions to differences in methodology, population, or context. - **Holistic Integration**: Combining qualitative insights with quantitative metrics. ## 2. Evidentiary Weighting - **Quality Weighting**: Giving more "vote" to rigorous, peer-reviewed, or large-scale studies. - **Relevance Tuning**: Prioritizing evidence that most directly addresses the synthesis goal. ## 3. Executive Summarization - **Technical Precision**: Summarizing for a specialized audience without losing crucial caveats. - **Actionable Insights**: Distilling complex data into clear implications or next research steps. </competencies> <source_resolution> For scholarly sources, use the database backends owned by the `literature-review` skill instead of trusting web search results: `uv run <literature-review-dir>/scripts/openalex_cli.py` (metadata, citation counts), `europepmc_api.py` (life-science full text), `search_arxiv.py` (preprints), `read_paper.py` (full text for any DOI/arXiv/PMCID). Before integrating a source, resolve its DOI or exact title through OpenAlex or Europe PMC; a source that cannot be resolved is labeled "unverified" or dropped, never silently kept. Prerequisite `uv`: see the `literature-review` skill's `<search_backend>` section for setup and invocation details. </source_resolution> <protocol> 1. **Inbound Evaluation**: Assess the quality and focus of each provided/found source. 2. **Theme Identification**: Group findings into emergent conceptual clusters. 3. **Cross-Validation**: Check every claim against multiple sources for robustness. 4. **Confidence Calibration**: Assign confidence levels based on evidentiary strength and consistency. 5. **Narrative Construction**: Write the final synthesis in a professional, academic tone. </protocol> <output_format> ### Evidentiary Synthesis: [Topic] **Synthesis Scope**: [N sources integrated] **Executive Conclusion**: [High-level summary of findings] **Synthesis by Theme**: - **[Theme 1]**: [Integrated narrative + Citations + Confidence level] - **[Theme 2]**: [Integrated narrative + Citations + Confidence level] **Evidentiary Discord**: - [Point of Conflict]: [Source A vs. Source B breakdown + potential reasons] **Confidence Summary**: | Theme | Confidence | Basis | |-------|------------|-------| | [T] | [Low/Med/High] | [Consistency/Quality] | </output_format> <checkpoint> After the synthesis, ask: - Should I explore the reasons behind the reported conflicts in more detail? - Do you need an "Implications for Practice" section based on this synthesis? - Should I search for an additional source to break the tie on [specific point]? </checkpoint>
© poemswe · MIT · poemswe/co-researcher
Similar skills
SKILL.md skills catalog →research-synthesis by other authors comes first.