CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

68

Quality

85%

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

75%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 an efficient, actionable facilitation guide with a clear sequenced workflow and reusable templates. It avoids over-explanation and is well-structured for a single-file skill.

DimensionReasoningScore

Conciseness

The body is lean and avoids explaining concepts Claude already knows, using compact format definitions and templates; a small amount of templated placeholder text could be trimmed, placing it just below the top 'every token earns its place' anchor.

4 / 5

Actionability

Provides concrete, copy-paste-ready templates (the action-items table with defined columns and the markdown summary scaffold) plus specific constraints (limit to 2-3 items, each specific/assignable/measurable), with only minor gaps versus fully worked examples.

4 / 5

Workflow Clarity

A clear five-step sequence runs from format selection through summary creation; because retrospective facilitation is not a destructive or batch operation, the absence of explicit validation checkpoints does not trigger the 3-cap, though none are present to reach 5.

4 / 5

Progressive Disclosure

Content is organized into well-labeled sections (Context, Instructions, formats, templates) in a single file with no external bundle files needed; at ~76 lines it slightly exceeds the under-50-line simple-skill threshold that would allow a 5, leaving minor organization headroom.

4 / 5

Total

16

/

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.

The description is well-crafted: third-person voice, explicit what-and-when structure, and natural trigger terms including the "retros" synonym. It is specific and distinct with little conflict risk.

DimensionReasoningScore

Specificity

Names the domain and several concrete elements ("what went well, what didn't, and prioritized action items with owners and deadlines") but stops short of an exhaustive list of actions, fitting the 'several specific actions; minor gaps' anchor rather than the comprehensive 5.

4 / 5

Completeness

Explicitly states both what it does ("Facilitate a structured sprint retrospective... prioritized action items with owners and deadlines") and when to use it ("Use when running a retrospective, reflecting on a sprint, creating action items..."), with concrete trigger phrases matching the top anchor.

5 / 5

Trigger Term Quality

Covers natural terms users would say ("retrospective", "sprint", "action items", "team feedback") plus the synonym "retros", but is missing a few common variations, matching the 'good keyword coverage; a few natural terms missing' anchor.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (sprint retrospectives) with distinct triggers and minimal overlap risk with other skills, matching the 'clear niche with distinct triggers' anchor.

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