aiox-dev

Full Stack Developer (Dex). Use for code implementation, debugging, refactoring, and development best practices Triggers: implement, develop, code, fix bug, refactor, dev, @dev, story development. Use when the user runs /aiox-dev or @dev.

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/aiox-dev/SKILL.md

Quality

Content

75%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 SKILL.md body is a compact, well-structured activation protocol with concrete registration commands and a clean section layout that points one level deep to source-of-truth files. Its main gap is the absence of validation checkpoints in the protocol and the reliance on external persona files that may not exist (only a fallback is named for one of them).

Suggestions

Add an explicit validation checkpoint after Step 1 (e.g., verify `.aiox/active-agent` and the persona file exist before proceeding) to strengthen workflow_clarity for this registration flow.

Name a fallback for every external file the protocol depends on (`.grok/agents/aiox-dev.md` has none), since Step 3 only provides a fallback for `.aiox-core/development/agents/dev.md`.

Convert source-of-truth paths into markdown links or clearly marked code spans so navigation is unambiguous and the one-level-deep references are visually signaled.

Dimension	Reasoning	Score
Conciseness	The body is lean and largely assumes Claude's competence (compact protocol list, short command table, tight authority snapshot); minor padding comes from restating sources-of-truth twice and a few elaborative labels like '(13-step Coder Agent workflow)'.	4 / 5
Actionability	Step 1 provides copy-paste-ready bash that registers the active agent, and starter commands are concrete tokens, but steps 2-5 ('Load persona', 'Adopt persona', 'Greet') point at external files or describe behavior rather than giving executable commands, leaving minor gaps.	4 / 5
Workflow Clarity	A clear numbered protocol sequences registration through persona adoption and exit, with explicit blocked operations acting as guardrails; however there are no validation checkpoints confirming the persona file exists or that registration succeeded before proceeding.	4 / 5
Progressive Disclosure	Content is well-organized into focused sections that point one level deep to real source-of-truth files (`.aiox-core/development/agents/dev.md`, `.grok/agents/aiox-dev.md`); no nested multi-hop references, though the referenced paths are prose strings rather than navigable links and no bundle files exist to verify.	4 / 5
	Total	16 / 20 Passed

Description

71%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 covers concrete actions and provides explicit command-based trigger guidance, giving it solid completeness and specificity. Its main weakness is broad, high-overlap trigger terms ('code', 'develop', 'fix bug') that risk colliding with other coding skills, relying on the '/aiox-dev' token for distinctiveness.

Suggestions

Tighten distinctiveness by scoping triggers to the AIOX workflow (e.g., 'Use when the user runs /aiox-dev for story-driven full-stack development within an AIOX repo') rather than generic verbs like 'code' and 'develop'.

Reformat the description so the 'what' and 'when' are cleanly separated; the current run-on 'Triggers:' clause mid-sentence muddies the explicit 'Use when...' guidance.

Drop the redundant duplicated trigger list (it appears in both `description` and `when-to-use`) to reduce ambiguity and avoid buzzword padding.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ('code implementation, debugging, refactoring, and development best practices') covering the core dev domain, though 'best practices' is slightly generic and coverage of the full-stack scope is implied rather than enumerated.	4 / 5
Completeness	Explicitly states both what (full-stack development actions) and when ('Use when the user runs /aiox-dev or @dev' plus a Triggers clause); the 'when' is concrete via command triggers but the natural-language trigger guidance is bundled rather than cleanly separated.	4 / 5
Trigger Term Quality	Good natural keyword coverage ('implement, develop, code, fix bug, refactor, dev, @dev, story development') plus explicit slash/mention triggers, but missing common synonyms and overlap with broad terms like 'code'/'develop' that many skills share.	4 / 5
Distinctiveness Conflict Risk	The dev domain ('implement, develop, code, fix bug') is broad and high-overlap with general coding assistance and likely sibling AIOX agents; only the '/aiox-dev' and '@dev' tokens clearly disambiguate it, so moderate conflict risk remains.	3 / 5
	Total	15 / 20 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-dev/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.