Name: scrum-master
Rating: 75.2 (1 reviews)
Author: alirezarezvani

scrum-master

Advanced Scrum Master skill for data-driven agile team analysis and coaching. Use when the user asks about sprint planning, velocity tracking, retrospectives, standup facilitation, backlog grooming, story points, burndown charts, blocker resolution, or agile team health. Runs Python scripts to analyse sprint JSON exports from Jira or similar tools: velocity_analyzer.py for Monte Carlo sprint forecasting, sprint_health_scorer.py for multi-dimension health scoring, and retrospective_analyzer.py for action-item and theme tracking. Produces confidence-interval forecasts, health grade reports, and improvement-velocity trends for high-performing Scrum teams.

Quality

94%

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

The canonical home for this skill is scrum-master in alirezarezvani/claude-skills

Quality

Content

88%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 is well-structured, actionable, and sequenced with strong validation checkpoints, but it suffers from duplicated metrics content and references several bundle files that are not actually present in the skill bundle.

Suggestions

Remove or deduplicate the "Key Metrics & Targets" table, since every target already appears in the Sprint Health Scorer dimension table above.

Ship the referenced bundle files (scripts/*.py, references/*.md, assets/*.json and templates) or remove the dangling references so signaled navigation paths resolve.

Trim the self-promotional intro line ("The unique value is in the three Python analysis scripts...") since the value is self-evident from the sections that follow.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean — tables, code blocks, and numbered steps assume Claude's Scrum knowledge without padding — but the "Key Metrics & Targets" table duplicates targets already stated in the Sprint Health Scorer dimension table (e.g. Commitment Reliability >85%, Scope Stability <15%, CV <20%), which could be trimmed.	4 / 5
Actionability	Copy-paste-ready commands like "python velocity_analyzer.py sprint_data.json --format text", a concrete input JSON schema, and specific per-workflow steps give fully executable guidance covering the common cases.	5 / 5
Workflow Clarity	Each workflow (Sprint Planning, Daily Standup, Review, Retrospective) is a clearly numbered sequence with explicit validation checkpoints and conditional branches (e.g. "If fewer than 3 sprints... stop and prompt", "If a blocker is unresolved after 2 days, escalate"), including feedback loops for the analytics batch operations.	5 / 5
Progressive Disclosure	Structure is good with a table of contents and clearly signaled one-level-deep references (references/velocity-forecasting-guide.md, assets/sample_sprint_data.json, etc.), but the referenced bundle directories (references/, scripts/, assets/) do not exist in the bundle, so several signaled paths do not resolve — a real navigation gap that keeps this below a 5.	4 / 5
	Total	18 / 20 Passed

Description

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

This is a strong, third-person description that concretely states capabilities, outputs, and trigger conditions with comprehensive natural trigger terms. Its only soft spot is the mild over-claim "for high-performing Scrum teams", which does not materially reduce the score.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions and outputs — "Monte Carlo sprint forecasting", "multi-dimension health scoring", "action-item and theme tracking", "confidence-interval forecasts, health grade reports, and improvement-velocity trends" — with comprehensive coverage rather than vague language.	5 / 5
Completeness	It explicitly answers both what ("data-driven agile team analysis and coaching... Runs Python scripts to analyse sprint JSON exports") and when ("Use when the user asks about...") with concrete trigger phrases.	5 / 5
Trigger Term Quality	The "Use when the user asks about sprint planning, velocity tracking, retrospectives, standup facilitation, backlog grooming, story points, burndown charts, blocker resolution, or agile team health" clause covers the natural phrases a user would actually say, including synonyms across the Scrum domain.	5 / 5
Distinctiveness Conflict Risk	The Scrum Master analytics niche is clear and the script- and ceremony-specific triggers (burndown charts, sprint forecasting, action-item tracking) are unlikely to fire for unrelated skills, giving minimal conflict risk.	5 / 5
	Total	20 / 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
referenced_paths_exist	Referenced path issues: 12 missing	Warning

	Total	15 / 16 Passed

Repository: alirezarezvani/claude-skills
Path: .gemini/skills/scrum-master/SKILL.md
Commit: 19392f7

Reviewed: ~3 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.