memory-browser
Browse ClawXMemory status and recent indexes using memory_overview first, then memory_list, and memory_get only for exact detail reads.
소스 정보
- 저장소
- OpenBMB/ClawXMemory
- 최근 소스 활동
- 2026년 3월 30일 11:21
- 감지된 SKILL.md 언어
- 영어
- 스타
- 49
- 포크
- 8
설치 방법
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
소스 파일 검토
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
SKILL.md 표시 중
SKILL.md
소스 지침 · 읽기 전용 미리보기- name
- memory-browser
- description
- Browse ClawXMemory status and recent indexes using memory_overview first, then memory_list, and memory_get only for exact detail reads.
- homepage
- https://github.com/OpenBMB/ClawXMemory/tree/main/clawxmemory
- metadata
- {"openclaw":{"skillKey":"openbmb-clawxmemory","requires":{"config":"[Truncated]"}}}
# Memory Browser
Use this skill when the user asks what ClawXMemory currently remembers, what indexes exist, or whether memory is fresh and healthy.
## Primary Path
1. Call `memory_overview` for counts, freshness, and runtime health.
2. Call `memory_list` to browse recent or filtered memory indexes.
3. If the user wants exact detail for one item, call `memory_get` only for that specific id.
## Example User Requests
- "What do you remember?"
Start with `memory_overview`, then `memory_list({ level: "l2" })`.
- "What L2 project memory entries exist?"
Use `memory_list({ level: "l2_project" })`.
- "What recent timeline memory entries exist?"
Use `memory_list({ level: "l2_time" })`.
- "Why was this not remembered?"
Start with `memory_overview`, then use `memory_flush` if the user wants an immediate refresh.
## Guardrails
- Keep browse answers concise; do not dump raw records unless the user asks.
- Prefer `memory_list` for browsing and `memory_get` for exact inspection.
- If overview shows pending work or runtime issues, say that clearly.
GitHub에서 보기