aiox-squad-creator

Activate Craft (squad-creator) for Squad Creator. Use to create, validate, publish and manage squads

Quality

52%

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

Quality

Content

38%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 offers concrete commands and three sequenced workflows with validation steps, but is weighed down by a large embedded YAML agent-definition block that is operational padding rather than skill knowledge, with no executable script examples and no error-feedback loops. Progressive disclosure is weak because the bulk of content is an inlined config whose referenced dependency files are not bundled.

Suggestions

Move the large YAML agent-definition/activation block out of SKILL.md into a referenced file; keep only a brief overview so the skill body stays lean and navigable.

Add at least one concrete script-invocation example (e.g. how to run squad-validator.js against a manifest) so the guidance is executable rather than just command names.

Add an explicit feedback loop for validation failures (e.g. 'If *validate-squad reports schema errors, fix the flagged fields in squad.yaml and re-run before publishing') to lift workflow clarity for the destructive publish/migrate operations.

Dimension	Reasoning	Score
Conciseness	The body is dominated by a ~200-line embedded YAML agent-definition block (persona, zodiac, greeting levels, visibility arrays) that is operational padding Claude does not need, matching the 'noticeably verbose; several padded sections' anchor.	2 / 5
Actionability	Concrete commands with flags are provided (e.g. 'design-squad --docs ./path', 'create-squad {name} --from-design'), but no script is ever invoked with an executable example and several commands are placeholders, leaving key execution details missing.	3 / 5
Workflow Clarity	Three numbered workflows with validation steps are clear, but there are no explicit error-feedback loops (what to do when validation fails) for destructive publish/migrate operations, which the rubric caps at 3 without such checkpoints.	3 / 5
Progressive Disclosure	No bundle files exist and a massive YAML config that the file itself says maps to external dependency files is inlined into SKILL.md, matching the 'content that clearly belongs in separate files is inlined' anchor.	2 / 5
	Total	10 / 20 Passed

Description

66%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 lists concrete actions and identifies a distinct squads niche, but front-loads activation machinery and lacks an explicit 'Use when...' trigger clause with concrete trigger phrases, capping completeness. It is solid but not exemplary.

Suggestions

Replace 'Activate Craft (squad-creator) for Squad Creator.' with a direct capability statement; the activation framing is internal noise that does not help users find the skill.

Add an explicit trigger clause, e.g. 'Use when creating, validating, publishing, or managing AIOX squads, or when the user mentions squad manifests or squad structure.'

Include natural synonyms and artifact forms (e.g. 'squad manifest', 'squad.yaml') so triggers match how users actually phrase requests.

Dimension	Reasoning	Score
Specificity	Names the squads domain plus four concrete verbs ('create, validate, publish and manage squads'), giving several specific actions; the leading activation phrasing is padding and 'manage' is generic, so it sits just below the comprehensive 5 anchor.	4 / 5
Completeness	Has a clear 'what' (create/validate/publish/manage squads) but only a weak 'Use to...' restatement rather than an explicit 'Use when...' trigger clause, so per the cap guidance completeness stays at 3.	3 / 5
Trigger Term Quality	Good keyword coverage with natural phrases like 'create a squad' or 'validate my squad' mapping to 'create, validate, publish'; missing synonyms and the artifact form ('squad manifest'), which the 5 anchor requires.	4 / 5
Distinctiveness Conflict Risk	The 'squads' niche within the AIOX ecosystem is mostly distinct with only minor overlap risk against closely related squad skills; not fully clear-cut enough for 5.	4 / 5
	Total	15 / 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: SynkraAI/aiox-core
Path: .claude/skills/AIOX/agents/squad-creator/SKILL.md
Commit: 4ef6530

Reviewed: 3 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.