aiox-squad-creator

Squad Creator (Craft). Use to create, validate, publish and manage squads

Quality

72%

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 ./.codex/skills/aiox-squad-creator/SKILL.md

Quality

Content

80%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 content is concise and offers concrete, mostly-executable activation guidance with a clear command catalog. Its main gaps are the absence of explicit validation checkpoints in the workflow and references to files that are neither bundled nor clearly structured for navigation.

Suggestions

Add an explicit validation checkpoint to the Activation Protocol (e.g., verify the agent file loaded successfully before adopting the persona) to raise workflow_clarity.

Either bundle the referenced files (squad-creator.md, constitution.md, generate-greeting.js) under references/scripts/assets or clearly mark them as external project artifacts so progressive disclosure structure is sound.

Include a short example greeting output or a *help command sample to close the minor actionability gap.

Dimension	Reasoning	Score
Conciseness	The body is lean and efficient with no over-explanation of concepts Claude already knows; every line (persona load, greeting command, command catalog, non-negotiables) earns its place, matching the score-5 anchor.	5 / 5
Actionability	It provides concrete executable guidance with specific file paths and commands ("Load .aiox-core/development/agents/squad-creator.md", "node .aiox-core/development/scripts/generate-greeting.js squad-creator") plus a command catalog, fitting the score-4 anchor of mostly executable guidance with minor gaps (e.g., no example outputs).	4 / 5
Workflow Clarity	The four-step Activation Protocol gives a clear sequence but lacks explicit validation checkpoints or feedback loops, matching the score-3 anchor of steps listed with checkpoints missing or implicit; the destructive/batch cap does not apply since this is a persona activator, not a destructive operation.	3 / 5
Progressive Disclosure	The body references external files (.aiox-core/development/agents/squad-creator.md, constitution.md, generate-greeting.js) that are not present in any bundle directory and are not clearly signaled as navigable references, fitting the score-3 anchor of references present but not clearly signaled despite otherwise reasonable section organization.	3 / 5
	Total	15 / 20 Passed

Description

65%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 includes an explicit "Use to..." trigger, giving it solid specificity and completeness. Its weaknesses are generic trigger terms lacking natural synonyms and an undefined "squads" concept that slightly limits distinctiveness.

Suggestions

Add natural user-facing trigger phrases and synonyms (e.g., "Use when the user wants to build, set up, or scaffold an AIOX squad") to improve trigger_term_quality.

Briefly define what a "squad" is or reference the project artifact so the domain object is concrete rather than abstract.

Expand the "when" clause with concrete triggering scenarios rather than restating the verbs, to push completeness toward 5.

Dimension	Reasoning	Score
Specificity	Lists several specific concrete actions ("create, validate, publish and manage squads") akin to the score-5 anchor, but the object "squads" is left undefined, leaving minor gaps in coverage that fit the score-4 anchor.	4 / 5
Completeness	It answers both "what" (create/validate/publish/manage squads) and "when" ("Use to..."), matching the score-4 anchor where both are present but the when clause could be more explicit with concrete trigger phrases.	4 / 5
Trigger Term Quality	The trigger terms are task verbs ("create, validate, publish and manage squads") rather than natural user phrases or synonyms; comparable to "Works with PDF files" which sits at the score-3 anchor with relevant but incomplete keyword coverage.	3 / 5
Distinctiveness Conflict Risk	"Squads" is a niche domain term making it mostly distinct with only minor overlap risk, fitting the score-4 anchor even though the term's exact meaning is underspecified.	4 / 5
	Total	15 / 20 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: SynkraAI/aiox-core
Path: .codex/skills/aiox-squad-creator/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.