continuous-learning
/continuous-learning
Turn a hard-won, multi-step procedure from the current session into its own small skill at ~/.claude/skills/learned-<slug>/SKILL.md, so future sessions load it when the same trigger shows up again (an exact error, a tool limitation, a recurring debugging situation, a multi-step project task). On demand only: use when the user says "save what we learned", "make this a pattern", "remember how we fixed this", or runs /continuous-learning; offer it at the natural end of a long session. One-line facts, preferences and corrections belong in Claude Code's auto-memory, not here. Keeps at most 20 learn
- Author
- mhylle ↗
- Repository
- claude-skills-collection ↗
- Licence
- MIT
- Last repository change
- 13.10.2026
Assessment and security
- Files in this package
- 4
- Scripts
- 0
- HTML comments
- 2
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 13.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
- SKILL.md zawiera komentarze HTML (2). Nie widać ich w podglądzie Markdown, a model je czyta.
What it does and when to use it
Turn a hard-won, multi-step procedure from the current session into its own small skill at ~/.claude/skills/learned-<slug>/SKILL.md, so future sessions load it when the same trigger shows up again (an exact error, a tool limitation, a recurring debugging situation, a multi-step project task). On demand only: use when the user says "save what we learned", "make this a pattern", "remember how we fixed this", or runs /continuous-learning; offer it at the natural end of a long session. One-line facts, preferences and corrections belong in Claude Code's auto-memory, not here. Keeps at most 20 learn
Triggers from the description
Original author description
Turn a hard-won, multi-step procedure from the current session into its own small skill at ~/.claude/skills/learned-<slug>/SKILL.md, so future sessions load it when the same trigger shows up again (an exact error, a tool limitation, a recurring debugging situation, a multi-step project task). On demand only: use when the user says "save what we learned", "make this a pattern", "remember how we fixed this", or runs /continuous-learning; offer it at the natural end of a long session. One-line facts, preferences and corrections belong in Claude Code's auto-memory, not here. Keeps at most 20 learn
How it works
- Contents
- Scope — auto-memory or learned skill?
- When to run
- Pattern types
- Workflow
- Writing a good learned skill
- References (loaded on demand)
SKILL.md preview
---
name: continuous-learning
description: >-
Turn a hard-won, multi-step procedure from the current session into its own small
skill at ~/.claude/skills/learned-<slug>/SKILL.md, so future sessions load it when the
same trigger shows up again (an exact error, a tool limitation, a recurring debugging
situation, a multi-step project task). On demand only: use when the user says "save
what we learned", "make this a pattern", "remember how we fixed this", or runs
/continuous-learning; offer it at the natural end of a long session. One-line facts,
preferences and corrections belong in Claude Code's auto-memory, not here. Keeps at
most 20 learned skills, updating or retiring existing ones instead of adding
near-duplicates.
---
# Continuous Learning
<!-- contents: generated by tests/skill_structure.py --write; edit headings, not this block -->
## Contents
- [Scope — auto-memory or learned skill?](#scope--auto-memory-or-learned-skill)
- [When to run](#when-to-run)
- [Pattern types](#pattern-types)
- [Workflow](#workflow)
- [Step 1 — Find candidates](#step-1--find-candidates)
- [Step 2 — Apply the bar](#step-2--apply-the-bar)
- [Step 3 — Check existing learned skills](#step-3--check-existing-learned-skills)
- [Step 4 — Confirm and write](#step-4--confirm-and-write)
- [Step 5 — Report](#step-5--report)
- [Writing a good learned skill](#writing-a-good-learned-skill)
- [References (loaded on demand)](#references-loaded-on-demand)
Reference files (open one when a step points to it):
- `references/examples.md`: Example learned skills
- `references/pattern-types.md`: Pattern types — criteria and body sections
- `references/storage-format.md`: Storage format
<!-- /contents -->
Promote a reusable problem-solving procedure from this session into a standalone skill that Claude Code discovers by itself. Each learned skill lives at `~/.claude/skills/learned-<slug>/SKILL.md`; its description appears in every future session's skill listing, so the model loads the body when the trigger shows up again.
---
## Scope — auto-memory or learned skill?
Claude Code's auto-memory (`~/.claude/projects/<project>/memory/`) already records preferences, corrections, project facts and pointers, one line each, and loads them into later sessions. This skill does not duplicate it.
| The learning... | Goes to |
|---|---|
| Fits in one memory line — a preference, a fact, a correction ("don't mock the database in integration tests", "this repo uses named exports") | Auto-memory. No skill. |
| Is a multi-step procedure with a recognisable trigger — an exact error message, a named tool limitation, a symptom pattern, a named project task | A learned skill (this workflow) |
When a candidate turns out to be a one-liner, say it belongs in memory and move on.
---
## When to run
Only when invoked; nothing triggers this skill automatically.
- The user asks: "save what we learned", "make this a pattern", "remember how we fixed this", "extract learnings from this session", or `/continuous-learning`.
- Another skill calls it at a natural boundary (`implement-phase` and `tt-implement-phase` do at phase completion).
- At the natural end of a long session in which a hard problem was solved, offer it in one line ("Want me to save the Prisma-in-CI fix as a learned skill?") and run it only if the user agrees.
There is no hook for this skill. A Stop hook fires after every response rather than once at session end, and a hook cannot run a skill, so a hook-driven version would fire on every turn or not at all.
---
## Pattern types
Four types qualify. Per-type criteria and body sections → `references/pattern-types.md`. Complete examples → `references/examples.md`.
1. **Error resolution** — a non-obvious fix for a specific error. Trigger: the exact error text.
2. **Workaround** — a way around a tool, framework or environment limitation. Includes when it becomes unnecessary.
3. **Debugging technique** — a repeatable investigation sequence for a recognisable problem class.
4. **Project procedure** — a multi-step task specific to one codebase (release, migration, client regeneration). The description names the project.
User corrections and single-rule conventions are not a type here; they go to auto-memory.
---
## Workflow
### Step 1 — Find candidates
Scan the session for:
- Errors that took more than one attempt to fix, and the root cause that was found.
- "Can't do X, so we did Y" moments.
- Investigation sequences that located a non-obvious cause.
- Multi-step project tasks the user had to explain or that were worked out by trial.
### Step 2 — Apply the bar
Promote a candidate only if all of these hold:
- It is a procedure (two or more steps), not a single rule.
- The trigger is concrete enough to recognise later — an error string, a tool and version, a symptom, a project and task name.
- The fix was not the first result in the official docs.
- The root cause or limitation is understood, not just the symptom silenced.
- It is likely to come up again, in this project or others.
Never save credentials, tokens, keys, passwords or personal data; use placeholders in any example.
Create or update at most 3 learned skills per run — pick the strongest candidates.
### Step 3 — Check existing learned skills
Glob `~/.claude/skills/learned-*/SKILL.md` and read each description.
- Same trigger or same root cause as an existing learned skill → update that skill (extend the fix, add an Evidence line, sharpen the description) instead of creating a near-duplicate.
- Related but with a different trigger → a new skill is fine; if the two would load in the same situations, merge them instead.
**Cap: 20 learned skills.** Every learned skill's description sits in the always-loaded skill listing, so the set has to stay small. If a new skill would take the count past 20, first propose merging two related skills or retiring one (its "Retire when" condition is met, the tool or version is gone, it never applied again), and add the new one only after a slot is free.
### Step 4 — Confirm and write
Show the user the planned changes: for each, `learned-<slug>`, whether it is new / updated / merged / retired, and its description. Write after they confirm — these files load into every future session.
If no one can confirm — you were called by another skill running as a forked or background subagent, so `AskUserQuestion` is not in your tool list — write nothing. Return the planned changes as `PROPOSED LEARNED SKILLS` (one line each, as above) so the caller can show them to the user and re-run this skill to write the approved ones.
Each learned skill is a `SKILL.md` with frontmatter `name: learned-<slug>` and a trigger-specific `description` of at most 300 characters, then a short body: trigger, pattern, fix, evidence, dates. Exact layout and frontmatter rules → `references/storage-format.md`. Retiring a skill means deleting its `learned-<slug>/` directory. New or changed skills are available from the next session on.
### Step 5 — Report
Report only what happened in this run:
```
Continuous learning
Created: learned-prisma-client-not-generated — PrismaClientInitializationError after a schema change in Docker/CI
Updated: learned-jest-esm-json-imports — added evidence line 2026-10-06
Retired: none
Left to auto-memory: "acme-frontend colocates tests next to source files"
Skipped: generic TypeScript null-check error — first result in the docs
Learned skills: 7 / 20
```
If nothing qualified, say so in one line.
---
## Writing a good learned skill
- **Description:** start with "Use when", name the trigger concretely (exact error text in quotes, tool and version, project name), then the fix in a few words. Leave out generic words ("debugging", "errors", "best practices") that would make it load for unrelated work.
- **Body:** fits on one screen; steps a future session can follow without this conversation.
- **Evidence:** dated, observable facts only — where it happened (repo), what was seen, what confirmed the fix (tests passed, command succeeded). No estimates of time saved or success rates.
- **Retire when:** the condition that makes the skill obsolete (upstream fix, version bump, migration finished).
When a run touches the set, also check for learned skills whose "Retire when" condition is now met and for pairs with overlapping triggers; include those retirements and merges in the Step 4 proposal.
---
## References (loaded on demand)
- `references/pattern-types.md` — per-type criteria and body sections
- `references/storage-format.md` — location, naming, frontmatter rules, body layout, updating, merging, retiring
- `references/examples.md` — one complete learned skill per type, plus examples that belong in auto-memory instead
Files in this package (4)
- SKILL.md 9 KB
- references/examples.md 7 KB
- references/pattern-types.md 3 KB
- references/storage-format.md 3 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · mhylle/claude-skills-collection | 100 | MIT |
| ericrisco/rsc-harness | 100 | MIT |
| tadokoro-ryusuke/cc-plugins | 100 | MIT |
| ckorhonen/claude-skills | 100 | MIT |
| affaan-m/ECC | 96 | MIT |
| affaan-m/ECC | 96 | MIT |
| aaione/everything-claude-code-zh | 96 | MIT |
| mturac/everything-openai-codex | 96 | MIT |
| mturac/everything-openai-codex | 96 | MIT |
Database snapshot: 13.11.2026 · package version 85927d607c73 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100self-learning
Capture a hard-won "golden path" from the current session as a reusable Agent Skill, so future sessions start already knowing it. Use it (1) right after non-trivial debugging, after working out a multi-step operational workflow, or after rediscovering project facts you didn't… - 100cc-skill-continuous-learning
Turn a completed debugging session or repeated user correction into a small, evidence-backed procedure. Use for explicit requests to capture reusable lessons; does not automatically extract or save memories. - 100session-learning
This skill should be used when the user asks about "session learning", "learn from session", "improve future sessions", "session reflection", "session metrics", "session analysis", "/session-reflect", "req learning", "learning updates", "rollback learning", or wants to… - 90skill-forge
Promote a procedure that was worked out end-to-end and verified into a reusable skill file, so the next similar task starts from the solved path. Use when a hard-won procedure succeeds with evidence, when the same multi-step task appears a second time, or when the user says "make this repeatable". - 100learned
Extract and persist learnings, corrections, and patterns from the current session to memory. Invoke immediately after any user correction or rejected suggestion, after validation of a non-obvious choice, when the user says "remember this" / "catat ini", when a new preference,… - 95learn
Save a hard-won lesson or surprising fix so future sessions benefit. Boundary: learn records facts/gotchas; distill produces reusable multi-step procedures from conversation history. Use when: "save this to knowledge", "record this", "remember for next time", "/learn", "記下來",…