wave-execute

Alias for /aiox-wave-execute. Use when the user runs /wave-execute or mentions wave-execute.

Quality

73%

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

Fix and improve this skill with Tessl

tessl review fix ./.grok/skills/wave-execute/SKILL.md

Quality

Content

86%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 a compact, well-structured delegation skill that states exactly how to follow the aliased source of truth and how to recover if it is missing. Its only real limitation is that the core action relies on loading another file rather than providing self-contained executable steps.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence: a one-line summary plus three tight protocol steps with no padding or over-explanation, matching anchor 5.	5 / 5
Actionability	It gives a concrete file path and executable command (`npm run sync:skills:grok`), but the primary action is "Load and follow" another file, which is inherently indirect, fitting anchor 4 rather than 5.	4 / 5
Workflow Clarity	The three steps form a clear sequence with a conditional checkpoint ("If that file is missing, regenerate"), but it lacks an explicit verification of the regenerated file, sitting at anchor 4.	4 / 5
Progressive Disclosure	Under 50 lines with no need for external bundle references, it is organized into a clear Protocol section, qualifying for the simple-skill exception to anchor 5.	5 / 5
	Total	18 / 20 Passed

Description

61%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 cleanly and explicitly covers both what the skill is (an alias) and when to invoke it, with a distinct, low-conflict trigger. Its main weakness is that an alias describes delegation rather than concrete capabilities, leaving the action coverage thin.

Suggestions

Optionally hint at what the aliased skill does (e.g., "Alias for /aiox-wave-execute, which ...") so the description conveys capability, not only redirection.

Add a natural-language synonym alongside the command name (e.g., "wave execution") to broaden trigger coverage beyond the single literal term.

Dimension	Reasoning	Score
Specificity	The description names the concrete target ("Alias for /aiox-wave-execute") but, as an alias, it delegates rather than listing the skill's own actions, matching anchor 2's "names the domain but actions are minimal."	2 / 5
Completeness	Both "what" (alias for /aiox-wave-execute) and "when" ("Use when the user runs /wave-execute or mentions wave-execute") are explicitly present, but the "what" is thin, so it sits at anchor 4 rather than 5.	4 / 5
Trigger Term Quality	"wave-execute" is the natural command term a user would say, but only that single term is given with no synonyms or variations, fitting anchor 3.	3 / 5
Distinctiveness Conflict Risk	The trigger is a single highly specific named command (/wave-execute), giving it a clear niche with minimal overlap risk, matching anchor 5.	5 / 5
	Total	14 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: SynkraAI/aiox-core
Path: .grok/skills/wave-execute/SKILL.md
Commit: 4ef6530

Reviewed: 1 day 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.