Help us improve
Share bugs, ideas, or general feedback.
From researcher
Use when you need to deeply investigate a codebase question using parallel sub-agents with persistent report output
npx claudepluginhub jugrajsingh/skillgarden --plugin researcherHow this skill is triggered — by the user, by Claude, or both
Slash command
/researcher:researchingThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Gather the research question from the user, then delegate to the research-orchestrator agent for autonomous parallel investigation.
Creates p5.js generative art with seeded randomness, noise fields, and interactive parameter exploration. Use for algorithmic art, flow fields, or particle systems.
Share bugs, ideas, or general feedback.
Gather the research question from the user, then delegate to the research-orchestrator agent for autonomous parallel investigation.
Research question from $ARGUMENTS.
If $ARGUMENTS is empty, ask via AskUserQuestion:
- question: "What would you like to research?"
options:
- "How does X work?"
- "Where is X implemented?"
- "What patterns does X use?"
- "Compare approaches for X"
Create a URL-safe slug from the research question (lowercase, hyphens, max 50 chars, strip articles).
mkdir -p docs/research
Spawn the research-orchestrator agent via Task tool with:
The agent autonomously decomposes the question, dispatches parallel specialist agents (locator, analyzer, pattern-finder), reconciles results, and writes the report to docs/research/{slug}-report.md.
After the orchestrator completes, read and present the report summary.
Offer next steps via AskUserQuestion:
- question: "Research complete. What next?"
options:
- label: "Deep dive"
description: "Investigate a specific finding further"
- label: "Create plan"
description: "Use findings to create an implementation plan"
- label: "Done"
description: "Research is sufficient"
planner:planning skill, passing the report path| Rule | Rationale |
|---|---|
| file:line references mandatory | Every technical claim must be verifiable |
| Synonym expansion for searches | Single terms miss aliased concepts |
| Progressive disclosure | Overview first, details on demand |
| Max 5 parallel agents | Resource and context limits |
| No fabricated paths | If not found, report that clearly |