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 set...

This skill appears to do what it says (audit, wipe, reseed LanceDB memory), but it contains high-impact operational steps you should not run blindly. Before installing or invoking: 1) Back up your existing memory directory (don't run rm -rf without a verified path). 2) Inspect MEMORY.md and other sources for secrets — avoid storing actual tokens/passwords or precise credential values in vector memory. 3) Restrict which agents/users can execute shell commands, gateway restarts, or config.patch actions. 4) Prefer manual runs initially or test on a non-production instance. 5) If you enable the cron job, ensure you have monitoring and backups so automated wipes cannot cause data loss. If you want tighter safety, request the skill be modified to use non-destructive API-level deletes with confirmation prompts and to explicitly forbid storing credential locations or other sensitive material.

Type: OpenClaw Skill Name: memory-hygiene-automaton Version: 1.0.2 The skill bundle contains instructions in SKILL.md for destructive file system operations (rm -rf) and the creation of automated cron jobs to wipe and reseed vector memory. While these actions align with the stated goal of 'memory hygiene,' the use of high-risk shell commands and the suggestion to store sensitive data like 'credentials locations' in vector memory represent significant security risks and potential for data loss if executed without strict oversight.