Capture a correction or lesson as a persistent learning rule with category, mistake, and correction. Use after mistakes or when the user says "remember this".
92
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Capture a lesson from the current session into permanent memory.
Use when the user says "remember this", "add to rules", "don't do that again", or after a mistake is identified.
[LEARN] Category: One-line rule
Mistake: What went wrong
Correction: How it was fixed| Category | Examples |
|---|---|
| Navigation | File paths, finding code, wrong file edited |
| Editing | Code changes, patterns, wrong approach |
| Testing | Test approaches, coverage gaps, flaky tests |
| Git | Commits, branches, merge issues |
| Quality | Lint, types, style violations |
| Context | When to clarify, missing requirements |
| Architecture | Design decisions, wrong abstractions |
| Performance | Optimization, O(n^2) loops, memory |
Recent mistake: Edited wrong utils.ts file
[LEARN] Navigation: Confirm full path when multiple files share a name.
Add to LEARNED section? (y/n)[LEARN] rule with categoryaad0763
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.