Help us improve
Share bugs, ideas, or general feedback.
From researcher
Use when you have 2+ independent problems that can be investigated in parallel by separate agents
npx claudepluginhub jugrajsingh/skillgarden --plugin researcherHow this skill is triggered — by the user, by Claude, or both
Slash command
/researcher:dispatchingThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Validate problem independence with user, then delegate to the parallel-dispatcher agent for autonomous execution.
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.
Validate problem independence with user, then delegate to the parallel-dispatcher agent for autonomous execution.
Problem list from $ARGUMENTS (newline or comma separated).
If $ARGUMENTS is empty, ask via AskUserQuestion:
- question: "List the independent problems to investigate (one per line):"
options:
- "Enter problems separated by newlines"
- "Enter problems separated by commas"
Parse the problem list. For each pair, check for dependencies:
| Dependency Type | Detection | Action |
|---|---|---|
| Shared state | Both reference same variable/config | Flag as dependent |
| Shared files | Both modify same file | Flag as dependent |
| Ordering | One problem's output is another's input | Flag as dependent |
| Conceptual | Related but no data dependency | Allow parallel |
If dependencies found, present them via AskUserQuestion:
- question: "These problems have dependencies. How should I proceed?"
options:
- "Run sequentially in dependency order"
- "Split into independent sub-problems"
- "Proceed anyway (I accept potential conflicts)"
Maximum 5 parallel agents. If more than 5 problems:
Spawn the parallel-dispatcher agent via Task tool with:
The agent autonomously dispatches parallel sub-agents, collects results, detects conflicts, and merges findings.
After the dispatcher completes, present the merged results.
If conflicts exist, ask user to resolve:
- question: "Conflicts detected between agent findings. How to resolve?"
options:
- "I'll clarify — let me provide context"
- "Accept both interpretations"
- "Re-investigate the conflicting area"
## Dispatch Complete
Problems: {total} dispatched, {successful} successful, {failed} failed
Conflicts: {count}
{merged results document}
| Rule | Rationale |
|---|---|
| Max 5 parallel agents | Resource and context limits |
| Verify independence first | Dependent parallel tasks produce corrupt results |
| Never dispatch dependent problems in parallel | Ordering matters |
| Flag all conflicts | Silent resolution hides disagreements |
| Include failure reasons | Failed agents still provide useful signal |