memai-distilllisted

Distill and MOVE knowledge between MemAI types: pull what is durable out of one checkpoint (or several) into a note/reasoning/anti_pattern, change a memory's type (checkpoint→note when the content is timeless), and merge near-duplicates. Use when the user asks to "distill memory", "turn a checkpoint into a note", "move a memory to another type", "merge duplicate memories", or as a step of the [[memai-maintenance]] pass. Knows that `distill` ARCHIVES its sources — and when not to use it. Conceptual base: [[memai-memory]] (the checkpoint × note × reasoning boundary).
Filipe-Soares-de-Almeida/MemAI · ★ 0 · AI & Automation · score 70

Install: claude install-skill Filipe-Soares-de-Almeida/MemAI

# memai-distill — distill / move type / merge Saves the **durable** knowledge that is stuck in the wrong type, or held in a checkpoint that is about to be archived, without losing any of it. > **The type boundary** ([[memai-memory]] §1): `note` = a **timeless** > fact; `reasoning` = an **analysis trace**; `anti_pattern` = a trap; > `checkpoint` = transient **bearing**. When a checkpoint (or a > `reasoning`) carries a fact that **outlives the session**, that fact > wants to be a `note`. --- ## 1. `distill` — extract the durable (ARCHIVES the sources) `optimize_stage` kind **`distill`**, payload `{source_uids:[...], new_type:"note|reasoning|anti_pattern", new_content, title, tags?, domain?}`: **creates** the new memory, links `supersedes` from it to every source and **archives every source**. The dashboard's undo purges the created memory and restores each source, so the whole thing is reversible. Two uses: - retiring the checkpoints of **finished** work while keeping what they taught; - **n-ary merge**: folding N near-duplicates into one, with **synthesized** content. `verified` is **required** — the kind archives its sources. Say what the live-facts check was and where the durable content landed. Payload details: - **`new_type`** accepts only `note` / `reasoning` / `anti_pattern`. `checkpoint`/`handoff` are not targets, and neither is **`diagram`**: a flow is written by `diagram()` + `diagram_node`/`diagram_edge`, never from prose. - **`reasoning` and `anti