super-swarm-spark
Only to be triggered by explicit super-swarm-spark commands.
Install with Tessl CLI
npx tessl i github:am-will/codex-skills --skill super-swarm-spark62
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
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 severely deficient as it provides no information about what the skill actually does. While it has a distinctive trigger term that prevents conflicts, the complete absence of capability information makes it impossible for Claude to understand when this skill would be useful beyond recognizing the exact command phrase.
Suggestions
Add concrete actions describing what this skill does (e.g., 'Orchestrates distributed task processing across multiple agents' or whatever the actual capability is)
Expand the 'Use when...' clause to include natural language variations users might say when they need this functionality, not just the exact command
Describe the purpose and outcomes of using this skill so Claude can intelligently select it even when users don't use the exact trigger phrase
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. It only states when to trigger but provides zero information about what the skill actually does. | 1 / 3 |
Completeness | The description completely fails to answer 'what does this do' - it only addresses 'when' (explicit commands) without any explanation of capabilities or purpose. | 1 / 3 |
Trigger Term Quality | Contains one specific trigger term 'super-swarm-spark' which is distinctive, but it's technical jargon rather than natural language users would say, and there are no variations or related terms. | 2 / 3 |
Distinctiveness Conflict Risk | The unique trigger term 'super-swarm-spark' is highly distinctive and unlikely to conflict with other skills due to its specificity as an explicit command. | 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. The main weaknesses are moderate verbosity with repeated information and a monolithic structure that could benefit from splitting templates into separate files. The skill effectively communicates the rolling pool concept and provides concrete implementation guidance.
Suggestions
Remove redundant mentions of the 12-agent limit (appears in title, Step 4, and Scheduling Policy section)
Consider extracting the Task Prompt Template and Execution Summary Template into separate referenced files to improve progressive disclosure
Consolidate the scheduling policy information into Step 4 rather than having a separate section that repeats the same constraints
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but contains some redundancy (e.g., repeating the 12-agent limit multiple times, verbose template sections). The scheduling policy section restates information already covered in Step 4. | 2 / 3 |
Actionability | Provides concrete, executable guidance with specific templates, exact parameters (agent_type: sparky), clear step-by-step processes, and example usage commands. The task prompt template is copy-paste ready. | 3 / 3 |
Workflow Clarity | Clear 6-step sequence with explicit validation at Step 5, integration pass at Step 6, and feedback loops (retry/escalate on failure, re-run tests until green). States are explicitly defined (pending, running, completed, failed). | 3 / 3 |
Progressive Disclosure | Content is well-structured with clear sections, but everything is in a single monolithic file. The lengthy task prompt template and execution summary template could be split into separate reference files for cleaner navigation. | 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.