research-synthesis

research-synthesis is a skill for Claude Code from poemswe/co-researcher. It costs 22 tokens per session (848 once invoked), scanned A, original, MIT.

A method for combining findings from several scientific studies into one evidence-based explanation. It compares agreement, disagreement, study quality, and relevance.

In plain words
What is it for?
Use it to synthesize research, explain differences between studies, and draw practical conclusions while preserving important limits.
Why use it?
It helps prevent a summary from treating conflicting or weak evidence as equally reliable.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the co-researcher plugin — 15 skills, 3 commands, 1 hook shipped together

Good fit Use it to synthesize research, explain differences between studies, and draw practical conclusions while preserving important limits.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/poemswe/co-researcher/research-synthesis
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add poemswe/co-researcher --skill research-synthesis
Clone the repo
git clone --depth 1 https://github.com/poemswe/co-researcher

Made for: Claude Code.

Or install co-researcher, the plugin that ships this one along with the rest of its 15 skills, 3 commands, 1 hook.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for research-synthesis

README.md
[![agentmods](https://agentmods.dev/badge/skills/poemswe/co-researcher/research-synthesis/github.svg)](https://agentmods.dev/skills/poemswe/co-researcher/research-synthesis)
Your own site
<a href="https://agentmods.dev/skills/poemswe/co-researcher/research-synthesis"><img src="https://agentmods.dev/badge/skills/poemswe/co-researcher/research-synthesis/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for research-synthesis

Your own site · 80×15
<a href="https://agentmods.dev/skills/poemswe/co-researcher/research-synthesis"><img src="https://agentmods.dev/badge/skills/poemswe/co-researcher/research-synthesis.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 22 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 848 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00022 $0.00848
Opus 5.5 $0.00009 $0.00339
Sonnet 5.5 $0.00004 $0.00170
Haiku 4.5 $0.00002 $0.00085

Measured 1mo ago against content hash 8042f369eeb2, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

research-synthesis scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/research-synthesis/SKILL.md · 79 lines

How it starts

The opening of the file, as written. The whole thing — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.

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.

<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>

Read the full file on GitHub · 79 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 1mo ago First seen · 79 lines · 22 tokens per session scan A 8042f369eeb2

Subscribe to this mod's changes

research-synthesis is a skill published in the GitHub repository poemswe/co-researcher (135 stars, last pushed 3d ago), licensed MIT. It adds 22 tokens to every session and 848 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

refactor-research-code

Clean research code for public release while preserving reported results. Uses releaseaudit.py to separate safe mechanical cleanup from ask-first behavior risks and identity leaks. Use for release-ready repos, dead experiment branches, config extraction, documented entrypoints, and double-blind code cleanup.

ShaishavMaisuria/research-paper-lifecycle-skills · 60 tokens

prepare-artifacts

Prepares a reproducibility artifact (code/data) for submission and badging. Use when a researcher says "artifact evaluation", "artifact appendix", "reproducibility", "badge", "Artifacts Available/Evaluated/Functional/Reusable", "Results Reproduced/Replicated", "ACM badging", "USENIX/OSDI/SOSP AE", "SIGMOD ARI"…

ShaishavMaisuria/research-paper-lifecycle-skills · 225 tokens

simulate-reviewers

Venue-calibrated peer-review simulation. Use when a researcher says "simulate reviewers", "mock review", "review my paper like a NeurIPS reviewer", "what would Reviewer 2 say", "red-team my paper", "find weaknesses before I submit", "peer review my paper", "strengths and weaknesses / pros and cons of my paper", "what…

ShaishavMaisuria/research-paper-lifecycle-skills · 239 tokens

verify-results

Check whether reported paper metrics are consistent with outputs from the local code artifact. Use for result reproduction checks, artifact evaluation, reproducibility checklists, code-versus-paper audits, table or claim metric comparisons, and badge-readiness review.

ShaishavMaisuria/research-paper-lifecycle-skills · 50 tokens

anonymize-paper

Deep anonymization sweep for double-blind paper submissions, plus clean de-anonymization for camera-ready. Use when a researcher says "anonymize my paper", "double-blind check", "blind this submission", "remove author names", "did I leak my identity" — or, after acceptance, "de-anonymize" / "restore authors for…

ShaishavMaisuria/research-paper-lifecycle-skills · 219 tokens

make-slides

Builds a conference talk deck (Beamer or Marp markdown) from a paper draft - problem-first narrative, one claim per slide, figures reused straight from the paper's LaTeX source, sized to the real slot (12-20 minute full talk vs 5-minute lightning). Use when the user asks to make slides, build a presentation or talk…

ShaishavMaisuria/research-paper-lifecycle-skills · 189 tokens