CtrlK
BlogDocsLog inGet started
Tessl Logo

aiox-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.

67

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

The canonical home for this skill is wave-execute in SynkraAI/aiox-core

SKILL.md
Quality
Evals
Security

Quality

Content

81%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.

A well-structured, command-heavy skill body with a clearly sequenced five-stage workflow, explicit validation and blocking conditions, and a useful checklist. Its main weaknesses are minor redundancy and a few placeholder gaps rather than structural problems.

Suggestions

Replace the '… run skill for phase …' ellipsis in the per-story CLI block with the concrete aiox sdc phase commands so the guidance is fully copy-paste executable.

Trim redundancy between the 'Not in scope' note and the 'Strip checklist' so each token earns its place and conciseness moves toward 5.

Consider moving the full CLI command catalog into a references/ file referenced one level deep, keeping SKILL.md as a tighter overview to lift progressive_disclosure.

DimensionReasoningScore

Conciseness

The body is lean and command-driven with minimal concept explanation, but carries minor redundancy (the 'Not in scope' list and 'Strip checklist' partly restate prior points), so it is efficient with a little trimmable fat rather than perfectly lean.

4 / 5

Actionability

It provides concrete, mostly copy-paste-ready CLI commands and a spawn_subagent prompt template, but placeholders like '… run skill for phase …' and unreplaced {wave-id}/{story-id} tokens leave minor gaps versus fully executable 5.

4 / 5

Workflow Clarity

The five EXECUTE stages are clearly sequenced with explicit validation checkpoints (preflight budget/intent scan, halt on quality_gate, fan-in overlap re-check, never silent overwrite), error-handling rules for failed dependents, and a closing checklist — satisfying the top anchor including for this batch operation.

5 / 5

Progressive Disclosure

Content is well-organized into clear sections with no nested references and no bundle files present, but at ~130 lines the inline CLI command catalog could arguably live in a separate reference file, leaving it just below the ideal split of 5.

4 / 5

Total

17

/

20

Passed

Description

83%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.

A strong description that concretely states several executable actions and pairs them with an explicit 'Use when' trigger clause, cleanly answering both what and when. It is slightly held back by jargon-laden triggers and minor overlap with the full-sdc skill it depends on.

DimensionReasoningScore

Specificity

Lists several concrete actions — 'plan story DAG + file-ownership batches', 'dispatch full-sdc per story', 'fan-in check', 'hand off merge to @devops' — with only minor coverage gaps, fitting the 'lists several specific actions' anchor rather than the fully comprehensive 5.

4 / 5

Completeness

It explicitly answers both what ('EXECUTE a lean wave — plan…dispatch…fan-in…hand off merge') and when ('Use when: wave-execute, run wave, epic wave, parallel stories SDC') with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

The 'Use when: wave-execute, run wave, epic wave, parallel stories SDC' clause gives good natural-phrase coverage a user would say, though 'SDC' is jargon and a few common synonyms are missing, keeping it just below the comprehensive 5.

4 / 5

Distinctiveness Conflict Risk

The wave-orchestration niche is mostly distinct with clear triggers, but 'depends on skill full-sdc' and the 'parallel stories SDC' trigger create minor overlap risk with the closely related full-sdc skill, so it sits at 4 rather than 5.

4 / 5

Total

17

/

20

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

frontmatter_unknown_keys

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

Warning

Total

14

/

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.