scrum-master-agent
Comprehensive Scrum Master assistant for sprint planning, backlog grooming, retrospectives, capacity planning, and daily standups with intelligent context-aware reporting
Install with Tessl CLI
npx tessl i github:alirezarezvani/claude-code-skill-factory --skill scrum-master-agent67
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
82%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 description excels at specificity and trigger term quality by listing concrete Scrum ceremonies and using natural practitioner terminology. However, it lacks an explicit 'Use when...' clause, which limits its completeness score. The phrase 'intelligent context-aware reporting' is somewhat vague compared to the other concrete actions.
Suggestions
Add a 'Use when...' clause with explicit triggers like 'Use when the user mentions sprints, Scrum ceremonies, agile planning, or needs help facilitating team retrospectives'
Replace 'intelligent context-aware reporting' with more specific actions like 'generate sprint burndown charts, velocity reports, or standup summaries'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'sprint planning, backlog grooming, retrospectives, capacity planning, and daily standups with intelligent context-aware reporting' - these are distinct, actionable Scrum ceremonies and activities. | 3 / 3 |
Completeness | Clearly answers 'what does this do' with specific Scrum activities, but lacks an explicit 'Use when...' clause or equivalent trigger guidance. The when is only implied through the domain terminology. | 2 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'Scrum Master', 'sprint planning', 'backlog grooming', 'retrospectives', 'capacity planning', 'daily standups' - these are standard terms any Scrum practitioner would use. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche in Scrum/Agile methodology with distinct triggers like 'Scrum Master', 'sprint', 'backlog', 'retrospectives' - unlikely to conflict with other skills due to specific domain terminology. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
35%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is comprehensive but severely over-engineered for a SKILL.md file. It reads more like product documentation than actionable instructions for Claude. The content explains concepts Claude already understands (Scrum methodology, story points, velocity) while the actual executable guidance (scripts) is described but not provided.
Suggestions
Reduce content by 70%+ by removing explanations of Scrum concepts, tool descriptions, and best practices that Claude already knows - focus only on project-specific configurations and invocation patterns
Either provide the actual script implementations inline or remove script descriptions entirely - currently describes 7 scripts without executable code
Move the 'How to Use' quick invocations to the top as the primary content, with everything else as optional reference files
Add explicit validation steps for data parsing (e.g., 'If CSV parsing fails, check for: missing headers, date format issues, non-numeric points')
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~400+ lines with extensive explanations Claude doesn't need (what Scrum is, what story points are, detailed installation instructions). The capabilities list, tool integration details, and best practices sections explain concepts Claude already knows well. | 1 / 3 |
Actionability | Provides concrete invocation examples and output format templates, but the referenced scripts (parse_input.py, calculate_metrics.py, etc.) are described but not provided with actual executable code. The calculation formulas are helpful but incomplete without implementation. | 2 / 3 |
Workflow Clarity | Lists workflow steps (daily standups, sprint planning, mid-sprint check) but lacks explicit validation checkpoints. No feedback loops for error recovery when data parsing fails or metrics calculations produce unexpected results. | 2 / 3 |
Progressive Disclosure | Content is organized into sections but everything is inline in one massive file. References scripts that should exist separately but doesn't clearly link to them. The 'How to Use' section is buried after extensive capability descriptions. | 2 / 3 |
Total | 7 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- 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.