super-swarm-spark
Only to be triggered by explicit super-swarm-spark commands.
43
42%
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/super-swarm-spark/SKILL.mdQuality
Discovery
7%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 weak across all dimensions. It provides no information about what the skill does, lists no concrete actions or capabilities, and relies entirely on an obscure command name as its only trigger. Without knowing what the skill accomplishes, Claude cannot make an informed decision about when to select it.
Suggestions
Add a clear 'what' clause describing the specific actions and capabilities this skill provides (e.g., 'Orchestrates multi-agent task decomposition and parallel execution').
Add a 'Use when...' clause with explicit trigger scenarios and natural language terms users might say when they need this skill.
Replace or supplement the jargon term 'super-swarm-spark' with plain-language descriptions of the use cases so Claude can match user intent even when the exact command name isn't used.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. It does not describe what the skill does—only that it should be triggered by a specific command. 'Super-swarm-spark commands' is abstract and undefined. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' entirely and only vaguely addresses 'when' by saying it should be triggered by explicit commands, without explaining what those commands are or what the skill accomplishes. | 1 / 3 |
Trigger Term Quality | The only keyword is 'super-swarm-spark commands,' which is technical jargon unlikely to be naturally used by a user. There are no natural language trigger terms that a user would say. | 1 / 3 |
Distinctiveness Conflict Risk | The unusual term 'super-swarm-spark' is distinctive enough that it's unlikely to conflict with other skills, but the lack of any capability description means Claude cannot meaningfully distinguish when to use it beyond pattern-matching on that specific phrase. | 2 / 3 |
Total | 5 / 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 feedback loops. Its main weaknesses are internal inconsistencies (12 vs 15 agent count mentioned in different places) and some verbosity/redundancy that could be tightened. The monolithic structure is acceptable but could benefit from splitting templates into separate files.
Suggestions
Resolve the inconsistency between '12' and '15' max concurrent agents—the title says 12, the intro paragraph says 15, and the scheduling policy says 12.
Consider extracting the Task Prompt Template and Execution Summary Template into separate referenced files to improve progressive disclosure and reduce the main file's length.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly long but most content is functional (templates, steps, policies). However, there's some redundancy—the max concurrency is stated as both 12 and 15 in different places, and some instructions are repeated across sections (e.g., plan file updating is mentioned in multiple places). The title says '12-Agent Pool' but the intro says 'up to 15'. Some tightening is possible. | 2 / 3 |
Actionability | The skill provides highly concrete, actionable guidance: a complete task prompt template with exact fields, specific scheduling rules, explicit step-by-step processes, example invocation commands, and a detailed execution summary template. Claude knows exactly what to do at each stage. | 3 / 3 |
Workflow Clarity | The workflow is clearly sequenced across 6 steps with explicit validation checkpoints (Step 5 validates every completion, Step 6 performs integration fixes with a test-until-green feedback loop). Error handling is addressed, and the completion bar provides clear exit criteria. The rolling pool scheduling policy is unambiguous. | 3 / 3 |
Progressive Disclosure | The content is entirely monolithic in a single file with no references to supporting documents. For a skill of this complexity (~200 lines), the task prompt template and execution summary template could reasonably be split into separate referenced files. However, the internal structure with clear headers is decent. | 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.