aiox-dev

Activate Dex (dev) for Full Stack Developer. Use for code implementation, debugging, refactoring, and development best practices

Quality

63%

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 ./.claude/skills/AIOX/agents/dev/SKILL.md

Quality

Content

56%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 with strong workflow validation gates, but it is markedly verbose (redundant command lists, conceptual examples) and monolithically inlines a large YAML config rather than splitting detail into bundle files.

Suggestions

Deduplicate the command catalog: keep one canonical list and have Quick Commands reference it instead of re-listing commands.

Remove or relocate the conceptual decision_logging JS example and trim the CodeRabbit execution_guidelines prose that restates the workflow block.

Move the large agent-definition YAML and CodeRabbit integration detail into bundle files (e.g., references/) referenced one level deep from SKILL.md to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The ~575-line body repeats the command list twice (YAML commands and Quick Commands), includes a conceptual JS example in decision_logging, and pads CodeRabbit prose that restates the workflow — noticeably verbose with several padded sections.	2 / 5
Actionability	Concrete commands (develop, run-tests), explicit cli paths, a 900000ms timeout, and copy-ready CodeRabbit invocations provide mostly executable guidance with only minor gaps.	4 / 5
Workflow Clarity	develop-story's order-of-execution includes validation gates ('Only if ALL pass'), and CodeRabbit self-healing has an explicit validate→fix→retry loop with a HALT, giving a clear sequence with most checkpoints present.	4 / 5
Progressive Disclosure	No bundle files exist, so the entire agent definition YAML is inlined as one monolithic block; dependency references are signaled in a dependencies section, but content that could be split stays inline.	3 / 5
	Total	13 / 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 cleanly states a domain and several concrete actions with an explicit 'Use for' trigger, but the persona-activation phrasing of the 'what' and the broad, generic triggers limit distinctiveness.

Suggestions

Reword the 'what' as a capability rather than a persona activation (e.g., 'Implements, debugs, and refactors code across the full stack').

Add concrete trigger synonyms or specifics users would say (e.g., 'fix a bug', 'refactor a module', 'wire up an API endpoint') to improve trigger term quality.

Tighten the 'when' clause to scope away from general coding assistance (e.g., tie it to story-driven implementation) to reduce overlap with other dev skills.

Dimension	Reasoning	Score
Specificity	Names the domain (Full Stack Developer) and three concrete actions ('code implementation, debugging, refactoring') plus one vague item ('development best practices'), matching the 'several specific actions; minor gaps' anchor.	4 / 5
Completeness	Both 'what' (Activate Dex (dev) for Full Stack Developer) and an explicit 'when' (Use for ...) are present, but the 'what' is a persona-activation statement rather than a crisp capability, so it is not a 5.	4 / 5
Trigger Term Quality	Natural user terms ('code implementation', 'debugging', 'refactoring') are present, but no synonyms or file-extension variants, so it stops short of comprehensive coverage.	4 / 5
Distinctiveness Conflict Risk	The 'Full Stack Developer' framing gives a niche, but the listed triggers ('implementation, debugging, refactoring, best practices') are broad and overlap with many general coding skills.	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
skill_md_line_count	SKILL.md is long (583 lines); consider splitting into references/ and linking	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: .claude/skills/AIOX/agents/dev/SKILL.md
Commit: 4ef6530

Reviewed: 9 days 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.