CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

sprint-health

Sprint health scoring and velocity analysis for agile teams. Usage: /sprint-health <analyze|velocity> [options]

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.gemini/skills/sprint-health/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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 exemplary in its leanness and gives concrete commands, examples, and an input schema. Its weaknesses are dangling references to files outside the bundle and implicit command-to-script mapping with no validation guidance.

Suggestions

Bundle or correct the script paths so "scripts/sprint_health_scorer.py" and "scripts/velocity_analyzer.py" resolve relative to the skill directory, and drop or explain the "Skill Reference" pointer to a non-existent sibling SKILL.md.

Make the command→script mapping explicit (e.g., 'analyze runs sprint_health_scorer.py; velocity runs velocity_analyzer.py').

Add a brief validation step for the input file (e.g., required fields and expected failure behavior) to strengthen workflow clarity.

DimensionReasoningScore

Conciseness

The ~35-line body is lean: usage lines, an input format example, command examples, and script signatures, with zero explanation of concepts Claude already knows. Every token earns its place.

5 / 5

Actionability

Commands are concrete and near copy-paste ready ("/sprint-health analyze sprint-24.json --format json") with a documented input JSON and script invocation signatures, but the mapping from command to script is implicit and the script paths do not resolve within the bundle — minor gaps keeping it below fully executable.

4 / 5

Workflow Clarity

As a simple two-command skill with a documented input format the actions are largely unambiguous, but there is no guidance on validating the input file or handling errors, and the command→script mapping is left implicit.

4 / 5

Progressive Disclosure

Sections are well organized, but the referenced paths ("project-management/skills/scrum-master/scripts/sprint_health_scorer.py", "project-management/skills/scrum-master/SKILL.md") do not exist in this bundle and point outside it, and the bare "Skill Reference" pointer's purpose is unclear — references present but not clearly signaled or resolvable.

3 / 5

Total

16

/

20

Passed

Description

53%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 names a clear, distinct domain and two concrete capabilities, but it lacks any "Use when..." trigger guidance and natural-language synonyms. Adding an explicit usage-trigger clause with common variations would lift completeness and trigger-term quality.

Suggestions

Add a 'Use when...' clause (e.g., 'Use when the user asks about sprint health, velocity trends, or agile delivery metrics') to satisfy completeness.

Include natural trigger variations such as 'sprint report', 'burndown', 'retrospective', or 'delivery metrics' to improve trigger-term coverage.

Name the concrete scoring dimensions (delivery, quality, team metrics) that the skill actually evaluates to raise specificity.

DimensionReasoningScore

Specificity

"Sprint health scoring and velocity analysis" names the domain and two actions, but the actions are generic and coverage is not comprehensive — matching the anchor for naming a domain with 1-2 concrete actions, not the several-specific-actions level above.

3 / 5

Completeness

The description has a clear "what" ("Sprint health scoring and velocity analysis for agile teams") but no "Use when..." clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 3.

3 / 5

Trigger Term Quality

"sprint health", "velocity", and "agile teams" are natural terms users would say, but common variations (sprint report, burndown, retro, team metrics) are missing and the remainder is CLI usage syntax rather than trigger words.

3 / 5

Distinctiveness Conflict Risk

The agile sprint-health domain is a clear niche with minimal overlap risk, but without explicit trigger phrases it does not reach the fully distinct level of the top anchor.

4 / 5

Total

13

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

alirezarezvani/claude-skills

Path

.gemini/skills/sprint-health/SKILL.md

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.