research — Skills — getagentictools

What it does

You'd need to read many files to find the few that are relevant.

You'd need to wade through long test output, CI logs, or stack traces to extract a failure.

You'd need to survey how a pattern, API, or symbol is used across the whole repo.

You'd need to read and summarize a large diff or PR.

The question has several independent sub-parts that could be investigated separately.

"What's the root cause of this failing test?" (the subagent reads the logs and traces the code; you get the cause)

"How is SessionManager used across the codebase?" (the subagent greps and reads; you get a summary with call sites)

Requirements & configuration

You'd need to read many files to find the few that are relevant.

You'd need to wade through long test output, CI logs, or stack traces to extract a failure.

You'd need to survey how a pattern, API, or symbol is used across the whole repo.

You'd need to read and summarize a large diff or PR.

Reading 2–3 files you already know you need. Just read them directly; delegation adds latency for no context savings.

Source

Repository: https://github.com/warpdotdev/common-skills

research FAQ

What does the research skill do?

Delegate noisy investigation to one or more subagents so the orchestrator's context stays clean, then work from the distilled answer. Use this skill whenever answering a question would require reading many files, long logs, large diffs, or wide codebase surveys — i.e. when producing the answer generates far more noise than the answer itself. Use it for "how does X work", "where is Y used", "what's the root cause of Z", "summarize this PR/log" style questions, and reach for it liberally before reading a pile of files inline. You'd need to read many files to find the few that are relevant. You'd need to wade through long test output, CI logs, or stack traces to extract a failure.

What does research require?

You'd need to read many files to find the few that are relevant. You'd need to wade through long test output, CI logs, or stack traces to extract a failure. You'd need to survey how a pattern, API, or symbol is used across the whole repo. You'd need to read and summarize a large diff or PR. Reading 2–3 files you already know you need. Just read them directly; delegation adds latency for no context savings.

How do I install research?

Run: npx -y skills add https://github.com/warpdotdev/common-skills --skill research --agent claude-code — the source lives at github.com/warpdotdev/common-skills.

Maintain research?

Let people know it's listed here — add the badge (live metrics, light/dark aware) or a plain link to your README or docs.

[![research on getagentictools](https://getagentictools.com/badge/skills/warpdotdev-common-skills-research.svg)](https://getagentictools.com/skills/warpdotdev-common-skills-research?ref=badge)

npx agentictools info skills/warpdotdev-common-skills-research

The second line is the CLI lookup for this page — handy in READMEs and docs.