aiox-sm

Activate the AIOX Scrum Master agent (River). Use for user story creation from PRD, story validation and completeness checking, acceptance criteria definition, story refinement, sprint planning, backlog grooming, retrospectives, daily standup facilitation, and local branch management (create/switch/list/delete local branches, local merges). ... Trigger when user asks to sm, or says 'activate sm', 'switch to sm', '@sm'.

Quality

67%

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 ./.kimi/skills/aiox-sm/SKILL.md

Quality

Content

42%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 content is over-padded and duplicates information across inline YAML and surrounding markdown, with execution detail offloaded to missing external files. Workflow and disclosure suffer from absent validation steps and a monolithic inlined definition.

Suggestions

Extract the complete YAML agent definition into a separate reference file and keep SKILL.md as a concise overview pointing to it, removing the duplicated command tables.

Add explicit validation/feedback steps (e.g., run story-checklist and only proceed on pass) to the story-creation and branch-management workflows.

Trim persona filler (zodiac, vocabulary lists, repeated DO/DO-NOT lines) that does not change Claude's behavior.

Dimension	Reasoning	Score
Conciseness	The body is noticeably verbose: it inlines a ~180-line YAML block, duplicates command listings across three places, and includes irrelevant persona detail (zodiac, repeated DO/DO-NOT directives) that Claude does not need.	2 / 5
Actionability	Concrete commands and allowed git operations are listed, but the actual execution guidance for tasks like *draft is deferred to external dependency files that are not bundled, leaving key steps unspecified.	3 / 5
Workflow Clarity	A numbered Typical Workflow and branch workflow exist, but neither includes validation checkpoints or feedback loops for destructive/batch operations (branch delete, local merge), which caps this dimension at 3 per the rubric.	3 / 5
Progressive Disclosure	The body has section structure but inlines a large YAML agent definition that belongs in a separate reference file, and points to external paths (command-authority-matrix.md, .aiox-core/development/...) that are not present in the bundle.	3 / 5
	Total	11 / 20 Passed

Description

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

The description is specific, complete, and well-triggered, clearly communicating the agent's purpose and invocation conditions. It is slightly held back on trigger term breadth by relying on abbreviated 'sm' forms over full synonyms.

Suggestions

Add spelled-out trigger synonyms like 'scrum master' alongside the 'sm' abbreviations so users who say the full phrase also match.

Remove or replace the inline '...' ellipsis with the omitted content so the description reads as a complete, self-contained statement.

Dimension	Reasoning	Score
Specificity	Lists many concrete actions (story creation from PRD, validation, acceptance criteria, sprint planning, branch create/switch/list/delete) with comprehensive coverage of the agent's capabilities.	5 / 5
Completeness	Explicitly answers both what (activate agent plus a detailed capability list) and when ('Trigger when user asks to sm, or says activate sm, switch to sm, @sm').	5 / 5
Trigger Term Quality	Includes natural trigger phrases ('activate sm', 'switch to sm', '@sm') a user would say, but misses spelled-out synonyms like 'scrum master' and a few common variations.	4 / 5
Distinctiveness Conflict Risk	Scoped to a specific Scrum Master role with concrete branch-management boundaries and implicit NOT-for guidance, giving it a clear niche with minimal conflict risk.	5 / 5
	Total	19 / 20 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
relative_links	Relative link issues: 1 suspicious	Warning

	Total	15 / 16 Passed

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

Reviewed: 2 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.