About research
A research skill for answering open questions with evidence rather than implementing changes. It prioritizes repository and documentation sources, cites findings, and identifies what remains uncertain.
Key features
- 01Defines a precise research question
- 02Searches repositories and docs first
- 03Investigates independent questions in parallel
- 04Connects findings to their sources
- 05Separates verified facts from inferences
Use cases
- 01Find evidence for behavior in a codebase
- 02Research external SDK or API documentation
- 03Investigate multiple independent open questions
Install
Copy the command and run it in a terminal.
$
npx skills add https:/After installing, type/researchin Claude Code to confirm it loaded.
Details
From the project READMEResearch
Use this skill when the next step depends on something not yet known. Research answers questions; it does not implement.
This is the canonical research lane. deep-dive, sciomc, and autoresearch
route here.
Goal
Replace assumptions with evidence, and say plainly what remains uncertain.
Workflow
- State the question precisely enough to know when it is answered.
- Search the repo and its docs first — local evidence outranks recollection.
- For external SDKs, frameworks, or APIs, consult official documentation.
- Sweep more than one way when the answer could hide: by file, by symbol, by caller, by history.
- Synthesize into findings, each tied to where it came from.
Scale
- Narrow lookup — answer it directly.
- Multiple independent questions — investigate in parallel.
- Unknown-size discovery — keep going until additional passes surface nothing new.
Rules
- Cite the source: file and line, or the document consulted.
- Distinguish what was verified from what was inferred.
- Report contradicting evidence rather than picking the tidier story.
- Do not implement as a side effect of researching.
Output
- The question
- Findings, each with its source
- What remains unknown or unverifiable
- Recommended next step, if one follows
Comments
Markdown supported