parallel-task-spark
Only to be triggered by explicit /parallel-task-spark commands.
Install with Tessl CLI
npx tessl i github:am-will/codex-skills --skill parallel-task-spark60
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 deficient as it only specifies a trigger command without explaining any capabilities or purpose. Claude cannot make an informed decision about when to use this skill beyond recognizing the exact command string. The description fails the fundamental requirement of helping Claude understand what the skill does.
Suggestions
Add concrete actions describing what the skill does (e.g., 'Executes multiple tasks in parallel, coordinates concurrent operations, manages task distribution')
Include natural language trigger terms users might say (e.g., 'parallel processing', 'run simultaneously', 'concurrent tasks', 'multi-task')
Add a 'Use when...' clause that covers both the explicit command AND natural language scenarios where parallel task execution would be appropriate
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. It only describes a trigger mechanism without explaining what the skill actually does. | 1 / 3 |
Completeness | Completely missing the 'what does this do' component. Only addresses 'when' (explicit command trigger) without any explanation of capabilities or purpose. | 1 / 3 |
Trigger Term Quality | Contains one specific trigger term '/parallel-task-spark' which is explicit, but it's a technical command rather than natural language users would say. No natural keywords like 'parallel', 'tasks', 'concurrent', etc. | 2 / 3 |
Distinctiveness Conflict Risk | The explicit command trigger '/parallel-task-spark' provides some distinctiveness, but without knowing what the skill does, it's impossible to assess true conflict risk with other 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. The multi-step process with validation checkpoints and error handling is well-defined. Minor improvements could be made in conciseness by reducing redundant emphasis and potentially extracting templates to separate files.
Suggestions
Remove redundant emphasis on 'sparky' role (mentioned 4+ times) - state once clearly in Step 3
Consider extracting the Task Prompt Template and Execution Summary Template to separate referenced files to improve progressive disclosure
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some redundancy (e.g., repeating 'sparky' role requirements multiple times, verbose template sections). The instruction to 'ALWAYS mark completed tasks' is emphasized with caps which adds noise rather than clarity. | 2 / 3 |
Actionability | Provides concrete, executable guidance with specific field names (agent_type: sparky), exact template structure, clear parsing instructions (e.g., 'depends_on' format), and example usage commands. The task prompt template is copy-paste ready. | 3 / 3 |
Workflow Clarity | Clear 5-step sequential process with explicit validation checkpoints (Step 4), feedback loops for retries/escalation, and wave-based execution pattern. Includes error handling section and explicit 'ensure committed before moving on' validation gates. | 3 / 3 |
Progressive Disclosure | Content is well-structured with clear sections, but the skill is somewhat monolithic. The lengthy task prompt template and execution summary template could potentially be referenced externally. However, for a skill of this complexity, inline templates are 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.
- 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.