
Deep Research
Scope → fan out → adversarially verify every load-bearing claim → cited synthesis with confidence and dissent. A comprehensive research harness.
v1.0.0 · ~908 tokens · ⬇ 7 · Updated July 6, 2026
What it does
A comprehensive research skill: scopes the question, fans out across angles and primary sources, then verifies every load-bearing claim adversarially (trace to primary, steel-man the counter, watch stale/self-report/benchmark-mixing/negative-claim traps, rate confidence), and synthesizes a cited report that shows disagreement and names what it couldn't verify. Never invents a citation.
Example uses
Research a buy-versus-build decision
You are about to commit budget in a vendor-claim-heavy market and need verified facts, not marketing pages.
Research whether we should buy a managed vector database or run pgvector ourselves for a 50-million-embedding workload. Fan out across vendor docs, independent benchmarks, and practitioner postmortems; trace every performance and pricing claim to a primary source, and flag benchmarks that were measured differently across sources instead of comparing them. End with a cited recommendation, a confidence rating per finding, and what you could not verify.Trace a viral statistic
A number is repeated everywhere and you need to know where it actually comes from before citing it yourself.
The claim that "40% of enterprise AI projects will be canceled by 2027" is quoted in dozens of articles. Trace it to its actual origin — the original report, its methodology, and what the source really said versus how it is being quoted. Steel-man both the claim and its critics, then tell me with what confidence I can use it in a board deck, with citations.Survey a fast-moving field
You need a current, sourced picture of a technology landscape where most articles are stale or vendor-written.
Give me a fact-checked report on the state of on-device LLM inference as of this month: which model sizes actually run on current flagship phones and at what speeds, per primary sources — vendor engineering blogs, published benchmarks, papers, not aggregator listicles. Show where sources disagree instead of averaging them into false consensus, rate confidence per finding, and list the open questions that would change the conclusions.Install
# 1. Create the skill folder in your Claude setup mkdir -p ~/.claude/skills/deep-research # 2. Download SKILL.md into it (or move the file you just downloaded) # → ~/.claude/skills/deep-research/SKILL.md # 3. Claude Code auto-discovers it on next launch.
Inside the skill
---
name: deep-research
description: Run a rigorous, multi-source research investigation and produce a cited, fact-checked report. Use for any question that needs depth and verification — market/competitor/technical research, "research X thoroughly", "give me a report on Y", "what's the state of Z". Fans out, verifies claims adversarially, synthesizes with citations. A comprehensive skill.
---
# Deep Research
Shallow research confidently repeats whatever ranks first. Deep research triangulates,
verifies, and tells you how sure it is. The output is a report you could act on, with the
receipts and the caveats.
## Phase 0 — Scope (don't skip)
- Pin the exact question. If it's vague ("is X good?"), narrow it: good for whom, versus what,
on which criteria, as of when. Ask 1-2 clarifying questions if the scope changes the answer.
- Decide what a good answer looks like (the criteria/dimensions) before searching — so you
research against a frame, not vibes.
## Phase 1 — Fan out (breadth first)
- Search several angles, not one query reworded: by entity, by claim, by counter-claim, by
time ("X 2026"), by source type (primary docs, data, expert commentary, dissent).
- Prefer PRIMARY sources: the vendor's own doc/pricing, the paper, the filing, the dataset —
over aggregators and listicles that summarize (and distort) them.
- Cast wide enough to find disagreement. If every source agrees, you probably haven't found
the critique yet — keep looking for it.
## Phase 2 — Verify (the part that makes it "deep")
For every load-bearing claim (a number, a "best", a causal statement):
- **Trace to the primary source.** A figure repeated by ten blogs traced to zero primary
sources is a rumor with good PR. Find where it actually originated — or drop it.
- **Adversarially check it**: actively look for the source that contradicts it. Steel-man the
other side. A claim that survives a genuine attempt to refute it is worth keeping.
- **Watch the traps**: stale data presented as current; a vendor's self-report treated as
independent; correlation dressed as causation; a benchmark measured differently across sources
(don't compare them); a negative claim ("X has no Y") that's just missing from your sources, not false.
- Rate confidence per claim: confirmed (multiple independent/primary) · likely · single-source · disputed.
## Phase 3 — Synthesize
- Answer the actual question first, plainly (the "if you read one line" version).
- Then the structured findings by dimension, each with its evidence and confidence.
- **Show the disagreement** where sources conflict — don't average it away into a false consensus.
- State what you could NOT verify and what would change the conclusion. Uncertainty named is
trustworthy; uncertainty hidden is a liability.
- **Cite every load-bearing claim** to its source. A report you can't check isn't research, it's an opinion.
## Rules
- Primary sources over summaries; a claim's value is its traceability, not its repetition count.
- Verify before you include; adversarially, not just confirmingly. Confirmation bias is the whole failure mode.
- Report confidence and dissent honestly. "I'm not sure, here's why" beats a confident wrong answer.
- Never invent a citation. If you can't source it, say so or cut it.
## Output
```
RESEARCH — <question>
Answer (1 paragraph): <the direct answer, plainly>
Findings by dimension:
<dimension> — <finding> [confidence] — sources: <cited>
Disagreements: <where sources conflict + your read>
Couldn't verify: <open questions>
What would change this: <the decisive unknowns>
Sources: <list — primary flagged>
```
Changelog
- v1.0.02026-07-03Initial clean-room write.
Frequently asked questions
Is Deep Research free?
Yes. Deep Research is free to download and MIT-licensed.
Where do I install Deep Research?
Place the SKILL.md file in ~/.claude/skills/deep-research/ and Claude Code auto-discovers it on next launch.
How many tokens does Deep Research use?
About 908 tokens — it is designed to be token-lean.

We're developers and SaaS builders who use these tools daily in production. Every review comes from hands-on experience building real products — DealPropFirm, ThePlanetIndicator, PropFirmsCodes, and many more. We don't just review tools — we build and ship with them every day.
Written and tested by developers who build with these tools daily.