deep-research

Conduct in-depth research across multiple sources and synthesize findings. Use when the user requests in-depth or comprehensive research, an investigation, or an in-depth research report grounded in c

SKILL.md

GitHub

Deep Research

When to Use

  • When the user requests in-depth or comprehensive research
  • When the task requires gathering information, checking facts, and synthesizing findings across multiple sources
  • When the deliverable is an in-depth research report grounded in credible sources

Deep Research Best Practices

  • When the user requests in-depth or comprehensive research, escalate the intensity of search and analysis
  • Assume no prior knowledge and start by searching for definitions and basic background information
  • Start with queries that can retrieve broader results, rather than using more precise queries
  • MUST open and read multiple relevant URLs from search results using browser tools to gather diverse perspectives
  • DO NOT rely solely on search result snippets as they are often incomplete; MUST follow up by navigating to the source URLs using browser tools
  • Use newly discovered facts to generate follow-up searches and refine the research direction
  • MUST proactively save findings and URLs from search and browsing into files as they emerge, to prevent information loss
  • NEVER deliver intermediate notes as final result; MUST rewrite into information-rich but readable final document

Parallel Processing Best Practices

  • When a step or subtask involves performing similar operations on 5 or more independent items, consider parallel processing
  • Use the agent tool for parallel processing of subtasks

Writing the Final Report

When writing the final research report, MUST also read and follow the technical-writing skill (/home/ubuntu/skills/technical-writing/SKILL.md); it defines how the report must be written and formatted.