Researcher

Conducts deep research and produces structured survey documents for decision-making.

1|Updated Apr 25, 2026
One-click install
npx skills add https://github.com/htxryan/claude-code-config-profiles --skill researcher-htxryan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Researcher
Source: https://github.com/htxryan/claude-code-config-profiles/tree/main/.agents/skills/compound/researcher
Command: npx skills add https://github.com/htxryan/claude-code-config-profiles --skill researcher-htxryan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often make architectural or technical decisions without a thorough understanding of the landscape. This Skill automates deep, PhD-level research on a topic and produces a structured survey document so decisions are grounded in evidence rather than guesswork. ## Core Features & Use Cases - Parallel Research Subagents: Spawns web search, codebase exploration, and docs scanning subagents simultaneously to gather comprehensive findings. - Structured Survey Output: Synthesizes findings into a rigorous template with abstract, taxonomy, per-approach analysis, comparative synthesis, open problems, and full references. - Memory & Docs Integration: Searches existing knowledge via ca search and checks docs/research/ and ADRs to avoid duplicating prior work. - Use Case: Before choosing a state management approach, ask for a survey of options; the Skill produces docs/research/state-management.md with trade-off tables and practitioner resources for the ADR process. ## Quick Start Ask the agent to research a topic, for example: research approaches to distributed caching and produce a survey document in docs/research.

Frequently Asked Questions about Researcher

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a research survey document for a technical topic?▼

Invoke the Researcher skill with your topic and scope. It spawns parallel subagents for web search, codebase exploration, and docs scanning, then synthesizes findings into a structured survey saved at docs/research/<topic-slug>.md.

What structure does the research output document follow?▼

Every document follows a fixed template: abstract, introduction, foundations, taxonomy of approaches, per-approach analysis, comparative synthesis table, open problems, conclusion, references, and practitioner resources.

Does the research skill check for existing knowledge before starting?▼

Yes. It runs ca search against memory with topic keywords and scans docs/research/, docs/compound/research/, and docs/decisions/ for prior surveys and ADRs that overlap with or constrain the research scope.

Will the research document recommend a specific approach?▼

No. The skill explicitly avoids recommendations and presents trade-offs only. Decision-making is delegated to the ADR process, keeping the survey a neutral landscape analysis.

What are common quality problems in generated research documents?▼

Common pitfalls include shallow treatment of approaches, missing taxonomy, recommendation bias, undeduplicated subagent findings, and skipping the comparative synthesis table. The skill's quality criteria checklist guards against each.