dispatching-parallel-agents
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
Install with Tessl CLI
npx tessl i github:obra/superpowers --skill dispatching-parallel-agents63
Quality
42%
Does it follow best practices?
Impact
100%
1.17xAverage score across 3 eval scenarios
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/dispatching-parallel-agents/SKILL.mdQuality
Discovery
7%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description fails to explain what the skill actually does, only describing when to use it. The technical language ('shared state', 'sequential dependencies') is not user-friendly, and the complete absence of concrete actions makes it nearly impossible for Claude to understand the skill's capabilities.
Suggestions
Add a clear 'what' statement describing the concrete capability (e.g., 'Executes multiple tasks in parallel to improve efficiency' or 'Spawns concurrent sub-agents to handle independent workstreams')
Replace technical jargon with natural trigger terms users would say, such as 'parallel tasks', 'run simultaneously', 'batch processing', 'multiple things at once'
Include specific examples of task types this skill handles (e.g., 'file processing', 'API calls', 'code analysis across multiple files')
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'independent tasks' and 'worked on' without specifying any concrete actions. It describes a condition for use rather than what the skill actually does. | 1 / 3 |
Completeness | Only provides a 'when' clause but completely omits 'what' the skill does. There's no explanation of the capability or actions this skill performs. | 1 / 3 |
Trigger Term Quality | Contains technical jargon ('shared state', 'sequential dependencies') that users would not naturally say. Missing natural trigger terms like 'parallel', 'multiple tasks', 'batch', or 'concurrent'. | 1 / 3 |
Distinctiveness Conflict Risk | The concept of '2+ independent tasks' is somewhat specific to parallel/concurrent execution, but the vague phrasing could overlap with task management, workflow, or orchestration skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, actionable skill that clearly teaches parallel agent dispatch with concrete examples and good workflow structure. The main weakness is some redundancy between sections (real example appears twice in different forms) and the content could be more concise by consolidating related sections. The decision flowchart and prompt templates are particularly strong.
Suggestions
Consolidate 'Real Example from Session' and 'Real-World Impact' sections - they describe the same scenario and add redundant tokens
Merge 'When to Use' and 'When NOT to Use' into a single decision section to reduce repetition of criteria
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient but includes some redundancy - the 'Real Example from Session' and 'Real-World Impact' sections largely repeat the same information, and some concepts are explained multiple times (when to use vs when NOT to use could be consolidated). | 2 / 3 |
Actionability | Provides concrete, executable guidance with specific TypeScript dispatch syntax, detailed agent prompt templates with exact structure, and real examples showing exact test file names and error messages. The prompt structure section is copy-paste ready. | 3 / 3 |
Workflow Clarity | Clear 4-step sequence (Identify → Create → Dispatch → Review) with explicit verification steps at the end. The decision flowchart (dot graph) clearly shows when to use the pattern, and the verification section provides explicit checkpoints for integration. | 3 / 3 |
Progressive Disclosure | Content is well-structured with clear sections, but it's somewhat monolithic at ~150 lines. The real example and real-world impact sections could be consolidated or moved to a separate file. No external references are provided for advanced patterns or related skills. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Reviewed
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.