// Diagnose and maintain ClawXMemory index health using scripts and tools. Use when installation, indexing, or data quality looks wrong.
Orchestrate ClawXMemory retrieval using memory_search first and memory_get for exact file reads. Use when the user asks for historical context, project progress, project collaboration rules, or user profile facts.
Audit ClawXMemory memory quality with a read-only Dream pass over current file memories and the global profile.
Browse ClawXMemory status and recent indexes using memory_overview first, then memory_list, and memory_get only for exact detail reads.
| name | memory-maintenance |
| description | Diagnose and maintain ClawXMemory index health using scripts and tools. Use when installation, indexing, or data quality looks wrong. |
| homepage | https://github.com/OpenBMB/ClawXMemory/tree/main/clawxmemory |
| metadata | {"openclaw":{"skillKey":"openbmb-clawxmemory","requires":{"config":["plugins.entries.openbmb-clawxmemory.enabled"]}}} |
Use this skill for diagnosis and maintenance of ClawXMemory storage/indexes.
memory_overviewmemory_listmemory_searchmemory_getmemory_flush.node {baseDir}/scripts/inspect-indexes.mjs --db <path>node {baseDir}/scripts/recent-sessions.mjs --db <path> --limit 5~/.openclaw/clawxmemory/memory.sqlite--db /absolute/path/to/memory.sqlitememory_overview, then check table counts and lastIndexedAt.memory_search, then inspect l2_project and recent l1 ids using memory_get.l2_time ids from memory_search, then compare against the latest l0 sessions.pendingL0 in memory_overview, then run memory_flush.