CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

sprint-status

Fast, concise sprint snapshot — burndown and emerging risks for situational awareness. 'How is the sprint going?'

Quality

82%

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

SKILL.md
Quality
Evals
Security

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.

A dense, highly actionable operational skill with exhaustive edge-case handling and copy-paste-ready tooling (exact grep pattern, output template, escalation flags). Its weaknesses are structural rather than substantive: one dangling config paragraph and a script call embedded mid-list slightly muddy an otherwise clean layout.

DimensionReasoningScore

Conciseness

The body is operational throughout — exact paths, thresholds, and classifications with no teaching of concepts Claude already knows. A few passages could be tightened (the dangling "**`story_granularity`** — it sets the grain..." paragraph with no antecedent, and the convoluted "an `In Review` story is closed before an `In Progress` one continues: its work is written" aside), which keeps it below level 5's 'every token earns its place'.

4 / 5

Actionability

Fully executable guidance throughout: exact file-match patterns (`sprint-003.md`, `sprint-03.md`), a copy-paste Grep invocation with pattern/glob/output_mode specified, precise thresholds (4-day staleness, 40% time remaining, 10/25-point burndown bands), exact flag strings, and a complete copy-paste output template. Not below level 4 — nothing is left as vague direction or pseudocode.

5 / 5

Workflow Clarity

Phases 1–6 are clearly sequenced (find sprint → days remaining → status scan → burndown → output → escalation) with explicit checkpoints for every failure mode: missing sprint directory per workflow mode, missing `sprint-status.yaml` fallback, MISSING story files, missing dates ("burndown assessment skipped"), never-stamped timestamps, and the no-Next/all-blocked edge case with a "never say it is [done]" guard. This exceeds level 4's 'most checkpoints present' — validation coverage is exhaustive for a read-only skill.

5 / 5

Progressive Disclosure

Good structure: numbered sections with separators, a self-contained body (no bundle files exist to reference), and clearly signaled pointers to sibling commands (`/sprint-plan update`, `/story-readiness`) that are one level deep. Minor organization gaps keep it from level 5: the `story_granularity` paragraph sits orphaned between the intro and Phase 1, and the `!` script invocation is nested inside a numbered sub-list where it disrupts scan-ability.

4 / 5

Total

18

/

20

Passed

Description

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

A concise, well-targeted description with a clear what and an effective embedded trigger question. Its main limitation is minimal enumeration of concrete capabilities — it advertises only burndown and risks while the skill also produces a status table, staleness detection, and escalation flags.

Suggestions

List the skill's concrete outputs more fully, e.g. "Produces a status table, burndown verdict, stale-story flags, and at-risk Must Haves" to lift specificity.

Replace or supplement the quoted question with an explicit trigger clause: "Use when the user asks how the sprint is going, wants sprint progress/health, or needs a quick burndown check."

Add a short disambiguator against sibling skills, e.g. "For replanning use /sprint-plan; for retrospectives use /retrospective" to reduce conflict risk.

DimensionReasoningScore

Specificity

"Fast, concise sprint snapshot — burndown and emerging risks" names the domain and two concrete outputs (burndown, emerging risks), matching the 'names domain and 1-2 concrete actions' anchor. It stops short of the level-4 anchor's 'several specific actions' (no mention of the status table, staleness check, or must-have risk flags it actually produces), and is well above level 2's domain-only vagueness.

3 / 5

Completeness

The 'what' is clear ("sprint snapshot — burndown and emerging risks for situational awareness") and the 'when' is present via the explicit trigger question "'How is the sprint going?'", so it is not capped at 3. It misses level 5 because there is no explicit 'Use when...' clause naming additional trigger situations (e.g., sprint check-ins, standup prep); the trigger is a single implied question rather than concrete trigger phrases.

4 / 5

Trigger Term Quality

Natural terms like "sprint snapshot", "burndown", and the quoted user question "'How is the sprint going?'" give good keyword coverage with a directly matchable user utterance. It falls short of level 5's comprehensive synonym coverage (missing "sprint progress", "sprint health", "sprint report", "sprint status") but exceeds level 3's partial coverage because the embedded verbatim question is a strong natural trigger.

4 / 5

Distinctiveness Conflict Risk

"sprint snapshot — burndown" carves out a clear niche with distinct triggers unlikely to fire for unrelated skills, but sibling skills referenced in the body (/sprint-plan, /milestone-review, /retrospective) occupy adjacent trigger space ("review the sprint", "sprint health") and the description itself does not disambiguate against them, leaving minor overlap risk.

4 / 5

Total

15

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

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

Warning

Total

14

/

16

Passed

Repository

Donchitos/Claude-Code-Game-Studios

Path

.claude/skills/sprint-status/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.