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.

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

85%

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 lean, well-structured, gated workflow with strong validation checkpoints and clear organization. Its main gap is actionability: the substantive procedure lives in the referenced task file rather than being self-contained in SKILL.md.

Suggestions

Inline a minimal concrete checklist of what 'execute po-close-story.md' entails so SKILL.md is actionable without the external task file.

Add one short example of an acceptable closure entry vs a rejected one to make the 'administrative closure entry' gate unambiguous.

Dimension	Reasoning	Score
Conciseness	The body is lean bullet-driven prose with no concept explanations or padding; every line (gates, protocol, forbidden list) earns its place, matching the score-3 anchor.	3 / 3
Actionability	The pre-close gates and post-phase checklist are concrete, but the core execution ('Load and execute po-close-story.md') delegates the actual procedure to an external file, so guidance is incomplete per the score-2 anchor.	2 / 3
Workflow Clarity	Numbered pre-close gates, a 'HALT on hard fail' feedback loop, a numbered protocol, and a post-phase verification checkbox list provide explicit checkpoints, matching the score-3 anchor.	3 / 3
Progressive Disclosure	As a simple under-50-line skill with no bundle files, the well-organized sections (Task SOT, Input, gates, Protocol, verification, Forbidden) meet the score-3 simple-skill allowance.	3 / 3
	Total	11 / 12 Passed

Description

90%

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, third-person, and clearly answers both what the skill does and when to use it with strong natural trigger terms. Its only weakness is that the capability statement names one action rather than enumerating several concrete actions.

Dimension	Reasoning	Score
Specificity	Names the domain ('Finalize bookkeeping for a story already completed by QA') and the constraint ('Never changes lifecycle status'), but lists a single action rather than multiple concrete actions, matching the score-2 anchor.	2 / 3
Completeness	Explicit 'what' (finalize bookkeeping, never change status) and an explicit 'Use when:' trigger clause, clearly answering both per the score-3 anchor.	3 / 3
Trigger Term Quality	'close story, *close-story, story Done, /close-story' covers the natural invocations a user would say, matching the score-3 anchor of good natural-term coverage.	3 / 3
Distinctiveness Conflict Risk	The QA-Done story closure niche with the /close-story trigger is clearly distinct from other skills and unlikely to conflict, matching the score-3 anchor.	3 / 3
	Total	11 / 12 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: SynkraAI/aiox-core
Path: .aiox-core/development/skills/close-story/SKILL.md
Commit: 0b32b68

Reviewed: about 13 hours ago

Table of Contents

Discovery Implementation Validation

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.