memai-maintenancelisted

Orchestrator of the MemAI MAINTENANCE pass (long-term agent memory). Runs [[memai-checkpoints]], [[memai-distill]], [[memai-confidence]] and [[memai-link]] as one curation pass, owns what none of them covers — the DOMAIN TREE (nested paths, cross-listing, casing), the DIAGRAMS and the store's DECAY (`review_after`) — and consolidates everything into ONE `optimize_stage` run the human applies or rejects in the dashboard. Use when asked to "optimize / maintain / curate / clean up / review my MemAI memories", "run the memory maintenance pass", "validate and set confidence", "set confidence in bulk", "archive old checkpoints", "link memories up", "fix the domain tree", or for any broad sweep over the store. Conceptual base: [[memai-memory]].
Filipe-Soares-de-Almeida/MemAI · ★ 0 · AI & Automation · score 70

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

# memai-maintenance — the MemAI curation pass Entry point of the **maintenance pass**. It does not do the fine-grained work — it **coordinates** the four specialized skills, owns what none of them covers (**domain tree**, **diagrams**, **decay**), and folds every result into a **single** `optimize_stage` run. > **Proposer → disposer.** This pass **applies nothing on its own**: it > collects the sub-skills' suggestions and hands them to the dashboard through > `optimize_stage`. The human applies or rejects each one there (a backup is > taken before the first apply; every apply can be undone). Apply directly > (`set_confidence`/`edit_memory`/`link_memories`/`forget`/`also_domain`) only > when the user asks for it **without** the dashboard. > > **`help()` is the source of truth for the tools** — signatures read live from > the code. When unsure of a name or an argument, call `help` before trusting > this file. > > **Dashboard:** `http://127.0.0.1:8888` (default port). The MCP server can > bring it up alongside itself when `MEMAI_ADMIN_AUTOSTART` is set; otherwise > `run-admin.bat`. --- ## 0. Pre-flight (done ONCE; the sub-skills reuse it) The orchestrator warms up **once** and keeps the result in context for every sub-skill. Read each source once; nothing below is read twice. 1. **`pulse(domain)`** — the state a scope inherits, plus: - **`scope`** — what the scope HOLDS next to what came back: `subdomains` (`own` = filed exactly there, `subtree` = with descendants)