SKILLEMALL.ai

AB 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.

alirezarezvani/claude-skills Agent Skills author: alirezarezvani MIT 12 files body ≈ 2 168 tokens Open the sourcegithub.com analyzed 2 d ago

Advanced Scrum Master skill for data-driven agile team analysis and coaching.

As a process B 68/100 · Nearly there — weak spots: result and completion, running it twice

AnalyzerJiraOperations and projectstype and topics are labelled automatically from the skill text
JSON
Technical rating
A
97/100
safety, quality, tests
Safety 60%
100
Quality 40%
92
Run on models
none yet
Process rating
B
68/100
Nearly there
Result and completion w 14
0
Running it twice w 4
30
Tools and files w 18
60
the three weakest of ten parameters · all ten

How to improve

    For the model run — optional
    • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
    • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

    Guard findings · 0

    ✓ No critical or high findings

    Files scanned: 12. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    ✓ No remarks against the Agent Skills spec

    Process rating: all ten parameters 68/100

    • 0Result and completion. Does not say what the result is
    • 30Running it twice. 4 mutating operations with no state check
    • 60Tools and files. Uses tools (python) that frontmatter does not declare
    • 60Failures and branches. 2 branches
    • 70When it triggers. States when to use, but not when not to
    • 100Steps. 36 steps
    • 100Inputs and preconditions. Inputs and preconditions are listed
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 2168 tokens
    • 100Progress reporting. Reports progress

    Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

    Quality signals

    • +5Description has no quoted example phrases that should trigger the skill
    • +4Description does not say when NOT to use the skill (false activations)
    • +3Output format is not stated: the model decides each time
    • +2Single-language instructions
    • +3Description length 660: enough signal without eating the budget
    • +4Structure: 19 headings
    • +3Step-by-step instructions: 36 items
    • +4Has examples (6 code blocks)
    • +4Reference files are cited in the instructions (2 of 3)
    • +3All 3 scripts are documented
    • +1License stated

    Quality base 70; lint remarks subtract, signals add up to 100. Result: 92.