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 ./.opencode/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 - it only provides a vague trigger condition using technical jargon. The absence of concrete actions, natural user keywords, and a clear 'what' component makes it nearly unusable for skill selection among multiple options.
Suggestions
Add concrete actions describing what this skill does (e.g., 'Executes multiple independent tasks in parallel to improve efficiency' or 'Coordinates concurrent work streams')
Replace technical jargon with natural user terms - include keywords like 'parallel', 'multiple tasks at once', 'batch processing', 'concurrent', or 'simultaneously'
Restructure to lead with capabilities, then follow with 'Use when...' clause containing user-friendly trigger terms
| 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' (partially) but completely omits 'what' - there's no explanation of what this skill actually does or what actions it performs. | 1 / 3 |
Trigger Term Quality | No natural user keywords are present. Users wouldn't naturally say 'shared state' or 'sequential dependencies' - these are technical jargon. Missing terms like 'parallel', 'multiple tasks', 'batch', or 'concurrent'. | 1 / 3 |
Distinctiveness Conflict Risk | The concept of '2+ independent tasks' provides some distinctiveness, but without specifying what kind of tasks or what the skill does, it could overlap with any multi-step workflow 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 strong skill with excellent actionability and workflow clarity. The concrete examples, agent prompt templates, and verification steps make it immediately usable. The main weakness is some redundancy between sections (real example appears twice with similar content) and the content could be slightly more concise by consolidating related sections.
Suggestions
Consolidate 'Real Example from Session' and 'Real-World Impact' sections - they contain overlapping information about the same debugging session
Consider merging 'When to Use' and 'When NOT to Use' into a single decision section to reduce repetition of concepts
| 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 'Verification' section provides a checklist for post-agent integration, and the pattern includes feedback loops for reviewing and integrating changes. | 3 / 3 |
Progressive Disclosure | Content is well-structured with clear sections, but it's somewhat monolithic - the detailed examples and common mistakes could potentially be split into separate reference files. However, for a skill of this complexity, inline content is reasonable. | 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.
- Repository
- projectbluefin/dakota
- Commit
f062bf8
- 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.