CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

common-session-retrospective

Review session corrections, trigger misses and recurring agent mistakes to propose targeted skill-library changes. Use for retrospective, rework or routing-gap analysis before registry edits; load +common/common-learning-log for redacted evidence.

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

The canonical home for this skill is common-session-retrospective in HoangNguyen0403/agent-skills-standard

SKILL.md
Quality
Evals
Security

Quality

Content

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

A well-structured instruction skill: a clearly sequenced protocol with real validation gates and rollback loops, concrete mechanisms and commands, and clean one-level-deep progressive disclosure into two verified reference files. The only weaknesses are mild — some duplicated links, run-on compound steps, and a few procedural steps lacking source specifics.

Suggestions

Consolidate the duplicated reference links (inline in 'Local preparation' vs. the 'References' section) into one location to save tokens.

Split the run-on Protocol steps 4, 7 and 8 into short sub-bullets so each rule is scannable rather than packed into one sentence.

Specify where correction signals are scanned from (e.g. transcript, learning log, review comments) to make the Extract step fully executable.

DimensionReasoningScore

Conciseness

The body is dense and protocol-style with no explanations of concepts Claude already knows, but reference links are duplicated (inline in 'Local preparation' and again in 'References'), Protocol steps 4/7/8 cram multiple rules into single run-on sentences, and the 'Canonical response anchors' section adds marginal value — minor trims, matching anchor 4 rather than the fully lean anchor 5.

4 / 5

Actionability

Guidance is concrete and executable for an instruction-only skill: an 8-label root-cause taxonomy, explicit improvement-item fields ('root cause, owner, chosen mechanism, verification/eval reference, adoption status'), a failure-shape-to-mechanism-to-verification table, and real commands (get_session_cost, prepare_retrospective, 'ags retrospective enable'). It stops short of anchor 5 because a few steps remain procedural, e.g. 'Scan for correction signals' does not specify which sources to scan.

4 / 5

Workflow Clarity

The 8-step Protocol is clearly sequenced (Extract, Classify, Trigger Miss Check, Propose, Authorize, Evaluate, Review and promote, Log and report) with explicit validation checkpoints — held-out evaluation in step 6 and independent approval plus fresh eval evidence in step 7 — and feedback/rollback loops ('Pin approved versions, monitor regressions, revert to last verified version'), matching anchor 5.

5 / 5

Progressive Disclosure

SKILL.md serves as a clear overview with a Structure tree, and both referenced files exist one level deep with well-labeled links ('Signal tables, taxonomy, report template'; 'Local preparation disposition, coverage, trigger, boundaries') including a working heading anchor (#trigger-miss-record resolves to the 'Trigger miss record' section in methodology.md) — matching anchor 5.

5 / 5

Total

18

/

20

Passed

Description

83%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: concrete actions, explicit 'Use for' trigger guidance, and a clearly distinguishable niche. It falls just short of top marks on specificity and trigger coverage because supporting actions (evaluate, log, report) and common synonyms like 'session review' are absent.

Suggestions

Add one or two natural trigger synonyms such as 'session review' or 'post-mortem' to broaden when-clause coverage.

Briefly acknowledge the downstream actions (evaluation and reporting of proposed changes) to make capability coverage more comprehensive.

DimensionReasoningScore

Specificity

Names the domain plus several concrete actions — 'Review session corrections, trigger misses and recurring agent mistakes to propose targeted skill-library changes' — but coverage stops at review/propose, leaving evaluation and reporting actions unmentioned, which keeps it below the comprehensive anchor 5.

4 / 5

Completeness

Both parts are explicit: the 'what' is the concrete action list ('Review session corrections, trigger misses and recurring agent mistakes...') and the 'when' is a concrete 'Use for' clause naming retrospective, rework and routing-gap analysis — matching the anchor-5 pattern of clearly answering both with trigger phrases.

5 / 5

Trigger Term Quality

'Use for retrospective, rework or routing-gap analysis' supplies good natural terms, though 'routing-gap analysis' leans technical and common variations like 'session review' or 'post-mortem' are missing, so it does not reach the comprehensive synonym coverage of anchor 5.

4 / 5

Distinctiveness Conflict Risk

The skill occupies a clear niche (session retrospective / skill-library maintenance) with distinct triggers ('retrospective', 'routing-gap'), but 'rework' alone could overlap with general review/refactoring skills, giving minor rather than minimal conflict risk.

4 / 5

Total

17

/

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

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

13

/

16

Passed

Repository

HoangNguyen0403/agent-skills-standard

Path

.agents/skills/common/common-session-retrospective/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.