CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

self-improvement

Captures learnings, errors, corrections, and feature requests to enable continuous improvement. Use when: (1) User corrects Claude ('No, that's wrong...', 'Actually...'), (2) User requests a capability that doesn't exist, (3) Claude realizes its knowledge is outdated or incorrect, (4) A better approach is discovered for a recurring task, (5) Receiving a Handoff block from self-healing (a recurring verified heal with Recurrence-Count at least 3) to distill into a memory file or new skill. For ACTIVE runtime failures where the agent needs to apply and verify a fix mid-task, use `self-healing` instead (it files HEAL- entries with proof; self-improvement promotes accumulated patterns). Also review learnings before major tasks. For CI-only/headless learning capture, use self-improvement-ci.

0.89x
Quality

86%

Does it follow best practices?

Impact

84%

0.89x

1 of 3 eval scenarios. Add 2 more for a full score.

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

81%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 body is highly actionable with strong validated workflows — human-approval gates on promotion, verification steps on extraction, and copy-paste templates for every entry type. Its main weakness is token efficiency: the inlined templates duplicate existing assets/ files, and a few sections restate general agent behavior. The orphaned references/examples.md is the only navigation gap in otherwise clean one-level-deep disclosure.

Suggestions

Replace the three inlined entry templates (Learning/Error/Feature Request, ~100 lines) with a brief field summary and a pointer to assets/LEARNINGS.md, assets/ERRORS.md, and assets/FEATURE_REQUESTS.md, which already contain the full templates.

Link references/examples.md from the Logging Format section so the 383-line worked-example file is discoverable.

Trim 'Multi-Agent Support' and 'Copilot Chat Integration' to one or two lines each — they largely restate when to log, which the Detection Triggers section already covers.

DimensionReasoningScore

Conciseness

The 507-line body inlines ~100 lines of full entry templates that duplicate assets/LEARNINGS.md, ERRORS.md, and FEATURE_REQUESTS.md, and sections like 'Multi-Agent Support' and 'Copilot Chat Integration' restate what the agent already knows. Mostly operational rather than padded, but clearly could be tightened.

3 / 5

Actionability

Fully executable throughout: copy-paste markdown entry templates, concrete bash (`mkdir -p .learnings`, grep status checks, `./skills/self-improvement/scripts/extract-skill.sh skill-name --dry-run`), an explicit ID format with examples, and a worked verbose-to-concise promotion example. Common cases are covered end to end.

5 / 5

Workflow Clarity

Multi-step processes carry explicit validation checkpoints and feedback loops: promotion requires 'Show the proposed diff for human approval before writing instructions' and 'Do not mark an unapplied proposal as promoted'; extraction ends with 'Verify: Read skill in fresh session'; skill edits require 'explicit scoped approval'; plus a quality-gate checklist before extraction.

5 / 5

Progressive Disclosure

References are one level deep, real, and well signaled ('Read these only when installing or configuring the skill' for installation.md/hooks-setup.md/amp-setup.md; context-maintenance.md linked at each relevant point). However, references/examples.md is never linked from the body (orphaned, hurting discovery) and the full entry templates inlined in the body duplicate the assets/ templates that belong in separate files.

4 / 5

Total

17

/

20

Passed

Description

87%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 dense but earns its length: it defines concrete capture targets, five explicit numbered triggers with natural user phrasing, and clean disambiguation from self-healing and self-improvement-ci. Third-person voice is maintained and no clause is pure padding. Weaknesses are limited: unstated storage mechanics and some jargon-heavy trigger terms (Recurrence-Count, Handoff block).

DimensionReasoningScore

Specificity

Names the domain and several concrete capture targets — 'Captures learnings, errors, corrections, and feature requests' plus 'distill into a memory file or new skill' — but the mechanics (logging to .learnings/ markdown files) are not stated, leaving minor gaps versus the comprehensive anchor.

4 / 5

Completeness

Explicitly answers both what ('Captures learnings, errors, corrections, and feature requests') and when, via a numbered 'Use when:' list of five concrete triggers plus supplementary cadence ('Also review learnings before major tasks') — matching the top anchor's what+when with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural quoted correction phrases users actually say ('No, that's wrong...', 'Actually...') and 'User requests a capability that doesn't exist', but omits common variations for feature requests and knowledge gaps (e.g., 'I wish you could', 'that's outdated') and leans on jargon like 'Handoff block' and 'Recurrence-Count'.

4 / 5

Distinctiveness Conflict Risk

Actively disambiguates the two nearest siblings ('For ACTIVE runtime failures... use `self-healing` instead'; 'For CI-only/headless learning capture, use self-improvement-ci'), carving a clear niche with minimal conflict risk.

5 / 5

Total

18

/

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.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (508 lines); consider splitting into references/ and linking

Warning

relative_links

Relative link issues: 1 suspicious

Warning

Total

14

/

16

Passed

Repository

pskoett/pskoett-ai-skills

Path

skills/self-improvement/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.