CtrlK
BlogDocsLog inGet started
Tessl Logo

aiox-sdc

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

63

Quality

75%

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

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is an exemplary lean orchestrator overview: a compact phase table with explicit gates and a focused rules list, all assuming Claude's competence. It sequences a multi-step workflow with validation checkpoints and feedback loops while keeping every token load-bearing.

DimensionReasoningScore

Conciseness

The body is a lean table plus a terse rules list with no padding or explanation of concepts Claude already knows; every line (phase routing, agent handles, file SOTs, the npm quality-gate command) earns its place.

3 / 3

Actionability

Guidance is concrete and copy-paste ready: specific sub-skill names, agent handles (@sm, @po, @dev, @qa, @devops), task-SOT file names, and the exact command `npm run lint && npm run typecheck && npm test`; per the instruction-only scoring note, absence of code is not penalized when guidance is this specific.

3 / 3

Workflow Clarity

The Phases table sequences 1→2→3→4→4b→5→6 with explicit validation checkpoints (Validate phase, '→ Ready on GO', 'approved → Done') and a feedback loop (4b Fix, 'QG loop ≤3'), matching the 'clear sequence with explicit validation steps; feedback loops for error recovery' anchor.

3 / 3

Progressive Disclosure

No bundle files exist locally, but the skill is under 50 lines and well-organized into a Phases table and Rules section; its external references (task-SOT files, constitution, full-sdc SKILL.md) are one level deep and clearly signaled via the table columns, so per the simple-skills note it scores 3.

3 / 3

Total

12

/

12

Passed

Description

50%

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 identifies the workflow and its slash command but stops short of giving explicit use-when triggers or distinguishing it cleanly from the preferred /aiox-full-sdc sibling. It is concise but underspecified on when Claude should invoke it.

Suggestions

Add an explicit 'Use when ...' clause naming natural triggers (e.g., starting a new story, moving a story through dev/review, or when the user mentions the SDC).

Clarify how /aiox-sdc differs from /aiox-full-sdc so the routing decision is unambiguous rather than just a 'prefer' hint.

Replace some internal jargon ('lean orchestrator') with plain-language action terms users would actually say.

DimensionReasoningScore

Specificity

It names a domain and a single action ("Run the AIOX Story Development Cycle") but does not enumerate multiple concrete actions, matching the 'names domain and some actions, but not comprehensive' anchor rather than the multi-action level 3.

2 / 3

Completeness

It states what the skill does ("Run the AIOX Story Development Cycle") but provides no explicit "Use when..." trigger guidance, so per the judging guideline completeness is capped at 2 ('has what, but when is missing or only implied').

2 / 3

Trigger Term Quality

Relevant terms like "Story Development Cycle" and the slash commands appear, but the phrasing leans on internal jargon ("lean orchestrator", slash names) without natural-language variations a user would commonly say, fitting 'some relevant keywords but missing common variations'.

2 / 3

Distinctiveness Conflict Risk

The AIOX SDC niche is fairly specific, but the description itself directs users to a competing skill ("Prefer /aiox-full-sdc"), signaling overlap with a sibling skill and matching 'somewhat specific but could still overlap with similar skills'.

2 / 3

Total

8

/

12

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.