CtrlK
BlogDocsLog inGet started
Tessl Logo

aiox-full-sdc

EXECUTE lean Full Story Development Cycle for one story: plan via CLI, run validate → develop → review (QG loop) → close with Sequence Lock, durable progress under .aiox/sdc/. Use when: full-sdc, full cycle, SDC, run story end-to-end.

66

Quality

81%

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

SKILL.md
Quality
Evals
Security

Quality

Content

77%

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

A highly actionable orchestrator skill with excellent workflow clarity and explicit validation/feedback checkpoints. Its weaknesses are minor redundancy across dispatch sections and a monolithic single-file structure that does not leverage progressive disclosure.

Suggestions

De-duplicate the preflight gate and the 'verify in the main session' instruction, stating them once and cross-referencing from the Grok dispatch section.

Consider extracting the detailed QG-loop branching rules or the persona-dispatch table into a reference file so SKILL.md stays a lean overview, enabling clearer progressive disclosure.

DimensionReasoningScore

Conciseness

Mostly lean and information-dense with tables and terse bullets, but the preflight gate and verify-after-subagent steps are restated across the Invocation, EXECUTE loop, and Grok dispatch sections, so it could be tightened.

2 / 3

Actionability

Provides concrete, executable CLI commands with flags ('aiox sdc plan/next/verify/preflight'), a phase-map table, and precise loop steps that are copy-paste ready (with justified placeholders).

3 / 3

Workflow Clarity

The EXECUTE loop is explicitly numbered with a mandatory preflight gate (HALT on exit 5), per-phase verify --mark checkpoints, and a fully specified review→apply_qa_fixes feedback loop with max-3 iteration cap and escalation rules.

3 / 3

Progressive Disclosure

Well-organized into clear sections and signals one-level-deep task-SOT files in the phase map, but it is a monolithic single file (~150 lines) with all detail inline and no bundle files to split content progressively.

2 / 3

Total

10

/

12

Passed

Description

85%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A specific, complete, and distinctive description with an explicit 'Use when' trigger clause. Its weakest point is trigger-term quality, where the keywords are somewhat product-internal and could be broadened with more natural phrasings.

Suggestions

Broaden the 'Use when' triggers with natural-language variations users would actually say, e.g. 'run the full story development cycle', 'develop a story end to end', alongside the existing 'full-sdc', 'full cycle', 'SDC'.

Consider spelling out 'SDC' (Story Development Cycle) once in the description so the trigger term is meaningful to users unfamiliar with the acronym.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ('plan via CLI', 'run validate → develop → review (QG loop) → close with Sequence Lock', 'durable progress under .aiox/sdc/') rather than vague language.

3 / 3

Completeness

Explicitly answers both what ('EXECUTE lean Full Story Development Cycle...') and when via an explicit 'Use when:' clause with named triggers.

3 / 3

Trigger Term Quality

The 'Use when' clause lists relevant terms ('full-sdc, full cycle, SDC, run story end-to-end') but they lean toward internal jargon and miss common natural variations a user might say ('story development cycle', 'develop a story').

2 / 3

Distinctiveness Conflict Risk

A clear niche (one-story full SDC with named phases under .aiox/sdc/) with distinct triggers unlikely to fire for unrelated skills.

3 / 3

Total

11

/

12

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

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.