deep-research

Files (4)

• SKILL.md
• reporting.md · references/
• search-strategies.md · references/
• source-evaluation.md · references/

SKILL.md (first lines)

# Deep research

Establish the question, decision criteria, and requested depth from the task. Ask only for missing information that would materially change the research. Preserve the user's named topic or model in searches; do not replace an unfamiliar or fast-changing name with a familiar one.

Read primary sources and distinguish their claims from your interpretation. Use current local code for questions about the installed implementation. Follow leads and seek independent evidence where a consequential, contested, or empirical claim needs it. One authoritative source may settle a documented product fact; a fixed source count does not establish truth.

Use these references only when needed:

- [Search strategies](references/search-strategies.md): discovery is stalled, terminology is unclear, or the question spans several kinds of sources.
- [Source evaluation](references/source-evaluation.md): sources conflict, evidence is indirect, or a study or benchmark needs scrutiny.
- [Reporting](references/reporting.md): producing a substantial comparison or research artifact.

Answer with citations near the claims they support. Paraphrase sources, reserve short marked quotes for exact wording that matters, and organize around findings and disagreements rather than one summary per source. Use the host's citation format and quotation limits.

Continue until the requested questions are supported or the unresolved gaps are identified. Follow remaining leads that could change the answer within the agreed scope and budget. Report unavailable evidence and limitations; do not imply exhaustive coverage or start unrelated research to fill a template.

From petekp/claude-code-setup, MIT.

More from petekp/claude-code-setup