aiox-sm

Activate River (sm) for Scrum Master. Use for user story creation from PRD, story validation and completeness checking, acceptance criteria definition, story refinement, sprint planning, backlog grooming, retrospectives, daily standup fa...

Quality

64%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/AIOX/agents/sm/SKILL.md

Quality

Content

48%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.

The body functions as an agent-activation document with clear orchestration and delegation guidance, but it is padded with persona ceremony and inlines a large YAML config that belongs in separate files, while its core task mechanics reference bundle files that are absent.

Suggestions

Move the inlined agent-definition YAML (persona, greeting_levels, vocabulary, activation-instructions) into a separate bundled file and keep SKILL.md as a lean overview with a one-level reference, to improve conciseness and progressive disclosure.

Provide the referenced dependency files (create-next-story.md, story-tmpl.yaml, story-draft-checklist.md) in the bundle, or inline the concrete story-drafting steps so the skill is actionable without missing files.

Trim persona padding (zodiac, Portuguese vocabulary, archetypal greeting ceremony, repeated CRITICAL/MANDATORY rules) that does not contribute to executing Scrum Master tasks.

Dimension	Reasoning	Score
Conciseness	The body is noticeably verbose and padded: an inlined ~180-line YAML agent definition includes persona ceremony (zodiac "♓ Pisces", Portuguese vocabulary lists, archetypal greeting levels, emoji_frequency, signature closings) and elaborate activation substeps that do not help Claude perform the actual task.	2 / 5
Actionability	Delegation tables, command lists, and a numbered typical-workflow give concrete orchestration guidance, but the core deliverable mechanics (how to actually draft a story) are delegated to dependency files (create-next-story.md, story-tmpl.yaml) that are not present in the bundle, leaving key details missing.	3 / 5
Workflow Clarity	The "Typical Workflow" lays out a clear 6-step sequence (create → quality check → handoff → monitor → correct → close) with an explicit quality-check checkpoint; it is not a destructive/batch operation so the cap does not apply, though some steps like "Monitor progress" are high-level.	4 / 5
Progressive Disclosure	There are clear section headers and a one-level dependency-resolution scheme, but the large agent-definition YAML is inlined in SKILL.md rather than split out, and the referenced dependency files do not exist in the bundle, leaving the structure only partially organized.	3 / 5
	Total	12 / 20 Passed

Description

80%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 strong description with an explicit "Use for" trigger and a comprehensive list of concrete Scrum Master actions. Its main defect is that the text is truncated mid-word, leaving the final trigger term incomplete.

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") giving comprehensive coverage of the Scrum Master domain, matching the score-5 anchor.	5 / 5
Completeness	It has both a "what" ("Activate River (sm) for Scrum Master") and an explicit "when" ("Use for ..."), so it is not capped at 3, but the description is literally truncated mid-word ("daily standup fa...") leaving the trigger list slightly incomplete, keeping it below a 5.	4 / 5
Trigger Term Quality	Natural agile terms a user would say ("user story", "sprint planning", "backlog grooming", "retrospectives", "daily standup", "acceptance criteria", "PRD") give good coverage, but there is little synonym variation and the truncation cuts off "facilitation".	4 / 5
Distinctiveness Conflict Risk	The Scrum Master framing with distinct agile triggers carves a clear niche with minimal conflict risk, though it could overlap with closely related PM/PO agile skills, fitting the score-4 anchor rather than 5.	4 / 5
	Total	17 / 20 Passed

Validation

87%

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

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 1 suspicious	Warning

	Total	14 / 16 Passed

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

Reviewed: 19 days 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.