synthesize-research
Skill0 starsChanged 4 months agoMITView on GitHub
Synthesizes multi-source research into a decision-ready summary. Use for research synthesis, literature or market scans, or collapsing many notes into findings. Do not use when the primary output is a competitor comparison matrix (use competitive-brief).
3 other projects use a version of this.
Adopted by
Most recently taken up by
- nisarth/claude-skills-storetheir own version, first seen Nov 8, 2026
- anthropics/knowledge-work-pluginstheir own version, first seen Oct 13, 2026
- lensetek/Research-Agent-Skills-Collectiontheir own version, first seen Jun 18, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- anthropics/knowledge-work-plugins★ 35ksame name
- lensetek/Research-Agent-Skills-Collection★ 1same name
- nisarth/claude-skills-store★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository40 other files it gives its agents.
- address-pr-feedbackSkill
- architectureSkill
- code-reviewSkill
- code-structureSkill
- competitive-briefSkill
- contract-guardSkill
- debugSkill
- deep-workSkill
- dependency-upgradeSkill
- deploy-checklistSkill
- diagnoseSkill
- documentationSkill
- explain-pr-step-by-stepSkill
- feedback-checkpointSkill
- grill-meSkill
- grill-with-docsSkill
- handoffSkill
- improve-codebase-architectureSkill
- incident-responseSkill
- memory-managementSkill
- observabilitySkill
- plan-criticSkill
- plan-from-rfcSkill
- pr-babysitterSkill
- prototypeSkill
- queue-checkSkill
- rebase-onto-mainSkill
- releaseSkill
- security-reviewSkill
- setup-engineering-skillsSkill
- squash-and-pushSkill
- system-designSkill
- tddSkill
- tech-debtSkill
- testing-strategySkill
- to-issuesSkill
- to-prdSkill
- triageSkill
- verification-before-completionSkill
- zoom-outSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 25
Every material claim needs a source or an explicit [inference] tag.
- Distinctive: line 26
Prefer primary sources over secondary summaries when available.
- Distinctive: line 27
Do not hide dissenting evidence.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Synthesize Research
Collapse sources into findings, tensions, and recommendations with traceable citations.
Workflow
- Question — one primary question; optional sub-questions.
- Intake — list sources (URL, doc, interview notes) with dates and credibility notes.
- Extract — atomic claims with source IDs; separate fact / opinion / anecdote.
- Cluster — themes; note agreements and contradictions. See
references/synthesis-template.md. - Conclude — answer the question; confidence; what would change the answer.
- Recommend — next actions or product implications, each tied to findings.
Constraints
- Every material claim needs a source or an explicit
[inference]tag. - Prefer primary sources over secondary summaries when available.
- Do not hide dissenting evidence.
Verification
- Primary question answered
- Findings mapped to sources
- Contradictions surfaced
- Confidence and open questions stated
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.