Help us improve
Share bugs, ideas, or general feedback.
From claude-code-learn
Deep research a topic using parallel agents, then synthesize and save comprehensive knowledge to ~/.claude/learnings/.
npx claudepluginhub ourines/claude-code-learn --plugin claude-code-learnHow this skill is triggered — by the user, by Claude, or both
Slash command
/claude-code-learn:deep-learnThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Deep research a topic using parallel agents. Each agent explores a different dimension simultaneously, then results are synthesized into a comprehensive knowledge file.
Conducts thorough multi-source research on complex topics, with interactive depth, focus, and format selection for tailored synthesis.
Conducts systematic topic research with complexity scoring (4-10), thinking mode selection (Standard/Think/Ultrathink), and generates structured markdown documentation for knowledge capture.
Conducts multi-source research on topics via web search, documentation queries, matrix memory, and GitHub using a 5-phase pipeline. Outputs markdown reports at quick/standard/exhaustive depths.
Share bugs, ideas, or general feedback.
Deep research a topic using parallel agents. Each agent explores a different dimension simultaneously, then results are synthesized into a comprehensive knowledge file.
Topic string from $ARGUMENTS.
Convert topic to slug (lowercase, hyphens). Check ~/.claude/learnings/<slug>.md.
If exists, read frontmatter. Ask user: Update, Replace, or Cancel.
mkdir -p ~/.claude/learnings
Determine the topic category, research dimensions, and agent count. Then decide how to orchestrate.
You have two orchestration modes — choose based on the situation:
Fire-and-forget parallel agents. Each works independently, you synthesize after all return.
Best for:
Create a team with shared task list. Agents can communicate, report partial findings, and you can dynamically assign follow-up work.
Best for:
Decision guideline:
| Signal | → Mode |
|---|---|
| You can enumerate all research dimensions upfront | Subagents |
| Topic is well-scoped (e.g., "React useEffect cleanup") | Subagents |
| Topic is broad or vague (e.g., "Kubernetes networking") | Team |
| You might need a second research round based on findings | Team |
| Agent findings may overlap or conflict and need real-time coordination | Team |
Agent count guideline:
| Topic Type | Suggested Agents |
|---|---|
| Library/Framework | 3-4: docs, code patterns, gotchas, ecosystem |
| Concept/Pattern | 2-3: theory, implementations, comparisons |
| Tool/CLI | 2-3: official docs, config recipes, troubleshooting |
| Language Feature | 2-3: spec/docs, adoption patterns, edge cases |
| Complex/Broad Topic | 4-5: split by subtopic areas |
You are NOT locked into these. Use your judgment. Scale up or down as needed.
Use the Task tool with subagent_type: "general-purpose" to spawn agents in parallel (multiple Task calls in a single message). Each gets a focused prompt and returns structured findings.
TeamCreate — create a research teamTaskCreate — create tasks for each research dimensionTask with team_name — spawn named agents, assign tasksTaskList. When an agent reports interesting findings via SendMessage, decide whether to:
Research "<topic>" focusing on: <specific dimension>.
Use these tools as needed:
- WebSearch / WebFetch for web sources
- mcp__context7__resolve-library-id + query-docs for library docs
- mcp__gh_grep__searchGitHub for real-world code
Return your findings as structured markdown:
## <Dimension Name>
### Key Findings
- ...
### Code Examples
```lang
...
Be thorough but concise. Prioritize accuracy and code correctness. Focus ONLY on your assigned dimension — other agents cover the rest.
### 4. Synthesize Results
After all agents return, merge their findings:
1. **Deduplicate** — remove overlapping content, keep the better version
2. **Cross-validate** — if agents disagree, flag the conflict or verify
3. **Organize** — structure into the standard knowledge format
4. **Attribute** — collect all sources from all agents
### 5. Save Knowledge File
Write to `~/.claude/learnings/<slug>.md`:
```markdown
---
topic: "<Original Topic Name>"
slug: "<slug>"
category: "<library|concept|tool|language-feature>"
created: "<YYYY-MM-DD>"
last_verified: "<YYYY-MM-DD>"
confidence: "<high|medium|low>"
tags: [<relevant, tags>]
sources_count: <N>
research_depth: "deep"
agents_used: <N>
strategy: "<subagents|team>"
---
# <Topic Name>
## TL;DR
<2-4 sentences: what it is, key capabilities, primary use case.>
## Core APIs / Concepts
### <Name>
- **Signature/Usage**: `<code>`
- **Purpose**: <one line>
- **Example**:
```<lang>
<minimal working example>
<Deeper material that basic /learn would skip: internals, performance, edge cases, architecture decisions.>
### 6. Knowledge Graph Indexing (Optional)
If `mcp__memory__create_entities` is available:
```json
{
"name": "<Topic Name>",
"entityType": "learning",
"observations": [
"Saved to ~/.claude/learnings/<slug>.md",
"Category: <category>",
"Research depth: deep (<N> agents)",
"Tags: <tag1>, <tag2>"
]
}
Tell the user:
// untested.high only when multiple agents' sources agree.research_depth: "deep" and agents_used fields in frontmatter distinguish deep-learn output from regular /learn.