CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

72

Quality

88%

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

86%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 content is well-structured, actionable, and respects progressive disclosure by keeping the workflow inline and the principle catalog in referenced files. The main improvement room is adding explicit validation/feedback loops and trimming minor stylistic framing.

Suggestions

Add an explicit validation checkpoint in Phase 2/3 (e.g. confirm the diff is non-trivial and commit messages were actually read before moving to analysis) to strengthen workflow_clarity toward a 5.

Trim stylistic framing like 'Not a lecture -- a mirror. Show the user what their code already demonstrates.' to tighten conciseness.

Consider briefly noting what the two reference files contain at the point they are cited, so navigation intent is even clearer.

DimensionReasoningScore

Conciseness

The body is efficient and assumes Claude's competence (no padding about what git or SE principles are), with only minor stylistic framing ('Not a lecture -- a mirror') that could be trimmed, placing it just below the lean anchor.

4 / 5

Actionability

Provides copy-paste-ready git commands (e.g. 'git log main..HEAD --oneline'), a concrete scope-selection table, and a complete output template, covering the common cases fully.

5 / 5

Workflow Clarity

Phases 1-4 are clearly sequenced with conditional handling (large diffs use --stat first), but there are no explicit validate->fix->retry feedback loops; since the operations are read-only the destructive cap does not apply, so it sits at 'clear sequence, minor validation gaps'.

4 / 5

Progressive Disclosure

The body is a well-organized overview that offloads the principle catalog to clearly signaled, one-level-deep references (references/se-principles.md, references/anti-patterns.md), both of which exist as real files.

5 / 5

Total

18

/

20

Passed

Description

90%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 is strong: it states a clear purpose, uses third-person imperative voice, and provides rich natural trigger phrases that answer both 'what' and 'when'. The only mild gap is capability specificity, which lists two actions rather than a comprehensive set.

DimensionReasoningScore

Specificity

Names the domain ('recent code changes via git history') and two concrete actions ('Analyze', 'extract software engineering lessons'), but does not list several specific actions, so it sits at the 1-2 concrete actions anchor rather than the 'several specific actions' anchor above.

3 / 5

Completeness

Explicitly answers 'what' ('Analyze recent code changes via git history and extract software engineering lessons') and 'when' ('Use when the user asks...') with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

Lists multiple natural phrases users would actually say ('what is the lesson here?', 'what can I learn from this?', 'engineering takeaway', 'what did I just learn?', 'reflect on this code'), giving comprehensive synonym-level trigger coverage.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (extracting engineering lessons from git history) with distinct, specific triggers and minimal overlap risk with other skills.

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
softaworks/agent-toolkit
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.