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.

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

77%

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

A dense, actionable workflow doc with concrete CLI commands and a well-sequenced multi-stage process including validation checkpoints. It loses points on conciseness (duplicated invocation, meta checklist) and on progressive disclosure (a monolithic file with no reference split).

Suggestions

Remove the duplicated `aiox wave plan` example from the Invocation section (keep it only in CLI) and drop the self-referential "Strip checklist", which does not guide execution.

Move the full CLI command catalog and/or partition rules into a REFERENCES.md or CLI.md and keep SKILL.md as a lean overview with clearly signaled one-level-deep links.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean and assumes competence (no concept explanations), but the `aiox wave plan ... --save` invocation is duplicated across the Invocation and CLI sections and the meta "Strip checklist" does not earn its place, so not every token is load-bearing as the 3-anchor requires.	2 / 3
Actionability	Provides fully executable CLI commands (`aiox wave plan`, `aiox wave mark ... --status`, `aiox sdc verify ... --mark`), a concrete spawn_subagent prompt, and a copy-paste handoff YAML block — not pseudocode, matching the 3-anchor.	3 / 3
Workflow Clarity	Five sequenced EXECUTE stages with explicit validation checkpoints (preflight intent/budget scan, `--dry-run` stop, fan-in overlap re-check), blocking conditions, and a failure cascade ("do not fake green") — a batch operation with proper feedback loops, so it is not capped at 2.	3 / 3
Progressive Disclosure	No bundle files exist and the skill is a single ~130-line monolith with no one-level-deep references; it is well-sectioned but the CLI command catalog and partition rules are inline rather than split into a reference file, fitting the 2-anchor better than the reference-structured 3-anchor.	2 / 3
	Total	10 / 12 Passed

Description

85%

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 concise, action-oriented description that names several concrete operations and includes an explicit Use-when trigger clause. Its main weakness is trigger-term quality: the keywords are domain-jargon-heavy and lack common natural variations.

Suggestions

Add everyday phrasings a user might actually say (e.g., "run several stories in parallel", "execute a batch of stories") alongside the jargon triggers like "SDC".

Spell out or pair the "SDC" abbreviation with a plain term so the trigger is recognizable to users unfamiliar with the internal acronym.

Dimension	Reasoning	Score
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" — matching the multi-action anchor rather than the single-domain anchor at 2.	3 / 3
Completeness	Explicitly states what it does (execute a wave: plan, dispatch, fan-in, handoff) and when via a literal "Use when:" clause, satisfying both halves; not 2 because the trigger guidance is explicit rather than implied.	3 / 3
Trigger Term Quality	"Use when: wave-execute, run wave, epic wave, parallel stories SDC" includes some natural phrases ("run wave", "epic wave") but leans on jargon ("SDC", "wave-execute") and misses common variations, so it does not reach the broad natural-coverage anchor at 3.	2 / 3
Distinctiveness Conflict Risk	Targets a clear niche — wave-level story orchestration with distinct triggers ("epic wave", "parallel stories SDC") — making misfiring onto unrelated skills unlikely; not 2 because the scope is sharply bounded rather than broadly overlapping.	3 / 3
	Total	11 / 12 Passed

Validation

87%

Warnings & errors only

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

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
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
Path: .grok/skills/aiox-wave-execute/SKILL.md
Commit: 0b32b68

Reviewed: about 13 hours ago

Table of Contents

Discovery Implementation Validation

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.