Only to be triggered by explicit /parallel-task commands.
60
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
22%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 is severely lacking as it only specifies a trigger condition without explaining what the skill actually does. Users and Claude cannot make informed decisions about when to use this skill because its capabilities are completely undefined. The description fails the fundamental purpose of helping Claude choose the right skill from a collection.
Suggestions
Add concrete actions describing what the skill does (e.g., 'Executes multiple tasks concurrently, manages parallel workflows, coordinates simultaneous operations').
Include natural language trigger terms beyond the slash command (e.g., 'parallel execution', 'run simultaneously', 'concurrent tasks', 'background processing').
Restructure to follow the pattern: '[What it does]. Use when [explicit triggers]' to ensure both components are clearly addressed.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. It only states when it should be triggered, not what it actually does. 'parallel-task' is mentioned but no capabilities are described. | 1 / 3 |
Completeness | The description only addresses 'when' (explicit /parallel-task commands) but completely fails to answer 'what does this do'. There is no explanation of the skill's purpose or capabilities. | 1 / 3 |
Trigger Term Quality | Contains one explicit trigger term '/parallel-task commands' which is specific, but lacks any natural language variations users might say (e.g., 'run in parallel', 'concurrent tasks', 'background tasks'). | 2 / 3 |
Distinctiveness Conflict Risk | The explicit command trigger '/parallel-task' provides some distinctiveness and reduces accidental triggering, but without knowing what the skill does, it's unclear if it might conflict with other task-related skills. | 2 / 3 |
Total | 6 / 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 well-structured orchestration skill with clear workflows, explicit validation steps, and actionable templates. The multi-step process is clearly sequenced with appropriate checkpoints for parallel task management. Minor improvements could be made in conciseness and potentially splitting out templates for better progressive disclosure.
Suggestions
Tighten the introductory paragraph - remove redundant phrases like 'Your role is to ensure' which restates what's already clear from the process steps
Consider extracting the Task Prompt Template and Execution Summary Template to separate referenced files if this skill grows or is frequently modified
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some redundant phrasing (e.g., 'Your role is to ensure that subagents are launched in the correct order (in waves), and that they complete their tasks correctly') and could be tightened in places. The templates are appropriately detailed without excessive explanation. | 2 / 3 |
Actionability | Provides concrete, executable guidance with specific steps, a detailed task prompt template, example usage commands, and an execution summary template. Claude knows exactly what to do at each stage. | 3 / 3 |
Workflow Clarity | Clear 5-step sequential process with explicit validation checkpoints (Step 4), feedback loops for retrying failed tasks, and explicit instructions to verify task completion before proceeding. The workflow handles parallel execution with dependency tracking. | 3 / 3 |
Progressive Disclosure | Content is well-structured with clear sections and templates, but everything is in a single file. For a skill of this complexity (~120 lines), the task prompt template and execution summary template could potentially be referenced separately, though the current organization is functional. | 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.
Table of Contents
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.