parallel-task-spark
Only to be triggered by explicit /parallel-task-spark commands.
49
53%
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-spark/SKILL.mdQuality
Discovery
29%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 actually does. While the explicit slash command trigger makes it distinctive and unlikely to conflict with other skills, the complete absence of capability descriptions, use cases, or natural language trigger terms means Claude cannot intelligently select this skill based on user intent. It functions purely as a command-gated skill with no discoverability.
Suggestions
Add a clear 'what' clause describing the concrete actions this skill performs (e.g., 'Orchestrates parallel task execution by splitting work into concurrent subtasks and aggregating results').
Add a 'Use when...' clause with natural language trigger terms so Claude can understand the skill's purpose even if the slash command isn't used (e.g., 'Use when the user wants to run multiple tasks in parallel, split work across threads, or speed up batch processing').
Include domain-specific keywords that users might naturally say, such as 'parallel processing', 'concurrent tasks', 'batch execution', or whatever the skill's actual domain is.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. It does not describe what the skill does—only that it is triggered by a specific command. 'parallel-task-spark' is a name, not a capability description. | 1 / 3 |
Completeness | The description answers neither 'what does this do' nor 'when should Claude use it' in any meaningful way. It only states the activation mechanism (a slash command) without explaining the skill's purpose or use cases. | 1 / 3 |
Trigger Term Quality | It includes one explicit trigger term ('/parallel-task-spark'), which is a slash command rather than a natural language keyword. Users who know the command will trigger it, but there are no natural language terms describing what the skill does or when a user might need it. | 2 / 3 |
Distinctiveness Conflict Risk | The explicit slash command trigger '/parallel-task-spark' is highly distinctive and unlikely to conflict with other skills, since it requires an exact command match rather than natural language interpretation. | 3 / 3 |
Total | 7 / 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. Its main weakness is moderate verbosity—the embedded task prompt template is lengthy and some instructions are repeated. The skill would benefit from extracting templates into separate files and trimming redundant directives.
Suggestions
Extract the Task Prompt Template and Execution Summary Template into separate referenced files (e.g., TASK_PROMPT.md, SUMMARY_TEMPLATE.md) to reduce the main skill's token footprint.
Remove redundant reminders about agent_type: sparky (mentioned 3 times) and consolidate into a single constraint statement.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is moderately efficient but includes some redundancy—e.g., repeating 'agent_type: sparky' constraints multiple times, and the task prompt template is quite verbose with instructions Claude could infer. The execution summary template adds bulk but is useful as a concrete output format. | 2 / 3 |
Actionability | The skill provides highly concrete, step-by-step guidance with a complete task prompt template, specific parsing instructions (e.g., '### T1:' format, 'depends_on' extraction), exact commit/push rules, and example invocations. The workflow is copy-paste actionable for an orchestrator agent. | 3 / 3 |
Workflow Clarity | The multi-step process is clearly sequenced (parse → read → launch → validate → repeat) with explicit validation checkpoints (Step 4 inspects outputs, checks commits, handles retries), feedback loops (retry or escalate on failure), and wave-based dependency management. The TDD RED→GREEN cycle provides built-in verification. | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear sections and headers, but it's a monolithic file with no references to supporting documents. The lengthy task prompt template and execution summary template could be split into separate referenced files to reduce the main skill's size. However, with no bundle files provided, this is somewhat expected. | 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.