dispatching-parallel-agents

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

Quality

42%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/dispatching-parallel-agents/SKILL.md

Quality

Discovery

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 only provides a vague trigger condition without ever stating what the skill does. It lacks concrete actions, natural user-facing keywords, and a clear 'what' component. A user or Claude selecting from many skills would struggle to understand the skill's purpose or when to prefer it over alternatives.

Suggestions

Add a clear 'what' statement describing the concrete action, e.g., 'Executes multiple tasks in parallel using concurrent subagents' or 'Runs independent subtasks simultaneously to speed up workflows'.

Include natural trigger terms users would actually say, such as 'parallel', 'at the same time', 'concurrently', 'multiple tasks', 'batch', 'speed up'.

Provide explicit examples of when to use it, e.g., 'Use when the user asks to do multiple things at once, run tasks in parallel, or when subtasks have no dependencies on each other'.

Dimension	Reasoning	Score
Specificity	The description does not list any concrete actions or capabilities. It describes a condition for use but never says what the skill actually does — no verbs like 'runs', 'executes', 'parallelizes', etc.	1 / 3
Completeness	The 'when' is partially addressed ('Use when facing 2+ independent tasks...'), but the 'what' — what the skill actually does — is entirely missing. Without knowing what it does, the description is fundamentally incomplete.	1 / 3
Trigger Term Quality	There are no natural keywords a user would say. Terms like 'independent tasks', 'shared state', and 'sequential dependencies' are abstract/technical jargon, not phrases users naturally use in requests.	1 / 3
Distinctiveness Conflict Risk	The concept of parallel/independent task execution is somewhat distinctive, but without naming the mechanism (e.g., parallel tool calls, subagents, concurrent execution), it could overlap with any multi-step or task-management skill.	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 with clear workflow steps and good concrete examples. Its main weakness is verbosity — multiple sections repeat the same concepts (when to use vs when not to use, benefits restating what's already clear, real example largely duplicating the pattern). Trimming redundancy and potentially splitting the detailed example into a separate file would improve token efficiency.

Suggestions

Consolidate 'When to Use' and 'When NOT to Use' into a single decision section, and remove the 'Key Benefits' section since the benefits are self-evident from the pattern description.

Consider moving the 'Real Example from Session' and 'Real-World Impact' sections into a separate EXAMPLES.md file referenced from the main skill, reducing the main file's token footprint.

Dimension	Reasoning	Score
Conciseness	The skill has significant redundancy — 'When NOT to Use' repeats 'Don't use when', 'Key Benefits' restates what's already obvious, and the 'Real Example from Session' section largely duplicates the pattern description. The dot graph is a nice idea but adds tokens for marginal value. Several sections could be consolidated or removed.	2 / 3
Actionability	Provides concrete agent prompt examples, specific dispatch syntax, clear common mistakes with do/don't pairs, and a real worked example with actual test file names and outcomes. The guidance is specific enough to be directly applied.	3 / 3
Workflow Clarity	The 4-step workflow (Identify → Create → Dispatch → Review/Integrate) is clearly sequenced with explicit validation checkpoints in the Verification section (review summaries, check conflicts, run full suite, spot check). The feedback loop for integration is well-defined.	3 / 3
Progressive Disclosure	The content is a monolithic single file with no references to supporting documents. While the sections are well-organized with clear headers, the real example, common mistakes, and agent prompt structure sections could be split into referenced files to keep the main skill leaner. For a skill of this length (~150 lines), some splitting would be appropriate.	2 / 3
	Total	10 / 12 Passed

Validation

100%

Warnings & errors only

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.

Repository: obra/superpowers
Commit: f2cbfbe

Reviewed: 17 days ago

Table of Contents

Discovery Implementation Validation

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.