CtrlK
BlogDocsLog inGet started
Tessl Logo

common-session-retrospective

Analyze conversation corrections to detect skill gaps and prepare targeted skill-library maintenance tasks. Use after any session with user corrections, rework, or retrospective requests. After finding correction loops, also load +common/common-learning-log to persist mistake entries to AGENTS_LEARNING.md.

67

Quality

81%

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

80%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 concise, well-structured protocol skill that delegates detail to a single real reference file. Its main weakness is the lack of an explicit validation checkpoint in the workflow for the batch repository-maintenance step.

Suggestions

Add an explicit validation/verification step between Implement (step 5) and Report (step 7), e.g. 'Verify: confirm no duplicate skills, AGENTS.md index updated, and SKILL.md stays <=70 lines' to lift workflow_clarity above the batch-operation cap of 3.

Reference the existing Implementation Checklist from methodology.md inline at the Implement step so verification is part of the main protocol rather than only in the referenced file.

For the Report step, specify the concrete output location or format expected (the methodology.md report template) so the final deliverable is unambiguous.

DimensionReasoningScore

Conciseness

Lean and well-organized with no padding and no explanation of concepts Claude already knows; every section and line earns its place.

5 / 5

Actionability

Concrete, specific guidance throughout (explicit 7-step protocol, schema reference, directives like 'append one entry using common/common-learning-log protocol'), with minor gaps in copy-paste-ready specifics for the implementation step which defers to other skills by design.

4 / 5

Workflow Clarity

A clear 7-step sequence exists, but the Implement step performs batch repository changes across multiple agent dirs with no inline validation/verification checkpoint before reporting, triggering the rubric's workflow_clarity cap of 3 for batch operations missing validation.

3 / 5

Progressive Disclosure

Clear overview with well-signaled one-level-deep references to references/methodology.md (verified to exist), with large tables and schema appropriately split out into the reference file.

5 / 5

Total

17

/

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 well-crafted description that clearly conveys both the skill's purpose and its trigger conditions in third-person voice. It is specific and actionable with only minor room for added synonyms and broader coverage.

DimensionReasoningScore

Specificity

Names several concrete actions ('Analyze conversation corrections to detect skill gaps', 'prepare targeted skill-library maintenance tasks', 'load +common/common-learning-log to persist mistake entries') with minor gaps in coverage rather than a comprehensive list.

4 / 5

Completeness

Explicitly answers both 'what' (analyze corrections, detect gaps, prepare maintenance tasks) and 'when' ('Use after any session with user corrections, rework, or retrospective requests') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural terms users would say ('user corrections, rework, or retrospective requests') with good coverage, though a few common synonyms like 'feedback' or 'what went wrong' are missing.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (session retrospectives, skill-library maintenance) with distinct triggers, with only minor overlap risk against a generic learning-log skill.

4 / 5

Total

17

/

20

Passed

Validation

87%

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

Validation14 / 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

Total

14

/

16

Passed

Repository
HoangNguyen0403/agent-skills-standard
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.