sprint-retrospective
Facilitate effective sprint retrospectives for continuous team improvement. Use when conducting team retrospectives, identifying improvements, or fostering team collaboration. Handles retrospective formats, action items, and facilitation techniques.
80
70%
Does it follow best practices?
Impact
100%
1.12xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.agent-skills/sprint-retrospective/SKILL.mdQuality
Discovery
75%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 is a reasonably well-structured skill description that follows the recommended format with an explicit 'Use when...' clause. Its main strengths are completeness and distinctiveness, clearly carving out the retrospective facilitation niche. However, it could be improved with more specific concrete actions and additional natural trigger terms users commonly use when requesting retrospective help.
Suggestions
Add more specific concrete actions like 'create Start/Stop/Continue boards, generate action item templates, structure 4Ls retrospectives, track improvement metrics'
Include common user variations in trigger terms such as 'retro', 'sprint review', 'what went well/wrong', 'lessons learned', 'agile ceremonies', 'team feedback session'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (sprint retrospectives) and mentions some actions like 'conducting team retrospectives, identifying improvements' and 'handles retrospective formats, action items, and facilitation techniques', but these are somewhat general categories rather than concrete specific actions like 'create Start/Stop/Continue boards' or 'generate action item templates'. | 2 / 3 |
Completeness | Clearly answers both what ('Facilitate effective sprint retrospectives for continuous team improvement. Handles retrospective formats, action items, and facilitation techniques') and when ('Use when conducting team retrospectives, identifying improvements, or fostering team collaboration') with an explicit 'Use when...' clause. | 3 / 3 |
Trigger Term Quality | Includes relevant terms like 'sprint retrospectives', 'team retrospectives', 'improvements', 'team collaboration', 'action items', and 'facilitation'. However, missing common variations users might say like 'retro', 'sprint review', 'what went well', 'lessons learned', or 'agile ceremonies'. | 2 / 3 |
Distinctiveness Conflict Risk | Has a clear niche focused specifically on sprint retrospectives and agile team improvement processes. The combination of 'retrospective', 'sprint', 'facilitation techniques', and 'action items' creates distinct triggers unlikely to conflict with general meeting or project management skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides solid, actionable retrospective templates with concrete examples that Claude can immediately use. However, the structure is misleading (steps imply sequence when they're alternatives), includes unnecessary metadata/empty sections, and lacks facilitation workflow guidance for actually running a retrospective session.
Suggestions
Rename 'Step 1/2/3' to 'Format Option 1/2/3' or similar to clarify these are alternatives, not sequential steps
Remove empty example placeholders and the metadata section which add no actionable value
Add brief guidance on when to choose each format (e.g., 'Use Mad-Sad-Glad when team morale is a concern')
Include a facilitation workflow showing how to actually run the session (intro → individual reflection → group discussion → voting → action items)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes useful templates but has some unnecessary padding like the metadata section, empty example placeholders, and references that don't add actionable value. The core templates are reasonably efficient but could be tighter. | 2 / 3 |
Actionability | Provides concrete, copy-paste ready markdown templates for three different retrospective formats with specific examples of items in each category. Action items include assignees and deadlines, making them immediately usable. | 3 / 3 |
Workflow Clarity | The steps present three different formats but don't explain when to choose each or how they sequence together. The 'Step 1, 2, 3' labeling is misleading since these are alternative formats, not sequential steps. Missing guidance on facilitation flow. | 2 / 3 |
Progressive Disclosure | Content is reasonably organized with clear sections, but includes empty example placeholders and a metadata section that adds no value. External references are provided but the skill is somewhat monolithic with all three formats inline rather than referenced. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
Total | 10 / 11 Passed | |
- Repository
- supercent-io/skills-template
- Commit
c033769
- 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.