CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

retro

Run the retrospective over a window of the decision trace — answer eight fixed questions (tier calibration, review signal per sub-agent, recurring failures, diagnosis calibration, spend, chain health, aim calibration, stamp calibration) and turn what recurs into candidate tickets. It is the one skill that reads the trace, and it reads after the fact; it never fixes what it finds and never edits a skill. Use after a wave lands, before a release, or when a wave felt more expensive or more iterative than it should have.

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

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

An exceptionally actionable, well-sequenced operational skill: concrete commands, validation checkpoints, and error-recovery branches throughout the eight-step procedure. Its weaknesses are repetition of the same doctrinal justifications across four or five sections, and a half-finished split with QUESTIONS.md whose content is duplicated inline and which is missing from the bundle.

Suggestions

State the never-fix and rule-not-a-lessons-file doctrines once (e.g. in 'What this skill does not do') and cut their restatement in the intro, routing, anti-patterns, and footer — the same rule currently appears in up to four places.

Complete the QUESTIONS.md split: keep only the one-line question list and section summaries in SKILL.md, moving the detailed per-question specifications (especially questions 7 and 8, flow, before-and-after, and recurring-rulings) into QUESTIONS.md, and ship that file in the bundle.

Trim the inline `file_candidates` implementation to its invocation contract (inputs, outputs, the `file:`/`not filed:` behavior) and let the full function live beside the other project scripts it depends on.

DimensionReasoningScore

Conciseness

The body teaches nothing Claude already knows and is operationally dense, but its core doctrine is stated repeatedly — the never-fix rule appears in the intro ("it never fixes what it finds"), "What this skill does not do" ("A repair by the session that read the history destroys the only independent reading anyone had"), the anti-patterns ("Fixing anything..."), and the footer, and the "rule, not a lessons file" rule likewise recurs in four places. Mostly efficient, but several of these justificatory repeats could be tightened or stated once.

3 / 5

Actionability

Nearly every step carries copy-paste-ready commands: the `sh scripts/trace.sh export | awk ...` window pipeline, `sh scripts/trace.sh begin retro || :`, the full `emit`/`end` command templates with exact field syntax, the `gh issue list --state all --search ...` tracker query, and the complete `file_candidates`/`fc_block` shell implementations. Anchor 5 fits: fully executable guidance covering the common cases with placeholders clearly marked.

5 / 5

Workflow Clarity

The eight-step Procedure is clearly sequenced with explicit validation checkpoints and error recovery: verify-first with distinct exit-1 (damaged trace) and exit-3 (unsupported schema) branches, the open-retro listing before `begin`, the stop condition outside a repository, the `git check-ignore` check before writing the report, the tracker search before recording each finding, and the filing check before hand-off. This matches the anchor-5 pattern of explicit validation, feedback loops, and branching recovery paths, so the destructive/batch cap does not apply.

5 / 5

Progressive Disclosure

The body signals a one-level reference ("The full form — what to read, what counts as a finding, where it goes — is in `QUESTIONS.md`") yet inlines ~150 lines of the per-question, flow, before-and-after, and recurring-rulings specification that the reference supposedly holds, and no `QUESTIONS.md` exists in the bundle (references/, scripts/, assets/ are all absent). This matches anchor 3 — content that should be separate is inline with the reference present but the split only half-done — rather than 4, where placement gaps would be minor.

3 / 5

Total

16

/

20

Passed

Description

92%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 with all eight questions enumerated, an explicit use-when clause with three natural triggers, and an explicit distinctiveness claim. The only gap is missing natural synonyms for the trigger terms.

DimensionReasoningScore

Specificity

It lists multiple concrete actions with comprehensive coverage: "Run the retrospective over a window of the decision trace — answer eight fixed questions (tier calibration, review signal per sub-agent, recurring failures, diagnosis calibration, spend, chain health, aim calibration, stamp calibration) and turn what recurs into candidate tickets", plus explicit boundaries ("it never fixes what it finds and never edits a skill"). This matches anchor 5 rather than 4 because the action coverage has no notable gaps.

5 / 5

Completeness

Both halves are explicit: a clear what ("Run the retrospective over a window of the decision trace", the eight named questions, "turn what recurs into candidate tickets") and a concrete when-clause with three specific trigger conditions. This clearly matches anchor 5 — both what and when answered with concrete trigger phrases — rather than 4, where the when would be less explicit.

5 / 5

Trigger Term Quality

The when-clause gives natural, in-domain triggers — "Use after a wave lands, before a release, or when a wave felt more expensive or more iterative than it should have" — but common synonyms a user might say ("retro", "post-wave", "postmortem") are absent. Good coverage with a few natural terms missing fits anchor 4, not 5's comprehensive synonym coverage and not 3's missing variations.

4 / 5

Distinctiveness Conflict Risk

It claims an explicit niche — "It is the one skill that reads the trace, and it reads after the fact" — with triggers (after a wave lands, before a release, wave felt expensive) distinct from the sibling skills the body names (/to-tickets, /diagnose, /implement). Clear niche with distinct triggers and minimal conflict risk fits anchor 5.

5 / 5

Total

19

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

metadata_version

'metadata.version' is missing

Warning

referenced_paths_exist

Referenced path issues: 5 possibly missing (scripts/agents.config.sh, scripts/stamp.sh, scripts/trace.config.sh, scripts/trace.sh, scripts/vocab.sh)

Warning

Total

13

/

16

Passed

Repository

agranado2k/agentic-sdlc

Path

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