skills/session-learning/SKILL.md
Socratic teaching pass over the work just done in a session: incremental comprehension stages, a running checklist doc, restate-understanding-first, and AskUserQuestion quizzes. The session doesn't end until the user has demonstrated understanding. Run after Claude has completed substantive work worth deeply understanding.
npx skillsauth add nweii/agent-stuff session-learningInstall 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.
you are a wise and incredibly effective teacher. your goal is to make sure the human deeply understands the session.
do this incrementally with each step instead of all at once at the end. before moving on to the next stage, you should confirm that they have mastered everything in the current one. this should be high level (e.g. motivation) and low level (e.g. business logic, edge cases).
keep a running md doc with a checklist of things the human should understand. make sure they understand 1) the problem, why the problem existed, the different branches 2) the solution, why it was resolved in that way, the design decisions, the edge cases 3) the broader context of why this matters, what the changes will impact.
make sure they understand why (and drill down into more whys), make sure they understand what and how as well. understanding the problem well is imperative.
to get a sense of where they're at, proactively have them restate their understanding first. then help them fill in the gaps from there—they might ask you questions or ask to eli5, eli14, or elii (explain like they're an intern).
quiz them with open-ended or multiple choice questions with AskUserQuestion (be sure to change up the order of the correct answer, and to not reveal the answer until after the questions are submitted). show them code or have them use the debugger if necessary!
/goal the session should not end until you've verified that the human has demonstrated that they understood everything on your list.
testing
Command-invoked tutoring pass for understanding something deeply: a concept being learned, or work just done in the session. Locates where the learner is, teaches one step per turn, quizzes to verify, and continues until they can explain the material back and apply it. Can produce durable artifacts (a walkthrough of the work, a record of what was learned, a glossary) saved through whatever the environment supports. Best run after substantive work, or when the aim is to learn something.
testing
Search, read, filter, combine, adapt, and save recipes in the Brain vault collection. Use whenever cooking and the collection are relevant — 'what should I make', 'recipes with miso', 'save this one' all imply it.
development
Writing-partner processes that draw out the user's own writing through questioning: guided drafting sessions, fragment mining, shaping raw material into a piece, and phrase tightening. Use for help discovering, developing, and structuring writing (notes, essays, messages, etc).
development
Plan, write, review, and maintain software tests. Use when building features or fixing bugs test-first with a red-green loop, writing or rewriting unit/integration/e2e tests, reviewing or auditing test quality, choosing what level of test to write, working with mocks and fixtures, or keeping an existing suite in mind while making code changes.