CtrlK
BlogDocsLog inGet started
Tessl Logo

aiox-sdc

Run the AIOX Story Development Cycle. Prefer /aiox-full-sdc (lean orchestrator). Slash: /aiox-sdc

60

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.grok/skills/aiox-sdc/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

92%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 tight, well-structured orchestrator: a clearly sequenced phase table with explicit gates and a bounded fix loop, plus a concise rules list, all without padding.

DimensionReasoningScore

Conciseness

The body is dense and lean — a phase table plus a short rules list — with no concept over-explanation and every line earning its place, matching the 'Lean and efficient; assumes Claude's competence' anchor.

5 / 5

Actionability

It gives concrete references (named skills, @agents, task SOT files, and the 'npm run lint && npm run typecheck && npm test' command), but as an orchestrator it delegates actual execution to sub-skills rather than providing copy-paste steps, leaving minor gaps.

4 / 5

Workflow Clarity

The phases table lays out a clear 1→6 sequence with explicit validation gates ('Ready on GO', 'approved → Done'), a bounded feedback loop ('QG loop ≤3'), and quality gates guarding the destructive push step — matching the explicit-validation anchor.

5 / 5

Progressive Disclosure

The overview cleanly signals one-level-deep references (each phase's task SOT file, the constitution, and sub-skills) via a well-structured table, with content appropriately split across the system rather than inlined.

5 / 5

Total

19

/

20

Passed

Description

48%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 is concise and names a distinct niche, but it relies on a single generic action verb and omits any explicit 'Use when' trigger guidance, leaving the 'when' only weakly implied by the slash command.

Suggestions

Add an explicit trigger clause, e.g. 'Use when running or resuming the AIOX story development workflow.'

Replace the generic 'Run' with concrete capabilities, e.g. 'Orchestrates the create → validate → develop → review → close → push story workflow.'

Disambiguate from /aiox-full-sdc by stating when this skill itself applies versus when to defer to the lean orchestrator.

DimensionReasoningScore

Specificity

The description names the domain ('AIOX Story Development Cycle') but the only action verb is the generic 'Run', matching the anchor 'Names the domain but actions are minimal or generic'; it does not list concrete capabilities of the cycle.

2 / 5

Completeness

It clearly states what the skill does ('Run the AIOX Story Development Cycle') but provides no explicit 'Use when...' trigger clause, so completeness is capped at 3 per the missing-trigger guideline.

3 / 5

Trigger Term Quality

Relevant keywords ('Story Development Cycle', 'SDC', '/aiox-sdc', '/aiox-full-sdc') are present but are niche jargon with no natural-language synonyms or variations a user might spontaneously say.

3 / 5

Distinctiveness Conflict Risk

'AIOX Story Development Cycle' is a clear niche with distinct triggers, but the explicit 'Prefer /aiox-full-sdc' creates minor overlap risk with that closely related sibling skill.

4 / 5

Total

12

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
SynkraAI/aiox-core
Reviewed

Table of Contents

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.