Memory Hygiene
Audit, clean, and optimize Clawdbot's vector memory (LanceDB). Use when memory is bloated with junk, token usage is high from irrelevant auto-recalls, or setting up memory maintenance automation.
Why this rating
Deterministic checks triggered by the tool capabilities and evidence.
- Locality: Local
Operates on local memory storage (e.g., `~/.clawdbot/memory/lancedb/`) and gateway configuration.
- Data access: Sensitive
Vector memory can contain user preferences, decisions, and other private long-term context.
- Action surface: Execute
Includes destructive operations like `rm -rf` wipes and can add scheduled cron maintenance jobs.
Best practices
Follow these steps to reduce risk when using this skill.
- Back up `~/.clawdbot/memory/lancedb/` (or export key entries) before wiping so you can recover important facts.
- Be cautious with scheduled wipes; review cron jobs regularly and keep a clear rollback plan.
- Never store plaintext secrets, OAuth URLs, or tokens in vector memory; use env vars or a secrets manager instead.
Evidence links
Public sources backing the indicator assignments.
Always be careful when navigating away from the website.
Max-risk rule
If any capability reaches a higher level, the entire indicator level bumps up to keep ratings deterministic and easy to scan.