parallel-task
Only to be triggered by explicit /parallel-task commands.
48
49%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/parallel-task/SKILL.mdQuality
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 extremely minimal and fails to communicate what the skill does. It only specifies a trigger mechanism ('/parallel-task' command) without describing any capabilities, actions, or use cases. While the explicit command trigger reduces some conflict risk, the description is essentially non-functional for helping Claude understand when and why to select this skill.
Suggestions
Add a clear 'what' clause describing the specific actions this skill performs (e.g., 'Breaks down complex tasks into parallel subtasks and coordinates their execution').
Add a 'Use when...' clause with explicit trigger guidance beyond just the slash command, describing the scenarios or user needs that warrant this skill (e.g., 'Use when the user issues /parallel-task or asks to run multiple independent tasks concurrently').
Include natural language trigger terms that describe the domain, such as 'parallel execution', 'concurrent tasks', 'subtask coordination', so Claude can better match user intent.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. It does not describe what the skill does — only how it should be triggered. 'parallel-task' hints at a domain but no specific capabilities are listed. | 1 / 3 |
Completeness | The 'what does this do' is entirely missing — there is no explanation of the skill's purpose or capabilities. The 'when' is partially addressed (only on explicit command), but without knowing what the skill does, completeness is very weak. | 1 / 3 |
Trigger Term Quality | It includes the explicit trigger term '/parallel-task' which is a specific command a user would type, but it provides no natural language keywords or variations that a user might say when needing this functionality. | 2 / 3 |
Distinctiveness Conflict Risk | The explicit slash-command trigger '/parallel-task' reduces conflict risk since it requires an exact command, but the lack of any description of what the skill actually does makes it hard to fully assess distinctiveness from other task-management or parallelism 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 strong actionability and clear workflow sequencing including validation checkpoints and error recovery loops. Its main weakness is the lengthy inline task prompt template which adds bulk and could be more concise or externalized. The skill effectively communicates a complex multi-agent coordination process with concrete steps and templates.
Suggestions
Consider extracting the large Task Prompt Template into a separate referenced file to improve progressive disclosure and reduce the main skill's token footprint.
Tighten the task prompt template by removing generic advice like 'Be careful with paths' and consolidating redundant instructions (e.g., the verification evidence requirement is stated in both the instructions and the post-template note).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some unnecessary verbosity. The task prompt template is quite long and could be tightened. Some instructions like 'Be careful with paths' are vague filler. However, it mostly avoids explaining concepts Claude already knows. | 2 / 3 |
Actionability | The skill provides highly concrete, actionable guidance: a specific task prompt template, clear parsing instructions for plan files, explicit step-by-step workflows, example usage commands, and an execution summary template. The instructions are specific enough to be directly executable. | 3 / 3 |
Workflow Clarity | The multi-step process is clearly sequenced (parse → read → launch → validate → repeat) with explicit validation checkpoints at Step 4, feedback loops for retrying failed tasks, and clear dependency-based wave execution. The TDD RED→GREEN validation cycle provides a concrete verification mechanism. | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear sections and headers, but the task prompt template is a large inline block that could potentially be a separate reference file. For a standalone skill with no bundle files, the organization is decent but the monolithic prompt template makes it feel heavy. The execution summary template at the end is appropriately placed. | 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
- am-will/codex-skills
- Commit
d3983b1
- 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.