CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

retrospective

Sprint or milestone retrospective from completed work, velocity, blockers. Actionable insights for the next iteration.

Quality

75%

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 ./.claude/skills/retrospective/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

81%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 content is a strongly actionable, well-sequenced workflow with genuine validation and error-recovery checkpoints, and a complete output template. Its weaknesses are mild padding in the generic insufficient-input preamble and repeated minimal-workflow conditionals, plus a monolithic single-file structure where the output template could be split into a reference file.

Suggestions

Trim the "Insufficient input" preamble to its operative rules; drop the off-domain asset-audit/performance-profile examples that do not concern retrospectives.

Consolidate the `workflow: minimal` / `qa.level: minimal` conditionals into one place instead of restating them in Phase 2 and Phase 6.

Move the Phase 4 markdown output template into a references/ file (e.g., references/retro-template.md) and link to it, keeping SKILL.md as the workflow overview.

DimensionReasoningScore

Conciseness

The body is mostly operational — exact paths, glob patterns, prompts, commands, and a full output template — but the ~40-line "Insufficient input" preamble pads with generic, off-domain examples ("an asset audit returning COMPLIANT", "performance profile reporting >99% headroom") irrelevant to retrospectives, and the `workflow: minimal` / `qa.level: minimal` handling repeats across Phases 2 and 6. It is tighter than anchor-2 verbosity but has several sections that could be trimmed, matching anchor 3.

3 / 5

Actionability

Guidance is fully executable: a concrete git log command (with the Git-Bash/PowerShell pitfall spelled out), exact glob patterns for existing retro detection, file paths for every data source, verbatim AskUserQuestion prompts with lettered options, and a complete copy-paste markdown output template covering the common cases. Nothing is pseudocode or hand-waved.

5 / 5

Workflow Clarity

Six phases are clearly sequenced with explicit validation checkpoints: a FOUND/ABSENT input protocol before any report, an existing-retrospective check with user-chosen recovery (update vs archive), data-existence gates with BLOCKED verdicts, and a permission ask gating every write (including the archive rename). Error paths and NOT ASSESSED — NO DATA states are explicitly defined, matching the anchor-5 pattern of explicit validation plus feedback loops.

5 / 5

Progressive Disclosure

The body is a single well-organized file with clear phase-level headers and no buried or nested references (none exist), so navigation is easy. It earns 4 rather than 5 because at ~280 lines the large Phase 4 output template (~90 lines) is a natural candidate for a one-level-deep references/ file (e.g., references/retro-template.md), which would slim SKILL.md to its workflow; there is no well-signaled reference structure to reward with a 5.

4 / 5

Total

17

/

20

Passed

Description

61%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 is concise and domain-specific with good natural keywords (sprint, milestone, retrospective, velocity, blockers), but it is noun-heavy with no action verbs and lacks any "Use when..." trigger clause, capping completeness. Adding an explicit trigger (e.g., "Use when a sprint or milestone ends, or when the user mentions a retro or post-sprint review") would lift both completeness and specificity.

Suggestions

Add an explicit 'Use when...' clause naming trigger moments, e.g., "Use when a sprint or milestone ends, when the user asks for a retro/post-sprint review, or before planning the next iteration."

Convert the noun phrases into concrete third-person actions, e.g., "Generates sprint or milestone retrospectives by analyzing completed work, velocity, and blockers; produces prioritized action items for the next iteration."

Include common synonyms users say — "retro", "post-mortem", "what went well" — to broaden natural trigger coverage.

DimensionReasoningScore

Specificity

"Sprint or milestone retrospective from completed work, velocity, blockers" names the domain plus several concrete content areas (completed work, velocity, blockers, actionable insights), but contains no action verbs at all — the actions are only implied. It sits between anchor 3 (domain + 1-2 concrete actions) and anchor 4 (several specific actions); it is not comprehensive in describing actions, so 3 fits best.

3 / 5

Completeness

The "what" is clear (a retrospective built from completed work, velocity, and blockers producing actionable insights), but there is no "Use when..." clause or equivalent explicit trigger guidance — the "when" is only weakly implied by the sprint/milestone framing. Per the rubric guideline, a missing 'Use when...' clause caps completeness at 3; it is above anchor 2 because the what is specific, not vague.

3 / 5

Trigger Term Quality

"sprint", "milestone", "retrospective", "velocity", "blockers", "next iteration" are the natural terms users in an agile workflow would say. A few common variations are missing — "retro", "post-mortem", "what went well" — matching anchor 4 (good coverage, a few natural terms missing) rather than 5.

4 / 5

Distinctiveness Conflict Risk

"Retrospective" is a clear, distinctive niche trigger with low generic overlap. It earns 4 rather than 5 because the skill sits in a family of closely related planning skills (sprint-plan, sprint-status, gate-check referenced in the body) with which "sprint"-based phrasing could produce minor overlap, and the description lacks an explicit trigger clause that would fully separate it.

4 / 5

Total

14

/

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/retrospective/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.