Saves what the user teaches - a lesson, preference, convention, glossary term or project fact - as a note in their local knowledge, scoped to a role, project or skill, so future work and routing use it; also forgets notes, exports them, and handles starter-knowledge updates after a release. Use when the user says "remember", "from now on", "note that", "always", "never again", "don't do X again", "forget", when they correct how you worked, when an incident teaches something, or when they ask ...
Installs into .claude/skills of the current project.
Are you the author of Open Skill Learn?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/vokhoinhon-open-skill-learn)
---
name: open-skill-learn
description: Saves what the user teaches - a lesson, preference, convention, glossary term or project fact - as a note in their local knowledge, scoped to a role, project or skill, so future work and routing use it; also forgets notes, exports them, and handles starter-knowledge updates after a release. Use when the user says "remember", "from now on", "note that", "always", "never again", "don't do X again", "forget", when they correct how you worked, when an incident teaches something, or when they ask to export notes or review seed updates.
---
# Open Skill Learn
A correction the user makes once should not have to be made again next week. This skill keeps such lessons as small local files that `open-skill route` attaches to future chains.
`open-skill` means the CLI; if it is not on PATH use `uvx --from git+https://github.com/VoKhoiNhon/open-skill-standard@v0.7.4 open-skill`.
## Save
One fact per note, written so it still makes sense months later. Record corrections and approaches the user confirmed, with the reason when it matters.
```bash
open-skill learn "<one fact>" --applies-to <scopes> --type lesson|preference|pitfall|glossary|project-fact
```
Scopes tell the router when the note applies; combine as needed, comma separated:
`skill:<id or invoke name>` (for example `skill:bmad-method/bmad-build`), `role:<role-id>`, `project:<path>` (`project:.` for the current project), `phase:<phase>`, or `role:*` for everything. Quote a scope with `*` (`'role:*'`) so the shell does not expand it. An unknown kind, role or phase is refused with the valid values.
Saving the same text again updates the existing note instead of duplicating it. Don't save what the repository or chat history already records; a copy goes stale when the source changes. The CLI refuses text that looks like a secret, token, email or phone number; keep credentials and personal data out of notes entirely.
## Forget, review, move
- `ls ~/.open-skill/knowledge/` lists notes (the `home` line of `open-skill status` shows the folder if it moved); each is a plain Markdown file the user can edit.
- `open-skill forget <note-id>` deletes one; delete notes that turned out to be wrong.
- `open-skill export <file.zip>` copies profile and notes to another machine (usage history stays local).
- `open-skill scan --memory` imports Claude Code memory files as notes, read-only.
## After an update
Updating skills or the CLI never changes the notes folder. When the CLI reports that it upgraded the user's data, or `open-skill status` lists seed updates to review, tell the user in one line and offer:
- `open-skill upgrade --dry-run`, then `open-skill upgrade` — back up, migrate, sync starter knowledge.
- `open-skill seeds diff` — upstream rewrote a seed the user had edited; `open-skill seeds accept <id>` takes upstream's wording (after a backup), `open-skill seeds keep <id>` keeps theirs.
- `open-skill upgrade --rollback` — undo the last upgrade.
Let the user decide on seed updates; their edited wording is theirs.
## First use
If `~/.open-skill/profile.yaml` does not exist, suggest `open-skill init --role <role>[=weight]`; it saves the user's roles and seeds starter notes for them.
