CtrlK
BlogDocsLog inGet started
Tessl Logo

aiox-validate-story-draft

Validate a story draft (Draft → Ready on GO). Runs the OSS PO validation task. Use when: validate story, *validate-story-draft, /validate-story-draft, story readiness.

70

Quality

87%

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

The canonical home for this skill is validate-story-draft in SynkraAI/aiox-core

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.

A tight, well-structured instruction skill with an explicit sequence, validation checklist, and feedback loops for GO/NO-GO outcomes. The only soft spot is actionability, since the detailed validation steps live in an external task file rather than inline.

Suggestions

Inline the 10-point checklist (or a one-line summary of its categories) so the skill is fully actionable without loading the external task file.

Add an explicit "if task file is missing, abort with guidance" branch to the Protocol so the fallback path is unambiguous.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence ("Task is source of truth — do not invent a parallel checklist"), with no padding or explanation of concepts Claude already knows; every section earns its place.

5 / 5

Actionability

Concrete, executable guidance is present (specific task-file paths, explicit status values, a verification checklist, a modes table), but the actual validation checklist steps are delegated to the external task file rather than stated inline, leaving minor gaps.

4 / 5

Workflow Clarity

A clear 6-step Protocol is sequenced with an explicit Post-phase verification checklist ("Must be true on disk before handing off") and feedback loops (auto-fix on GO vs. list fixes on NO-GO), matching the top anchor for sequenced validation with checklists.

5 / 5

Progressive Disclosure

Under 50 lines, single-purpose, and well-organized into clearly labeled sections (Task SOT, Input, Protocol, Post-phase verification, Forbidden, Modes), with one-level-deep references to task files; no bundle needed.

5 / 5

Total

19

/

20

Passed

Description

82%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.

A concise, third-person description that clearly answers both what the skill does and when to invoke it, with concrete trigger phrases. Specificity of the underlying actions is the weakest point, as it delegates the detailed validation work to an external task rather than enumerating it.

Suggestions

Add one or two concrete validation actions to the description (e.g., "checks the 10-point readiness checklist and appends a Change Log") to lift specificity from 3 toward 4-5.

Include a natural synonym or two in the Use-when clause (e.g., "story review", "ready a story") to broaden trigger coverage.

DimensionReasoningScore

Specificity

"Validate a story draft (Draft → Ready on GO). Runs the OSS PO validation task." names the domain and 1-2 concrete actions (validate, status transition) but coverage is narrow rather than comprehensive.

3 / 5

Completeness

It explicitly states what it does (validate a story draft, transition Draft→Ready, run the OSS PO task) and provides an explicit "Use when:" clause with concrete trigger phrases, satisfying both what and when.

5 / 5

Trigger Term Quality

"Use when: validate story, *validate-story-draft, /validate-story-draft, story readiness" gives good natural keyword coverage including the slash-command form, though a few common synonyms are absent.

4 / 5

Distinctiveness Conflict Risk

The niche is narrow and explicit (story-draft validation in the AIOX/SDC workflow) with distinct, skill-specific trigger tokens, leaving minimal overlap risk with other skills.

5 / 5

Total

17

/

20

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.