CtrlK
BlogDocsLog inGet started
Tessl Logo

dispatching-parallel-agents

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

48

Quality

50%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/dispatching-parallel-agents/SKILL.md

The canonical home for this skill is dispatching-parallel-agents in obra/superpowers

SKILL.md
Quality
Evals
Security

Quality

Content

60%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is well-structured and actionable with a clear validated workflow, but it is padded by repeated guidance and a duplicated real-world example. Trimming the redundant sections would meaningfully improve token efficiency.

Suggestions

Merge "Real Example from Session" and "Real-World Impact" into one section; they describe the identical scenario.

Consolidate "When to Use", "When NOT to Use", and "Common Mistakes" so the do/don't guidance is stated once.

Fold the "Verification" section into Pattern step 4 (Review and Integrate) to remove the overlap.

DimensionReasoningScore

Conciseness

Several sections restate the same guidance (When to Use / When NOT to Use / Common Mistakes) and the same 6-failures-3-files story is told twice (Real Example and Real-World Impact), plus Review-and-Integrate overlaps the Verification section, making it noticeably padded.

2 / 5

Actionability

It provides a concrete Task() dispatch example and a copy-pasteable agent-prompt template with good/bad contrasts, giving mostly executable guidance with only minor gaps around environment-specific syntax.

4 / 5

Workflow Clarity

The 4-step Pattern is clearly sequenced and the batch operation includes validation checkpoints (check for conflicts, run full suite, spot check), though an explicit fix-and-retry feedback loop is not spelled out.

4 / 5

Progressive Disclosure

No bundle files exist and the skill is organized into clear, navigable section headers with no nested references; the single-file layout is appropriate for a pattern skill, with only minor organization gaps from redundancy.

4 / 5

Total

14

/

20

Passed

Description

40%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is a clear trigger clause but omits the skill's actual capability, leaving the 'what' unspecified. Trigger terms are relevant but somewhat technical and lack common synonyms.

Suggestions

Lead with what the skill does, e.g. "Dispatches specialized parallel agents for independent tasks...", then keep the "Use when" clause.

Add natural synonyms users would say, such as "parallel", "concurrent", or "run multiple tasks at once".

Avoid jargon-only triggers like "sequential dependencies" in favor of plain-language equivalents.

DimensionReasoningScore

Specificity

The description names the trigger domain ("2+ independent tasks", "without shared state") but names no concrete actions the skill performs, so it is above the entirely-vague anchor yet below naming concrete capabilities.

2 / 5

Completeness

It has an explicit "Use when" trigger but never states what the skill does (dispatch parallel agents), matching the anchor where only the 'when' is present without a 'what'.

2 / 5

Trigger Term Quality

It includes relevant terms like "independent tasks" and "shared state", but "sequential dependencies" leans technical and common natural synonyms (e.g. parallel, concurrent, multitask) are missing.

3 / 5

Distinctiveness Conflict Risk

The no-shared-state / independent-task trigger carves a fairly distinct parallel-dispatch niche with only minor overlap risk against related coordination skills.

4 / 5

Total

11

/

20

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
lucianghinda/superpowers-ruby
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.