skills/learn-from-session/SKILL.md
Use when ending a session, when the user asks to save lessons, or when you notice a correction or preference worth remembering. Captures non-obvious lessons to AGENTS.md or skill files so the agent gets smarter over time. Do NOT use for trivial facts derivable from reading code.
npx skillsauth add paulund/skills learn-from-sessionInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Scan the session — re-read the conversation. Identify non-obvious lessons:
Categorize each lesson — use the memory conventions tree:
Is this a universal rule for a language, framework, or tool?
├── Yes → the relevant global skill in ~/.agents/skills/
└── No → Is it about user preferences or codebase conventions?
├── Yes → {repo}/AGENTS.md
└── No → Skip
Present to user — use the question tool. For each lesson, show a short description and proposed destination. Let the user confirm or redirect before writing.
Save — write the confirmed lessons to the appropriate files. Append to the relevant section.
Report — briefly state what was found (or "nothing worth saving") and where each lesson was saved.
| Rationalization | Reality | |---|---| | "This is a standard best practice, everyone knows this" | If the agent violated it and got corrected, it's not standard for this agent. Save it. | | "I'll remember this for next time" | You won't. Write it down now. | | "The user didn't say this explicitly, I inferred it" | Don't save inferred preferences — only explicit corrections and confirmations. | | "This is already in my training data" | Then why did you get it wrong? The user's correction takes priority over training data. |
development
Use when implementing any logic, fixing any bug, or changing any behaviour. Use when you need to prove code works, when a bug report arrives, or when modifying existing functionality. Do NOT use for config changes, data migrations, or dependency updates.
development
Use when starting a new feature, when requirements are unclear, when asked to write code without a clear spec, or before any non-trivial implementation. Do NOT use for trivial bug fixes or one-line changes.
development
Use when you want authoritative, source-cited code free from outdated patterns. Use when building with any framework or library where correctness matters. Detects the stack from dependency files, fetches official documentation, implements following documented patterns, and cites sources for every framework-specific decision.
development
Use when preparing to ship a feature, release, or deployment. Use before merging to main, creating a release, or deploying to production. Do NOT use for CI-only changes or internal refactors that don't reach production.