CtrlK
BlogDocsLog inGet started
Tessl Logo

super-swarm-spark

Only to be triggered by explicit super-swarm-spark commands.

44

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a strong, actionable orchestration guide with concrete templates, explicit validation feedback loops, and clear sectioning. Its main weakness is an internal inconsistency on the maximum agent count (12 vs 15) across the header, goals, and scheduling sections.

DimensionReasoningScore

Conciseness

The body is well-organized and assumes Claude's competence without explaining known concepts, but it carries an internal contradiction (header/goals say 12 vs 15 agents) and the prompt template could be tightened, fitting the level-2 anchor of mostly efficient with some unnecessary/loose material.

2 / 3

Actionability

It provides a copy-paste task prompt template, exact agent_type, scheduling states, example commands, error-handling rules, and a summary template, matching the level-3 anchor of fully executable, specific guidance.

3 / 3

Workflow Clarity

Six clearly sequenced steps include explicit validation checkpoints (Step 5 validates every completion; Step 6 re-runs tests until green) and error-recovery loops, matching the level-3 anchor of clear sequence with validation feedback.

3 / 3

Progressive Disclosure

With no bundle files present, the single-file skill is organized into clearly labeled sections (Process, Scheduling Policy, Error Handling, templates), meeting the level-3 standard for simple skills needing no external references.

3 / 3

Total

11

/

12

Passed

Description

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.

The description is critically underspecified: it conveys only a trigger condition and omits any statement of what the skill does, leaving a user unable to recognize when it applies beyond a typed command. It reads as a guard clause rather than a capability description.

Suggestions

Add a concrete statement of what the skill does, e.g. 'Executes a development plan by delegating tasks in parallel to a rolling pool of up to 12 Sparky subagents.'

Replace the custom-name-only trigger with natural user phrasing, e.g. 'Use when the user asks to implement or execute a plan file with parallel subagents.'

Use third-person capability voice ('Parses plan files and delegates...') instead of a passive trigger-only sentence.

DimensionReasoningScore

Specificity

The description only states 'Only to be triggered by explicit super-swarm-spark commands' — it names no concrete actions or capabilities, matching the level-1 anchor of vague/abstract language with no actions.

1 / 3

Completeness

It states a trigger ('when') but entirely omits what the skill does, so the 'what' is missing per the level-1 anchor for missing what or weak when.

1 / 3

Trigger Term Quality

'super-swarm-spark' is a custom skill name rather than a natural term a user would say unprompted, fitting the level-1 anchor of technical jargon with no natural keywords.

1 / 3

Distinctiveness Conflict Risk

The restriction to 'explicit super-swarm-spark commands' narrows accidental triggering, but the otherwise empty description leaves its function indistinct, fitting the level-2 anchor of somewhat specific but potentially overlapping.

2 / 3

Total

5

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
am-will/codex-skills
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.