CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

retro

Facilitate a structured sprint retrospective — what went well, what didn't, and prioritized action items with owners and deadlines. Use when running a retrospective, reflecting on a sprint, creating action items from team feedback, or learning how to run effective retros.

Quality

86%

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

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 a well-structured, actionable facilitation workflow that stays lean and assumes Claude's competence. Its main gaps are minor: a few restated format definitions that could be trimmed and no explicit confirmation/validation checkpoint before emitting the final summary.

Suggestions

Trim the per-format explanatory questions (Start/Stop/Continue, 4Ls, Sailboat bullets) to just the format names plus one distinguishing line, since Claude already knows these frameworks.

Add an explicit checkpoint before final output, e.g. 'Confirm the chosen format and collected items with the user before generating action items and the summary.'

DimensionReasoningScore

Conciseness

The body is efficient — a format menu, a one-row table spec, and a compact summary template with no concept over-explanation. Minor trimmable instances exist: the per-format bullet questions ("Start: What should we begin doing?") restate facilitation formats Claude already knows, keeping it just below anchor 5.

4 / 5

Actionability

Concrete guidance dominates: an exact action-item table schema (Priority/Action Item/Owner/Deadline/Success Metric), a copy-paste summary template, and hard limits ("Limit to 2-3 action items"). A few steps remain high-level ("Group similar items into themes"), so it is not fully copy-paste-ready like anchor 5.

4 / 5

Workflow Clarity

A clear 5-step numbered sequence (choose format → process feedback → analyze sprint → generate action items → create summary) with some checkpoints ("or let the user pick", carry-over status check). It lacks explicit validation/confirmation steps before producing the final summary, so it matches anchor 4 rather than 5; the destructive/batch cap does not apply.

4 / 5

Progressive Disclosure

This is a single-task, self-contained skill with no need for external references: content is short, well-organized into labeled sections, and easy to navigate. Per the simple-skill guidance, well-organized sections alone warrant a 5; nothing belongs in a separate file.

5 / 5

Total

17

/

20

Passed

Description

87%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 strong description: it states concrete capabilities in third person, includes an explicit and multi-trigger 'Use when...' clause, and occupies a distinct niche (sprint retrospectives). Only minor gains available from adding a few more natural synonyms.

DimensionReasoningScore

Specificity

"Facilitate a structured sprint retrospective", "what went well, what didn't", and "prioritized action items with owners and deadlines" name several concrete actions. Not 5 because coverage has minor gaps (no mention of sprint-performance analysis or output format); not 3 because it lists more than 1-2 specific actions.

4 / 5

Completeness

It explicitly answers both: what ("Facilitate a structured sprint retrospective — ... prioritized action items with owners and deadlines") and when ("Use when running a retrospective, reflecting on a sprint, creating action items from team feedback, or learning how to run effective retros") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Triggers include "running a retrospective", "reflecting on a sprint", "creating action items from team feedback", and "retros" — natural phrases users would say. A few natural synonyms are missing (e.g., "post-mortem", "team reflection"), so it falls just short of comprehensive anchor 5.

4 / 5

Distinctiveness Conflict Risk

"Sprint retrospective" is a clear niche with distinct, domain-specific triggers (retro, sprint reflection, action items from team feedback), minimizing conflict with unrelated skills. It matches anchor 5's pattern of a distinct niche with explicit triggers.

5 / 5

Total

18

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

phuryn/pm-skills

Path

pm-execution/skills/retro/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.