memory-capture — Claude Code skill: save a thread's outcome to Basic

What memory-capture does

The skill reads where a conversation has landed and writes it up as a single Basic Memory note. Not a transcript — the decisions made, the insights surfaced, the trade-off that got settled. Because the note should read top-to-bottom as one document, a second capture in the same thread rewrites it in place rather than appending.

Re-capture needs a stable key to find the same note. If your agent exposes a session or thread id, it goes into thread_id in the frontmatter, and the lookup runs through bm_search with filters rather than query — full-text search does not reliably match custom YAML fields. Without an id, the skill matches by topic and keeps a consistent title. The overwrite goes through bm_write with overwrite=True and expected_checksum; if another session edited the note in between, you get REVISION_CONFLICT and have to read it again.

All of this runs on the Basic Memory MCP server, so bm_search, bm_read and bm_write need somewhere to go. The note layout is fixed: context, topical sections, an observations block tagged [decision], [tradeoff] and similar, plus relations via relates_to. There is no changelog section at the bottom — revisions sit in the prose where they matter. Ask for a separate note explicitly and the skill skips the thread lookup and creates a fresh one without thread_id.