memory-hygiene

Audit and clean LanceDB vector memory for Clawdbot deployments.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/xintuchain/tongtong --skill memory-hygiene-xintuchain
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: memory-hygiene
Source: https://github.com/xintuchain/tongtong/tree/main/skills/memory-hygiene
Command: npx skills add https://github.com/xintuchain/tongtong --skill memory-hygiene-xintuchain

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents bloated LanceDB vector memory and excessive token usage by auditing, cleaning, and reseeding stored memories so the agent only recalls relevant facts.

Core Features & Use Cases

  • Audit memory: Inspect vector entries to identify junk, low-importance, or duplicate memories and surface items causing high token use.
  • Clean and reseed: Remove the LanceDB store safely and repopulate it with curated key facts such as user preferences, important decisions, and lessons learned.
  • Automate maintenance: Disable autoCapture to stop noisy auto-saves and schedule monthly maintenance jobs to wipe and reseed memory automatically.
  • Use case: When a long-running Clawdbot accumulates transient status messages and irrelevant logs that cause frequent, costly auto-recalls, run an audit, wipe the LanceDB store, and reseed only high-value facts to restore efficient behavior.

Quick Start

Run an audit to list top memory entries, disable autoCapture, wipe the LanceDB store, and reseed key facts from MEMORY.md to restore a concise memory.

Frequently Asked Questions about memory-hygiene

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I clean up a cluttered LanceDB vector memory causing high token usage?

To clean a cluttered LanceDB vector memory, audit stored entries to identify duplicates and low-value data, safely wipe the LanceDB store, and reseed it with curated key facts to reduce token waste.

Why does my Clawdbot agent recall irrelevant logs and transient status messages?

Clawdbot agents recall irrelevant logs when autoCapture saves noisy, low-value entries during long-running operations, which you can prevent by disabling autoCapture and reseeding only important facts.

Can I automate LanceDB memory maintenance to prevent bloated vector stores?

Yes, you can automate LanceDB memory maintenance by disabling autoCapture and scheduling monthly maintenance jobs to wipe and reseed memory automatically.

What permissions do I need to manage Clawdbot memory and LanceDB stores?

Managing Clawdbot memory requires filesystem permission to manage the LanceDB store directory, access to the gateway configuration, and the ability to run memory_recall, memory_store, and gateway restarts.

How do I reseed LanceDB memory with curated facts after wiping the store?

After wiping the LanceDB store, reseed memory by storing curated key facts such as user preferences, important decisions, and lessons learned from your MEMORY.md file to restore efficient behavior.