CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

lesson-learned

Analyze recent code changes via git history and extract software engineering lessons. Use when the user asks 'what is the lesson here?', 'what can I learn from this?', 'engineering takeaway', 'what did I just learn?', 'reflect on this code', or wants to extract principles from recent work.

Quality

93%

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

92%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, highly actionable skill body: concrete git commands with explicit defaults, a hard gating checkpoint on loading references, a complete output template, edge-case handling for large diffs and trivial changes, and correctly externalized one-level-deep reference files. The only weakness is mild duplication between the phase instructions, the What-NOT-to-Do table, and the Conversation Style section.

Suggestions

Deduplicate repeated guidance: the commit-messages-contain-intent point appears in both Phase 2 and the What-NOT table, and 'be specific / avoid abstract advice' appears in both Conversation Style and the What-NOT table — keep each in one place to trim tokens.

Drop the stylistic framing ('Not a lecture -- a mirror. Show the user what their code already demonstrates') and fold its intent into the Phase 3 or Conversation Style bullet, since the body already demonstrates reflective tone through its instructions.

Consider merging the 'Conversation Style' bullets that restate What-NOT table rows (e.g., specificity and leading with positives) into a single guidance section to reduce redundancy.

DimensionReasoningScore

Conciseness

The body is efficient — tables for scope and anti-patterns, a copy-paste output template, no explanation of git or SE basics Claude already knows. It stays at 4 rather than 5 because a few points are stated twice: commit messages 'contain intent that raw diffs miss' appears in both Phase 2 and the What-NOT table, and 'Be specific / abstract advice is worthless' is duplicated in Conversation Style and the What-NOT table; the framing line 'Not a lecture -- a mirror' is disposable flavor. It is clearly above the 'mostly efficient but some unnecessary explanation' midpoint because the padding is duplication, not concept explanation.

4 / 5

Actionability

Concrete, copy-paste-ready git commands cover the common cases ('git log main..HEAD --oneline', 'git diff main...HEAD', 'git show <sha>', 'git diff --cached'), with explicit defaults (N=5, feature-branch vs main behavior) and a fill-in output template with per-field sentence counts. This matches the 'fully executable; specific examples cover the common cases' anchor — an instruction-only skill whose guidance is entirely actionable.

5 / 5

Workflow Clarity

A clear four-phase sequence (load references → determine scope → gather → analyze → present) with explicit checkpoints: 'Do not proceed until you've loaded at least se-principles.md' is a hard gate, Phase 1 resolves scope ambiguity with a decision table plus defaults, Phase 2 has a conditional for large diffs (>500 lines → --stat, read top 3-5 files), and the What-NOT-to-Do table plus the trivial-changes escape hatch ('no deep lesson here, just good housekeeping') act as checklists and error-avoidance guidance. No destructive or batch operations exist, so no feedback loop is required; the sequence is unambiguous.

5 / 5

Progressive Disclosure

The SKILL.md body is a workflow overview, and the catalog content is correctly externalized: 'Read references/se-principles.md to have the principle catalog available' and 'Optionally read references/anti-patterns.md' — both verified to exist, one level deep, no nested references inside them, and the optional file is clearly signaled as conditional. This matches the 'clear overview with well-signaled one-level-deep references; content appropriately split' anchor.

5 / 5

Total

19

/

20

Passed

Description

91%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 a clear what (analyze git history, extract SE lessons), an explicit 'Use when' clause with six realistic verbatim trigger phrases, and uses third-person imperative voice throughout. Minor overlap risk with code-review skills and only two named actions keep it just short of top marks on specificity and distinctiveness.

DimensionReasoningScore

Specificity

Quotes: 'Analyze recent code changes via git history' and 'extract software engineering lessons' — two concrete actions with an explicit mechanism (git history), matching the 'several specific actions; minor gaps' anchor. Not a 5 because coverage stops at two actions and doesn't hint at the output form (e.g., mapped principles), and not a 3 because the named mechanism and output object are more specific than 'domain plus 1-2 generic actions'.

4 / 5

Completeness

The 'what' is explicit ('Analyze recent code changes via git history and extract software engineering lessons') and the 'when' is an explicit 'Use when' clause with concrete trigger phrases, exactly matching the anchor for clearly answering both what AND when. Neither half is vague or merely implied.

5 / 5

Trigger Term Quality

Quotes: 'what is the lesson here?', 'what can I learn from this?', 'engineering takeaway', 'what did I just learn?', 'reflect on this code' — six natural verbatim phrases a user would actually say, plus the broader 'wants to extract principles from recent work'. This matches the 'comprehensive coverage of natural terms including synonyms' anchor; nothing common is missing.

5 / 5

Distinctiveness Conflict Risk

Quotes: 'extract software engineering lessons' and 'reflect on this code' — a fairly clear niche (retrospective learning from git history) with distinct triggers. Not a 5 because 'reflect on this code' and lesson-extraction phrasing could overlap with code-review or retrospective-type skills; mostly distinct with minor overlap risk against closely related review skills.

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

softaworks/agent-toolkit

Path

skills/lesson-learned/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.