deep-research-synthesis
Skill1 starsChanged 30 days agoMITView on GitHub
This skill should be used for thorough, multi-source research that must be credible and well-sourced, and for turning that research into a synthesis. Trigger phrases: "deep research", "comprehensive research", "research report", "investigate X thoroughly", "find best practices with sources", "market/competitive research", "synthesize these findings", "fact-check this", "is this claim actually true?". Use it whenever a question needs rigorous, cited research rather than a quick answer.
In this repository7 other files it gives its agents.
- conversion-copywritingSkill
- ecommerce-cro-auditSkill
- experiment-designSkill
- getting-startedSkill
- outbound-and-positioningSkill
- report-information-designSkill
- voc-researchSkill
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
- Distinctive: line 21
Ground in primary/first-party data first: If the subject owns data (analytics, a repo, internal docs), pull it before web opinion.
- Distinctive: line 23
Demand provenance: Every statistic gets a source name, URL, and year.
- Very specific: line 26
Reflect and stop deliberately: After each pass: what did I find, what's missing, is coverage enough?
≈ “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
Deep Research & Synthesis
Produce research a skeptical expert would trust: every load-bearing claim sourced, reliability labeled, conflicts surfaced, and the synthesis honest about what's known vs. estimated.
Principles
- Scope before searching. Pin down the question, audience, deliverable, and depth. For research, start an initial recon search immediately rather than gating everything on a clarifying question.
- Ground in primary/first-party data first. If the subject owns data (analytics, a repo, internal docs), pull it before web opinion.
- Fan out, don't trickle. Decompose into independent streams; research in parallel (parallel subagents when available).
- Demand provenance. Every statistic gets a source name, URL, and year.
- Tier reliability. Primary/academic/first-party vs directional/vendor; use directional figures for direction only (
references/source-tiering.md). - Verify the load-bearing claims against primary sources; drop or label what doesn't survive.
- Reflect and stop deliberately. After each pass: what did I find, what's missing, is coverage enough? Stop when saturated (
references/research-rigor.md). - Surface conflicts; never fabricate.
Workflow
- Scope & clarify, then write a one-paragraph research brief (constraints stated, unknowns marked open).
- Recon the subject and any first-party data to sharpen the stream plan.
- Plan 3–5 independent streams mapped to eventual report sections.
- Fan out with precise, self-contained briefs (
references/subagent-briefs.md); pull interactive/first-party data yourself. - Collect with discipline (URLs + years; concrete examples; note source type).
- Tier, score, and verify (credibility scoring + primary-over-secondary in
references/research-rigor.md); re-fetch primaries for load-bearing stats. - Coverage check, then synthesize — lead with the conclusion, weave inline citations, show conflicts, end with a tiered source list. Hand to
report-information-designfor a polished deliverable.
Reference map
references/research-playbook.md— recon→plan→fan-out→verify→synthesize loop in detail.references/research-rigor.md— query expansion, the reflection/gap loop, stop conditions, credibility scoring, self-contained briefs + verbatim-return contract (from gpt-researcher / STORM / open_deep_research).references/source-tiering.md— the reliability rubric, confidence phrasing, handling conflicts.references/subagent-briefs.md— the parallel-research brief template + worked examples.
Engagement context
At the start of a task, check for the engagement brief (default ./cro-engagement.md, created by the getting-started skill / /kickoff). If it exists, read it first and tailor scope, audience, and depth to it. If it's missing and the work is more than a one-off, offer to capture one via getting-started.
Related skills
report-information-design (turn the synthesis into a report), ecommerce-cro-audit (a frequent consumer of this skill's evidence). Agents: deep-researcher runs a single stream; cro-verifier adversarially checks the result.
Honesty guardrails
Only cite URLs actually opened in this session, and run python3 ${CLAUDE_PLUGIN_ROOT}/skills/report-information-design/scripts/check_citations.py <synthesis-file> on the synthesis before handing it on (LLM research tools fabricate or break a meaningful share of links). For a load-bearing claim surfaced only by AI search, find a second independent source. Label vendor/self-interested figures directional; distinguish "verified against primary" from "widely cited but untraced"; prefer recent sources for fast-moving topics; include a short source-reliability appendix so the reader can defend the work.
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.

