develop-story

Implement a story (Ready → InProgress → ready for review). Runs the OSS develop task. Use when: develop story, *develop, /develop-story, implement ACs.

Quality

70%

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

Fix and improve this skill with Tessl

tessl review fix ./.aiox-core/development/skills/develop-story/SKILL.md

Quality

Content

72%

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

The skill body is an exemplar of lean, well-structured progressive disclosure with explicit quality gates and a verification checklist. Its main weakness is that the actionable core is delegated to an external task file rather than rendered inline, leaving some actionability and workflow detail implicit.

Suggestions

Inline a brief, concrete error-recovery loop around the quality gates (e.g., "if lint/typecheck/test fails: fix and rerun until green before marking [x]").

Add one or two executable specifics from the delegated Task SOT (e.g., how to load the task, the exact checkbox update command) so the skill is more self-contained.

Make the link to the Task SOT a clickable reference and confirm the referenced path exists in the bundle to strengthen progressive-disclosure integrity.

Dimension	Reasoning	Score
Conciseness	The body is dense and terse ("Lean SDC skill. Task is source of truth.", "REUSE > ADAPT > CREATE") with no concept explanations Claude already knows; every line carries directive load.	3 / 3
Actionability	It provides concrete commands ("npm run lint", "npm run typecheck", "npm test") and branch naming ("feat/{story-id}-*"), but the core implementation work is delegated to an external Task SOT rather than given as executable inline guidance.	2 / 3
Workflow Clarity	A numbered Protocol plus explicit Quality gates and a Post-phase verification checklist give a clear sequence with checkpoints, but the detailed task sequence is delegated to the external task file and no explicit error-recovery feedback loop is written.	2 / 3
Progressive Disclosure	The body is a clear overview with well-organized sections (Task SOT, Input, Protocol, gates, verification, Forbidden) and a single clearly-signaled one-level-deep reference (".aiox-core/development/tasks/dev-develop-story.md"), with no nested references.	3 / 3
	Total	10 / 12 Passed

Description

67%

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 clearly covers both what the skill does and when to use it, with explicit triggers. It is held back by jargon and command-syntax triggers plus a single-action framing that lacks breadth of concrete capabilities.

Suggestions

Expand the action list beyond "implement a story" to name concrete sub-actions (e.g., write tests, run quality gates, update File List) for higher specificity.

Add natural-language trigger variations a user would actually say and replace jargon (spell out "acceptance criteria" alongside "ACs", drop "OSS develop task").

Tie the trigger more tightly to the story-development niche to reduce overlap with generic develop/build skills.

Dimension	Reasoning	Score
Specificity	"Implement a story (Ready → InProgress → ready for review). Runs the OSS develop task." names the domain and a primary action but lists only one concrete action rather than the multiple specific actions the top anchor requires.	2 / 3
Completeness	It states what ("Implement a story...") and an explicit "Use when:" trigger clause, satisfying both required components.	3 / 3
Trigger Term Quality	"Use when: develop story, develop, /develop-story, implement ACs" includes some natural terms, but leans on command syntax (develop, /develop-story) and jargon ("ACs", "OSS develop task") rather than broad natural variations.	2 / 3
Distinctiveness Conflict Risk	The story/AC framing is a recognizable niche, but the bare term "develop" is generic enough to overlap with other development-oriented skills.	2 / 3
	Total	9 / 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/develop-story/SKILL.md
Commit: 0b32b68

Reviewed: about 14 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.