research · yeachan-heo — Claude Code skill: what it does, how to install
The research skill investigates open questions in a codebase and its docs, then ties findings to sources. Use it when an unresolved fact affects your next step.
MIT 1 installs ★ 40,997 updated 2026-10-24
npx skills add Yeachan-Heo/oh-my-claudecode --skill research -a claude-codeWhat research does
The skill first sharpens the question, then searches the repository and its documentation. For external SDKs, frameworks, and APIs, it checks official documentation. When an answer might be hidden in different parts of a project, it searches by file, symbol, caller, or history.
Its findings point to their sources and distinguish verified facts from inferences. It also reports conflicting evidence instead of choosing one account. For several independent questions, it can investigate in parallel; open-ended discovery continues while further passes uncover new information. Research does not change the project, so implementation remains a separate step.
What it helps with
- trace calls to a function across a repository
- check an SDK behavior against official documentation
- investigate a mismatch between docs and code
- report sourced findings for several independent questions
Example prompts for the agent
- Trace where this function is called in the project and cite the files and lines.
- Check the official documentation for how this API handles errors.
- Compare the docs with the code and separate verified facts from inferences.
How to install research
1Skills CLI (Vercel)
npx skills add Yeachan-Heo/oh-my-claudecode --skill research -a claude-code2Manually: put the files in place
~/.claude/skills/research/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/research/
1Skills CLI (Vercel)
npx skills add Yeachan-Heo/oh-my-claudecode --skill research -a codex2Manually: put the files in place
.agents/skills/research/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add Yeachan-Heo/oh-my-claudecode --skill research -a cursor2Manually: put the files in place
.cursor/skills/research/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install Yeachan-Heo/oh-my-claudecode skills/research2Manually: put the files in place
.github/skills/research/SKILL.md1Skills CLI (Vercel)
npx skills add Yeachan-Heo/oh-my-claudecode --skill research -a gemini-cli2Platform CLI
gemini skills install https://github.com/Yeachan-Heo/oh-my-claudecode --path skills/researchManually: put the files in place
.devin/skills/research/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add Yeachan-Heo/oh-my-claudecode --skill research -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about research
How do I install research in Claude Code?
Run npx skills add Yeachan-Heo/oh-my-claudecode --skill research -a claude-code. The skill file is ~/.claude/skills/research/SKILL.md.
What does research do?
It investigates a question using the repository, its docs, and official materials for external APIs, then cites its findings. It does not implement changes.
How does research handle conflicting evidence?
It reports contradictions rather than selecting the tidier explanation, and marks which findings were verified versus inferred.
Source text
SKILL.md · MIT
--- name: research description: Investigate an open question and return grounded, sourced findings --- # Research 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 1. State the question precisely enough to know when it is answered. 2. Search the repo and its docs first — local evidence outranks recollection. 3. For external SDKs, frameworks, or APIs, consult official documentation. 4. Sweep more than one way when the answer could hide: by file, by symbol, by caller, by history. 5. 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
© Yeachan-Heo · MIT · Yeachan-Heo/oh-my-claudecode
Similar skills
All skills for Science and research →research by other authors comes first.