dispatching-parallel-agents
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
63
42%
Does it follow best practices?
Impact
100%
1.17xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/dispatching-parallel-agents/SKILL.mdEvaluation results
100%
34%Multi-Service Incident Triage
Independent domain identification and parallel dispatch decision
Independent domain recognition
66%
100%
Parallel dispatch recommended
80%
100%
One investigator per domain
100%
100%
Auth service excluded from parallel work
100%
100%
Independence reasoning
20%
100%
No shared state concern noted
20%
100%
Scope per investigator defined
90%
100%
Integration step included
50%
100%
100%
10%Automated Test Failure Investigation
Quality of parallel agent prompt construction
One prompt per test file
100%
100%
Specific test names included
100%
100%
Error messages or expected/received included
100%
100%
Scope constraint present
58%
100%
Clear output specified
58%
100%
No broad 'fix everything' prompts
100%
100%
Prompts are self-contained
100%
100%
No timeout-only fix instruction
100%
100%
Prompts are distinct
100%
100%
100%
Parallel Agent Results Integration
Post-dispatch integration review and conflict detection
Agent summaries reviewed
100%
100%
Conflict identified
100%
100%
Conflict explanation
100%
100%
StorageAdapter independence noted
100%
100%
Integration order recommended
100%
100%
Spot check item identified
100%
100%
Full suite verification recommended
100%
100%
No timeout-increase recommendation
100%
100%
- Repository
- roman01la/skills-agents
- Commit
45417f2
- Evaluated
- Agent
- Claude Code
- Model
- Claude Sonnet 4.6
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.