parallel-task-spark

Only to be triggered by explicit /parallel-task-spark commands.

Quality

49%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/parallel-task-spark/SKILL.md

Quality

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 critically deficient because it provides no information about what the skill actually does—only how it is triggered. Without any explanation of capabilities, Claude cannot make an informed decision about when this skill is appropriate beyond recognizing the exact slash command. The description fails on specificity and completeness.

Suggestions

Add a clear explanation of what the skill does, e.g., 'Orchestrates parallel task execution by spawning concurrent sub-agents for independent workstreams.'

Include a 'Use when...' clause with natural language triggers describing scenarios, e.g., 'Use when the user needs to run multiple independent tasks simultaneously, mentions parallel execution, or wants to split work across agents.'

Add domain-specific keywords users might naturally say, such as 'parallel tasks', 'concurrent execution', 'multi-agent', 'split work', etc.

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 not explained.	1 / 3
Completeness	The 'what does this do' is entirely missing—there is no explanation of the skill's functionality. The 'when' is partially addressed (only on explicit command), but without knowing what it does, the description is fundamentally incomplete.	1 / 3
Trigger Term Quality	It includes one explicit trigger term ('/parallel-task-spark'), which is a specific command a user might type. However, it lacks any natural language keywords describing the domain or task, and no common variations are provided.	2 / 3
Distinctiveness Conflict Risk	The explicit command trigger '/parallel-task-spark' reduces accidental activation, providing some distinctiveness. However, without describing what the skill actually does, it's impossible to fully assess conflict risk with other skills, and the name alone is somewhat opaque.	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 workflow clarity and actionability—it clearly defines the parse-launch-validate-repeat loop with explicit validation checkpoints and dependency management. The main weaknesses are moderate verbosity (some redundant instructions and a lengthy inline template) and the lack of content splitting for the large task prompt template. Overall it's a solid, functional skill that could benefit from tightening.

Suggestions

Extract the Task Prompt Template into a separate file (e.g., TASK_PROMPT_TEMPLATE.md) and reference it from the main skill to improve conciseness and progressive disclosure.

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 at the end adds bulk but is useful as a concrete output format.	2 / 3
Actionability	The skill provides highly concrete, actionable guidance: a specific task prompt template, exact steps for parsing plans, clear subagent launch instructions, example usage commands, and a structured execution summary template. The workflow is copy-paste ready for an orchestrator agent.	3 / 3
Workflow Clarity	The multi-step process is clearly sequenced (Steps 1-5) with explicit validation checkpoints (Step 4 validates outputs, requires RED->GREEN evidence or non-testable verification), feedback loops (retry or escalate on failure), and wave-based execution with dependency checking before each wave.	3 / 3
Progressive Disclosure	The content is well-structured with clear sections and headers, but the task prompt template is very long and inline. This template could be referenced from a separate file to keep the main skill leaner. For a skill of this complexity (~120 lines), some content splitting would improve navigability.	2 / 3
	Total	10 / 12 Passed

Validation

100%

Warnings & errors only

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: ca2c3b3

Reviewed: 10 days ago

Table of Contents

Discovery Implementation Validation

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.