Skip to content

VoKhoiNhon/open-skill-standard / skills/open-skill-learn

open-skill-learn

Verified

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.5 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.

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.

reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 470kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall