npx skills add https://github.com/openclaw/skills
sundial-org/awesome-openclaw-skills
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.
Installation
npx skills add sundial-org/awesome-openclaw-skills --skill memory-hygiene
Similar popular skills
Related neighbors and high-traction skills in the same topics — useful to compare before installing.
Audit, clean, and optimize Clawdbot's vector memory (LanceDB). Use when memory is bloated with …
376 installsUse when making code changes to ensure they pass VS Code's hygiene checks. Covers the pre-commi…
2.2K installsUse when the user asks to "watch my list health over time", "flag decaying / unengaged subscrib…
10 installsAtomic commits, PR size limits, commit thresholds, stacked PRs
328 installsmacOS disk cleanup, cache pruning, stale file detection, and Downloads triage. TRIGGERS - disk …
258 installsEstablishes git workflow guardrails including conventional commits, commit message hooks, branc…
229 installsAlso in this package
Other skills from sundial-org/awesome-openclaw-skills · top by installs.
npx skills add sundial-org/awesome-openclaw-skills
More details
Agent compatibility
Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.
Also listed on
Alternate registries and mirrors of this skill.
Repository health
main
Package contents
Files included with this skill beyond the listing page.
-
skill md
SKILL.md1,970 B -
docs
SUMMARY.md217 B
History
- First seen on skills.sh
- First recorded snapshot · 95 installs
SKILL.md
Memory Hygiene
Keep vector memory lean. Prevent token waste from junk memories.
Quick Commands
Audit: Check what's in memory
memory_recall query="*" limit=50
Wipe: Clear all vector memory
rm -rf ~/.clawdbot/memory/lancedb/
Then restart gateway: clawdbot gateway restart
Reseed: After wipe, store key facts from MEMORY.md
memory_store text="<fact>" category="preference|fact|decision" importance=0.9
Config: Disable Auto-Capture
The main source of junk is autoCapture: true. Disable it:
{
"plugins": {
"entries": {
"memory-lancedb": {
"config": {
"autoCapture": false,
"autoRecall": true
}
}
}
}
}
Use gateway action=config.patch to apply.
What to Store (Intentionally)
✅ Store:
- User preferences (tools, workflows, communication style)
- Key decisions (project choices, architecture)
- Important facts (accounts, credentials locations, contacts)
- Lessons learned
❌ Never store:
- Heartbeat status ("HEARTBEAT_OK", "No new messages")
- Transient info (current time, temp states)
- Raw message logs (already in files)
- OAuth URLs or tokens
Monthly Maintenance Cron
Set up a monthly wipe + reseed:
cron action=add job={
"name": "memory-maintenance",
"schedule": "0 4 1 * *",
"text": "Monthly memory maintenance: 1) Wipe ~/.clawdbot/memory/lancedb/ 2) Parse MEMORY.md 3) Store key facts to fresh LanceDB 4) Report completion"
}
Storage Guidelines
When using memory_store:
- Keep text concise (<100 words)
- Use appropriate category
- Set importance 0.7-1.0 for valuable info
- One concept per memory entry