memory-hygiene

Audit and prune Clawdbot's LanceDB vector memory to reduce token waste.

2|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/Wike-CHI/acquisition-agent --skill memory-hygiene-wike-chi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: memory-hygiene
Source: https://github.com/Wike-CHI/acquisition-agent/tree/main/skills/memory-hygiene
Command: npx skills add https://github.com/Wike-CHI/acquisition-agent --skill memory-hygiene-wike-chi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

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.

Core Features & Use Cases

  • Audit memory to identify unused or outdated entries.
  • Wipe memory to clear all vector memory and reseed with key facts.
  • Schedule automated maintenance to prevent memory bloat during long sessions and deployments.

Quick Start

Use memory-hygiene to audit and prune your vector memory, then reseed with key facts.

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 bloated vector memory and reduce token waste?

You can audit and prune vector memory to reduce token waste by identifying and removing unused or outdated entries. This optimization improves response quality by eliminating irrelevant auto-recalls in long-running sessions.

What is the best way to automate memory maintenance for long-running deployments?

Automating memory maintenance involves scheduling regular pruning tasks to prevent vector memory bloat. This keeps memory lean and efficient during long-running deployments and memory-heavy workflows without manual intervention.

Can I wipe all vector memory and reseed it with essential facts?

Yes, you can completely wipe all vector memory to clear accumulated junk and reseed it with essential facts. This provides a fresh baseline for accurate data management when memory is heavily bloated with irrelevant entries.

Why does my automated recall return irrelevant results and high token usage?

Irrelevant automated recall results and high token usage occur when vector memory accumulates junk over time. Auditing the memory database identifies outdated entries causing this bloat, and pruning them restores response quality.

When do I need to audit vector memory for maintenance?

You should audit vector memory when memory bloats with junk, token usage rises from irrelevant auto-recalls, or when setting up maintenance automation for long-running sessions and memory-heavy workflows.