dispatching-parallel-agents

tessl i github:obra/superpowers --skill dispatching-parallel-agents

Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies

58%

Overall

Validation — 88%

Implementation — 77%

Activation — 7%

SKILL.md

Review

Evals

Validation

88%

Warnings & errors only

Criteria	Description	Result
metadata_version	'metadata' field is not a dictionary	Warning
license_field	'license' field is missing	Warning

	Total	14 / 16 Passed

Implementation

77%

This is a strong, actionable skill with clear workflow guidance and concrete examples. The main weakness is some redundancy between sections (real example appears twice in different forms) and the document could be more concise by consolidating related sections. The actionability and workflow clarity are excellent with specific prompts and verification steps.

Suggestions

Consolidate 'Real Example from Session' and 'Real-World Impact' sections - they contain overlapping information

Consider moving the detailed real-world example to a separate EXAMPLES.md file and referencing it

Merge 'When to Use' and 'When NOT to Use' sections into a single decision guide to reduce repetition

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 agent prompt structure section is copy-paste ready.	3 / 3
Workflow Clarity	Clear 4-step workflow (Identify → Create → Dispatch → Review) with explicit verification steps at the end. The decision tree diagram and numbered steps make the process unambiguous, and the verification section provides a clear checklist for integration.	3 / 3
Progressive Disclosure	Content is well-structured with clear sections, but it's a monolithic document that could benefit from splitting detailed examples into separate files. The real example section adds significant length that could be referenced externally.	2 / 3
	Total	10 / 12 Passed

Activation

This description fails to explain what the skill does, focusing only on 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 actual capabilities.

Suggestions

Add concrete actions describing what this skill does (e.g., 'Executes multiple tasks in parallel using subagents' or 'Coordinates concurrent workflows')

Replace technical jargon with natural trigger terms users would say, such as 'parallel tasks', 'multiple things at once', 'batch processing', or 'simultaneous work'

Restructure to lead with capabilities before the 'Use when' clause, following the pattern: '[What it does]. Use when [trigger conditions].'

Dimension	Reasoning	Score
Specificity	The description contains no concrete actions - it doesn't specify what the skill actually does, only when to use it. 'Independent tasks' and 'shared state' are abstract concepts without specific capabilities listed.	1 / 3
Completeness	The description only addresses 'when' (facing 2+ independent tasks) but completely omits 'what' - there's no explanation of what this skill actually does or what actions it performs.	1 / 3
Trigger Term Quality	Uses technical jargon like 'shared state' and 'sequential dependencies' that users would rarely say naturally. Missing common trigger terms users might actually use like 'parallel', 'multiple tasks', 'at the same time', or 'batch'.	1 / 3
Distinctiveness Conflict Risk	The criteria of '2+ independent tasks without shared state' provides some specificity that could distinguish it from single-task skills, but 'independent tasks' is still vague enough to potentially overlap with many workflow or automation skills.	2 / 3
	Total	5 / 12 Passed

Reviewed

16 days ago

Table of Contents

Validation Implementation Activation

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.