deep-research
Research a topic thoroughly in this repo and return a structured summary with file references. Use when you need to understand how something works, find patterns across modules, or audit implementations.
Best use case
deep-research is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Research a topic thoroughly in this repo and return a structured summary with file references. Use when you need to understand how something works, find patterns across modules, or audit implementations.
Teams using deep-research should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/deep-research/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How deep-research Compares
| Feature / Agent | deep-research | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Research a topic thoroughly in this repo and return a structured summary with file references. Use when you need to understand how something works, find patterns across modules, or audit implementations.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Deep Research (Explore) Research $ARGUMENTS thoroughly. ## Required output 1. **Findings**: 3-10 bullets, each backed by specific file references 2. **Key code locations**: a short list of the most important paths to read next 3. **Open questions / unknowns**: what you could not confirm from the repo ## Method - Start broad: use Glob to find likely modules. - Then go deep: use Grep to locate exact identifiers and call sites. - Read the top-ranked files and follow references until the flow is clear. - Stop when you hit diminishing returns (two additional searches yield no new information). ## Rules - Be evidence-driven: always cite file paths. - Do not implement changes; this skill is for investigation only.