CtrlK
BlogDocsLog inGet started
Tessl Logo

review-story

QA gate for a story — verdict PASS/CONCERNS/FAIL/WAIVED + lifecycle transition. Use when: review story, qa gate, *qa-gate, /review-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

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 lean, well-organized instruction-only skill that routes to external Task SOT files with clear one-level references and explicit verification checkpoints. Main limitation is that executable review detail lives in the referenced task files rather than inline, which is appropriate for its design but caps self-contained actionability.

Suggestions

Add a one-line note on what the FAIL feedback loop entails (e.g., the fix list handed to apply-qa-fixes) to push workflow_clarity toward 5.

Consider inlining a minimal gate-file schema or verdict-decision summary so the skill is more self-contained without the external task files.

Make the Post-phase verification checklist explicitly gated (require all boxes before lifecycle transition) to strengthen the validation checkpoint.

DimensionReasoningScore

Conciseness

Lean ~49-line body with no over-explanation of concepts Claude knows; every section earns its place and assumes competence, matching the 5-anchor.

5 / 5

Actionability

Concrete pointers (load qa-gate.md, write gate under docs/qa/gates/, verdict values, status table) but the core review execution is deferred to external Task SOT files rather than self-contained, fitting the 4-anchor with minor gaps.

4 / 5

Workflow Clarity

Numbered Protocol plus a status-policy table and an explicit Post-phase verification checklist give a clear sequenced workflow with checkpoints; the FAIL-recovery feedback loop is only lightly specified, leaving a minor gap below the 5-anchor.

4 / 5

Progressive Disclosure

Under 50 lines and well-organized with clearly signaled one-level-deep references (Primary/Supporting Task SOT, lifecycle rules), so the simple-skill exception applies and content is appropriately split.

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.

A tight, well-structured description that explicitly answers both what and when with concrete trigger phrases and a distinct QA-gate niche. Minor room to expand action coverage, but it avoids vagueness and over-claims entirely.

DimensionReasoningScore

Specificity

Names the QA-gate domain and several concrete actions (verdict set PASS/CONCERNS/FAIL/WAIVED plus lifecycle transition), with only minor coverage gaps, fitting just above the 3-anchor.

4 / 5

Completeness

Clearly states both what it does ('QA gate for a story — verdict ... + lifecycle transition') and when to use it ('Use when: review story, qa gate, *qa-gate, /review-story'), matching the 5-anchor.

5 / 5

Trigger Term Quality

Includes natural phrases a user would say ('review story', 'qa gate') plus the slash-command and glob forms; good coverage though a few common synonyms are absent.

4 / 5

Distinctiveness Conflict Risk

The story-QA-gate niche with a verdict taxonomy and /review-story trigger is clearly distinct with minimal overlap risk against other skills.

5 / 5

Total

18

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

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.