CtrlK
BlogDocsLog inGet started
Tessl Logo

retro

Reflect on recent work—capture learnings and surface what to think about next

58

Quality

66%

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 ./skills/retro/SKILL.md
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 lean, well-structured instruction skill with concrete actionable steps and a clear workflow including a memory health-check checkpoint. Its only real weakness is minor redundancy in the insight-capture guidance.

DimensionReasoningScore

Conciseness

The body is efficient and assumes Claude's competence, but the repeated guidance ("Extract insights, not summaries" then "Focus on _insights_, not a summary of actions taken") is a minor instance of over-explanation that could be trimmed, fitting anchor 4 rather than a lean 5.

4 / 5

Actionability

Gives concrete, actionable guidance throughout (numbered Memory Health Check steps, a copy-paste report template "MEMORY.md: [N] lines...", and specific bullet prompts), with only minor gaps in the more abstract retro sections; matches anchor 4 for an instruction-only skill.

4 / 5

Workflow Clarity

A clear sequence runs from insight capture to open threads to a memory health check to a user prompt and merge, with a validation checkpoint (the staleness/line-count scan); minor validation gaps in the merge step keep it at 4 rather than 5.

4 / 5

Progressive Disclosure

This is a simple, single-purpose skill under 50 lines with no need for external references, and its sections (Overview, What I Learned, What to Think About Next, Memory Health Check) are well-organized, so per the simple-skills scoring note it earns a 5.

5 / 5

Total

17

/

20

Passed

Description

53%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 conveys a clear purpose and niche but omits any "when to use" trigger guidance, which caps its completeness and trigger quality. It is reasonably specific yet leans on generic verbs rather than concrete, comprehensive actions.

Suggestions

Add an explicit "Use when..." trigger clause, e.g. "Use when wrapping up a session, before clearing context, or when the user asks for a retrospective."

Include the natural keyword "retrospective" so users who say that term reliably surface the skill.

Tighten verbs to more concrete actions (e.g. "extract 2-4 technical insights and list open threads") to lift specificity.

DimensionReasoningScore

Specificity

Names the domain (reflecting on recent work) and 2 concrete actions ("capture learnings" and "surface what to think about next"), but the actions are generic rather than comprehensive, matching anchor 3; not several specific actions so it is not a 4.

3 / 5

Completeness

Provides a clear "what" (reflect, capture learnings, surface next thoughts) but no "when"/trigger guidance, and the judging guidelines cap completeness at 3 when a "Use when" clause is missing.

3 / 5

Trigger Term Quality

Has some relevant natural terms ("reflect", "learnings", "think about next") but lacks common synonyms like "retrospective" and any explicit "Use when" trigger phrase, matching anchor 3; keyword coverage is not broad enough for a 4.

3 / 5

Distinctiveness Conflict Risk

The retrospective framing is a clear, mostly-distinct niche with only minor overlap risk against planning or memory skills, fitting anchor 4; lack of explicit triggers keeps it from a 5.

4 / 5

Total

13

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
tslateman/duet
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.