CtrlK
BlogDocsLog inGet started
Tessl Logo

wave-execute

EXECUTE a lean wave — plan story DAG + file-ownership batches via CLI, dispatch full-sdc per story, fan-in check, hand off merge to @devops. Use when: wave-execute, run wave, epic wave, parallel stories SDC.

72

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

88%Weight 40%Scale 1-5

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

The body is highly actionable and well-sequenced with strong validation checkpoints for a batch/parallel operation, assuming Claude's competence throughout. Slight repetition between early sections is the only real weakness.

DimensionReasoningScore

Conciseness

The body is lean and assumes competence (no padding explaining what a wave is), but CLI commands are repeated across the Invocation and CLI sections, leaving minor instances that could be trimmed.

4 / 5

Actionability

Provides copy-paste-ready commands (aiox wave plan/advance/next/mark/report, aiox sdc plan/next/verify), a concrete spawn_subagent prompt, and a YAML handoff template covering the common cases.

5 / 5

Workflow Clarity

Five clearly sequenced EXECUTE stages with explicit validation checkpoints (preflight rejection, --dry-run stop, SDC completed/HALT wait, fan-in overlap re-check, conflict surfacing), plus blocking conditions and a strip checklist.

5 / 5

Progressive Disclosure

Well-organized into clear sections with no nested or buried references and no bundle files that should have been split out; minor overlap between the Invocation and CLI sections keeps it from a perfect mark.

4 / 5

Total

18

/

20

Passed

Description

92%Weight 40%Scale 1-5

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 specific, complete, and distinct, with explicit trigger guidance and a clear what/when structure. Trigger terms are slightly jargon-weighted, keeping it just short of a perfect mark on that dimension.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'plan story DAG + file-ownership batches via CLI, dispatch full-sdc per story, fan-in check, hand off merge to @devops' — giving comprehensive coverage of what the skill does.

5 / 5

Completeness

Explicitly answers both 'what' (plan/dispatch/fan-in/hand-off) and 'when' via a concrete 'Use when:' trigger clause with multiple trigger phrases.

5 / 5

Trigger Term Quality

The 'Use when: wave-execute, run wave, epic wave, parallel stories SDC' clause offers good natural-phrase coverage, but several terms are jargon-heavy and a few common synonyms are missing.

4 / 5

Distinctiveness Conflict Risk

A clear niche (lean story-wave execution with full-sdc children and @devops merge) with distinct triggers; minimal overlap risk with other skills.

5 / 5

Total

19

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
SynkraAI/aiox-core
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.