Skip to main content

memory-maintenance

Diagnose and maintain ClawXMemory index health using scripts and tools. Use when installation, indexing, or data quality looks wrong.

소스 정보

저장소
OpenBMB/ClawXMemory
최근 소스 활동
2026년 3월 30일 11:21
감지된 SKILL.md 언어
영어
스타
49
포크
8

설치 방법

기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.

소스 파일 검토

설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.

파일 탐색기
3 개 파일

SKILL.md 표시 중

SKILL.md
소스 지침 · 읽기 전용 미리보기
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":"[Truncated]"}}}
# Memory Maintenance Use this skill for diagnosis and maintenance of ClawXMemory storage/indexes. ## Mixed Mode Policy - Prefer tool calls for normal user-facing retrieval flows. - Use scripts only for diagnostics, data checks, and troubleshooting. ## Recommended Workflow 1. Read current memory behavior with tools: - `memory_overview` - `memory_list` - `memory_search` - `memory_get` 2. If the user wants an immediate refresh or you see pending memory, run `memory_flush`. 3. If behavior is still suspicious, run scripts: - `node {baseDir}/scripts/inspect-indexes.mjs --db <path>` - `node {baseDir}/scripts/recent-sessions.mjs --db <path> --limit 5` 4. Compare script output with tool output. 5. Report concrete findings: - missing data - stale indexing - low extraction quality - query mismatch ## Script Defaults - Default DB path: `~/.openclaw/clawxmemory/memory.sqlite` - You can override with `--db /absolute/path/to/memory.sqlite` ## Common Debug Cases - Install succeeds but recall empty: start with `memory_overview`, then check table counts and `lastIndexedAt`. - Project answers weak: start with `memory_search`, then inspect `l2_project` and recent `l1` ids using `memory_get`. - Timeline mismatch: inspect `l2_time` ids from `memory_search`, then compare against the latest `l0` sessions. - Recent turn not visible yet: inspect `pendingL0` in `memory_overview`, then run `memory_flush`. ## Guardrails - Scripts are read-only diagnostics in this skill. - Do not modify DB directly from this skill unless user explicitly asks for data repair.
GitHub에서 보기