kb-memory

Distill one captured Claude Code session (or a --since window of them) into 1–3 durable kb memories — what was decided, what shipped, what failed and why. Use when a finished session had commits but produced no curated memory (the Stop-hook nudge names this skill), when the user asks to distill/keep what a session learned, or after substantial work worth remembering. Dedups against existing memory, quality-gates every write, stamps session provenance. Supports --dry-run.

Distill a closed or rotated kb slate into durable memory — reads every post across the slate's current AND archived generations, writes 1-5 kb memories (decisions plus the tried dead ends with their reasons), one short narrative note, and dated plan-file Status lines. Use at milestone/tag time when a project's slate has been closed or rotated, when the operator asks to distill/archive a slate before it ages out of relevance, or when a plan file's Status still points at a slate that no longer has anything live left on it. The daemon never authors memory text (#10/#26, no in-daemon LLM) — this skill is where the slate's working state becomes curated fact.

Tidy a project's kb slate — read the open board plus history and the displaced lists, then drop noise YOU or a presumed-ended session authored (never a live other session's now/warn/take/hand), merge near-duplicate founds with --supersedes, and close (done) asks whose asker's session has ended. Use when the nudge line fires ("this session has N undropped found/idea posts"), when a slate's found/idea section looks cluttered or stale, when starting work on a project whose slate hasn't been tidied in a while, or when the operator asks to tidy/clean up the slate. Every action IS an ordinary attributed post (drop / found --supersedes / done) — this skill invents no separate report kind, and posts nothing beyond the drops/merges/closes it actually makes.

Sweep code-citing kb memories against the live checkout via kb-code's doclens and file dated [kb-drift] comments on citations that no longer resolve — plus a born-stale check and an escalation path to kb memory flag when the FACT itself is wrong. Use on a cadence (weekly, or after a large refactor lands), when the user asks whether memory still matches the code, or when a recall hit cites code you know just moved. Dedups to one open comment per (memory, path). Supports --dry-run.

Turn one project's ledger (a week — or any N-day window — of sessions/commits/decisions/research) into a short narrative "week in review" note. Use when the user asks "what did I ship on <project> this week", wants a weekly/periodic review, or asks to summarize recent project activity from kb. Reads GET /api/sessions/ledger (facts, daemon-computed, LLM-free); the narrative prose is written by YOU, the agent — never the daemon (#10/#26, kb's no-in-daemon-LLM rule). Saves the result as a kb note (kb notes new) in the sessions corpus the ledger's rows came from.