CtrlK
BlogDocsLog inGet started
Tessl Logo

aiox-close-story

Finalize bookkeeping for a story already completed by QA. Never changes lifecycle status. Use when: close story, *close-story, story Done, /close-story.

70

Quality

86%

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 close-story in SynkraAI/aiox-core

SKILL.md
Quality
Evals
Security

Quality

Content

86%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 tightly written, well-structured SDC skill that assumes Claude's competence and front-loads blocking gates, a clear protocol, and a verification checklist. The main gap is that actionable detail lives in an external task file rather than the body, which caps actionability, and the error-recovery loop is implied rather than explicit.

Suggestions

Add an explicit validate→fix→re-check loop for gate failures instead of the single "On any hard fail → HALT" rule, which would lift workflow_clarity to 5.

Inline the one or two highest-value concrete steps from po-close-story.md (e.g., the exact closure-metadata fields to set) so the body is executable without loading the external task file.

DimensionReasoningScore

Conciseness

The body is lean and dense: short sections (Task SOT, Input, Pre-close gates, Protocol, Post-phase verification, Forbidden) with no padding or explanation of concepts Claude already knows; every line earns its place.

5 / 5

Actionability

Concrete, executable guidance is present (specific gate verdicts to check, "$ARGUMENTS[0/1]", the file to load/execute, the @po adoption), but the core task delegates to an external "po-close-story.md" so the body itself is not fully copy-paste executable end-to-end.

4 / 5

Workflow Clarity

A clear sequenced protocol with explicit blocking pre-close gates, a HALT rule, and a post-phase verification checklist provides strong checkpoints; it stops short of a 5 because the verify/fix/retry feedback loop is only implied ("On any hard fail → HALT") rather than an explicit fix-and-revalidate cycle.

4 / 5

Progressive Disclosure

This is a sub-50-line single-purpose skill with well-organized sections and no external bundle files; per the simple-skill exception, clean sectioning alone earns a 5 with no need for one-level-deep references.

5 / 5

Total

18

/

20

Passed

Description

87%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 clearly answers both 'what' and 'when' with concrete, natural trigger phrases in third-person voice. Minor gaps are the narrow action vocabulary and a few missing synonyms, which keep specificity and trigger_term_quality at 4 rather than 5.

Suggestions

Broaden the action list slightly (e.g., "finalize closure metadata, update epic index/backlog, suggest next story") to lift specificity toward 5.

Add a couple of natural synonyms to the trigger clause (e.g., "wrap up story", "finalize story") to improve trigger_term_quality.

DimensionReasoningScore

Specificity

"Finalize bookkeeping for a story already completed by QA. Never changes lifecycle status." names the domain and a concrete action (finalize bookkeeping) plus an explicit invariant, but the action set is narrow rather than a comprehensive list of operations.

4 / 5

Completeness

It explicitly states both what it does ("Finalize bookkeeping... Never changes lifecycle status") and when to use it ("Use when: close story, *close-story, story Done, /close-story") with concrete trigger phrases.

5 / 5

Trigger Term Quality

The "Use when" clause surfaces several natural terms users would actually say ("close story", "*close-story", "story Done", "/close-story") including the slash-command form, but lacks synonyms like "wrap up story" or "finalize story".

4 / 5

Distinctiveness Conflict Risk

The QA-complete + lifecycle-preserving niche and its command-style triggers (/close-story, *close-story) are distinct from other story-handling skills, giving minimal conflict risk.

5 / 5

Total

18

/

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.