Capture useful lessons from the current session as clear, reusable notes for the user. Use when asked to learn from a session or save what was learned.
Installs into .claude/skills of the current project.
Are you the author of Learn?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/catherine1401-learn)
---
name: learn
description: Capture useful lessons from the current session as clear, reusable notes for the user. Use when asked to learn from a session or save what was learned.
---
- Extract verified, reusable knowledge from the current session, including corrections and why they matter. Do not turn the work log into a note or invent lessons.
- Create `.docs/learn/` if absent. Ensure Git ignores it; reuse an existing `.docs/` ignore rule or add `.docs/learn/` to `.gitignore`.
- Use exactly one note per conversation at `.docs/learn/<YYYY-MM-DD>-<conversation-slug>.md`. Make the slug short lowercase English words joined by hyphens; add a numeric suffix if another conversation already uses the name. Reuse and update the same note on later invocations in the conversation, grouping distinct lessons under separate headings.
- Start each note with YAML frontmatter containing a reader-facing `title` and a `keywords` list of search terms.
- Write the note for the user in plain language. For each lesson, explain the concept, why it matters, when to apply it, and one concrete example from the session. Define necessary jargon and distinguish verified facts from uncertainty.
- Exclude secrets, personal data, and incidental session details. If the session contains no verified reusable lesson, explain that instead of creating a filler note.
