Individual skill

deep-research

Runs a thorough multi-source research process - decompose the question, gather independent sources, cross-check, synthesize - and delivers a structured, cited brief with confidence levels and gaps. Use when someone asks "research this topic in depth", "give me everything on X", "what does the evidence say about Y", or needs a broad question answered from secondary sources with citations. Do NOT use for designing a study that collects new data - use primary-research instead; for distilling an already-gathered pile of 20+ sources into themes, use research-synthesis; for verifying one discrete claim, use fact-checker.

skills/deep-research/SKILL.md

Read pinned source

Source commit 97a13607d669157a4a16d5ba79b77f208319f7b9

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
24
Repository last updated
Oct 13, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Deep Research

Go wide, then deep: triangulate across independent sources and report what was actually found, including the gaps. The costly failure this skill prevents is the confident brief built on an echo - a dozen articles that all trace to one blog post or one press release, presented as consensus. "Not found" is a legitimate finding; a smooth answer papering over thin evidence is not.

## Inputs to collect

1. The research question, restated until the user confirms it. Ambiguity here multiplies through every later step.
2. What decision or output the research feeds. A brief informing a purchase differs from one informing a publication.
3. Scope boundaries: geography, industry, population, and what is explicitly out of scope.
4. Depth and deadline. Default: 3-6 sub-questions, at least two independent sources per sub-question.
5. Known sources or prior work to build on. Treat supplied sources as leads to appraise, not settled evidence.

Label any assumed scope as an assumption.