aiox-sm

Scrum Master (River). Use for user story creation from PRD, story validation and completeness checking, acceptance criteria definition, story refinement, sprint planning, backlo...

Quality

81%

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

78%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 compact, well-structured persona-activator skill with concrete commands and a clear activation sequence. It is held back from full marks by verbatim duplication of the description in 'When To Use', mid-word truncation, and command details that live in external files.

Suggestions

Replace the verbatim 'When To Use' copy with a brief, distinct expansion (or remove it) to avoid duplicating the frontmatter description and wasting tokens.

Complete the truncated 'lo...' in the When To Use list so the full scope of activities is visible.

Add a short validation/confirmation checkpoint to the Activation Protocol (e.g. confirm the source file loaded successfully before generating the greeting) to strengthen workflow clarity.

Dimension	Reasoning	Score
Conciseness	The body is lean with short sections and no concept over-explanation, matching the efficient 4-anchor; held at 4 rather than 5 because the 'When To Use' section duplicates the frontmatter description verbatim and the body is truncated at 'lo...', both minor trims needed.	4 / 5
Actionability	Gives concrete, executable guidance — the load path `.aiox-core/development/agents/sm.md`, the command `node .aiox-core/development/scripts/generate-greeting.js sm`, and named starter commands (`draft`, `story-checklist`, `*guide`) — matching the mostly-executable 4-anchor; not a 5 because the actual command behavior is deferred to external files not shown here.	4 / 5
Workflow Clarity	The Activation Protocol is a clear 4-step sequence (load source → adopt persona → generate greeting → stay in persona) with a fallback path, matching the clear-sequence 4-anchor; not a 5 because there is no explicit validation/confirmation checkpoint, though this persona-activation task is non-destructive so the missing-feedback-loop cap does not apply.	4 / 5
Progressive Disclosure	The skill is under 50 lines with no bundle files (references/scripts/assets absent) and is organized into clearly labeled sections that point one level deep to external project artifacts (sm.md, constitution.md), matching the well-signaled simple-skill 5-anchor; not a 4 because structure and navigation are clean rather than merely 'mostly good'.	5 / 5
	Total	17 / 20 Passed

Description

83%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 specific, well-triggered description for a Scrum Master persona skill that answers both what and when with concrete agile terms. Its main weakness is that the text is truncated mid-word, which limits full confirmation of completeness and trigger coverage.

Suggestions

Complete the truncated 'backlo...' so the full list of supported activities and trigger phrases is visible rather than cut off.

Add a few natural synonyms or phrasings a user might actually say (e.g. 'writing user stories', 'grooming the backlog', 'running standup') to lift trigger-term coverage to comprehensive.

Clarify what '(River)' refers to (persona name vs product) so the niche is unambiguous to anyone outside the project.

Dimension	Reasoning	Score
Specificity	Lists many concrete actions — 'user story creation from PRD', 'story validation and completeness checking', 'acceptance criteria definition', 'story refinement', 'sprint planning', 'backlog grooming', 'retrospectives', 'daily standup facilitation' — which matches the comprehensive-coverage anchor; not a 4 because coverage is broad rather than having only minor gaps.	5 / 5
Completeness	Both 'what' (Scrum Master activities) and 'when' (explicit 'Use for ...' clause with concrete triggers) are present, satisfying the 4-anchor; held at 4 rather than 5 because the trigger list is literally cut off mid-word ('backlo...'), preventing full confirmation of explicit completeness.	4 / 5
Trigger Term Quality	Contains natural agile phrases users would say ('user story', 'PRD', 'acceptance criteria', 'sprint planning', 'backlog grooming', 'retrospectives', 'daily standup'), but the description is truncated at 'backlo...' so full synonym coverage cannot be confirmed, keeping it below the comprehensive 5 anchor.	4 / 5
Distinctiveness Conflict Risk	A clearly niched 'Scrum Master (River)' scope with distinct agile-ceremony triggers has minimal overlap with other skills, matching the clear-niche anchor; not a 4 because the trigger set is specific rather than merely 'mostly distinct'.	5 / 5
	Total	18 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: SynkraAI/aiox-core
Path: .codex/skills/aiox-sm/SKILL.md
Commit: 4ef6530

Reviewed: 1 day 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.