memory-bloat-audit

Audit configured memory workspaces for invariant violations and emit a Drift incident.

Updated Jun 23, 2026

Search Tags:#automation #drift detection #memory audit #invariant checking #workspace health #incident generation

Ready to run

npx skills add https://github.com/Walliiee/agent-harness --skill memory-bloat-audit

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: memory-bloat-audit
Source: https://github.com/Walliiee/agent-harness/tree/main/skills/memory-bloat-audit
Command: npx skills add https://github.com/Walliiee/agent-harness --skill memory-bloat-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill audits the memory system for drift, stale content, and missing structure so the agent’s long-term memory stays reliable instead of silently degrading over time.

Core Features & Use Cases

Invariant checking: Detects stale daily files, freehand writes, stuck promote-queue items, and empty wiki spaces.
Operational drift detection: Confirms the memory pipeline is behaving as documented after promotion and cleanup runs.
Incident generation: Produces a single rolled-up Drift incident when any memory invariant fails, making review and remediation straightforward.
Use case: Run it on a scheduled cadence to verify that memory capture, promotion, and migration are still happening correctly across configured workspaces.

Quick Start

Ask the agent to audit the configured memory workspaces for invariant violations and report any Drift incidents with recommended fix paths.

Frequently Asked Questions about memory-bloat-audit

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

FAQPage Schema

How do I audit my agent's long-term memory system for drift and stale content?▼

A memory audit detects stale daily files, stuck promote-queue items, and empty wiki spaces by checking invariants across configured workspaces, ensuring long-term memory remains reliable and does not silently degrade.

How do I detect memory capture drift and invariant violations in configured workspaces?▼

Memory capture drift and invariant violations are detected through filesystem inspection of workspace configuration, verifying that memory capture, promotion, and migration pipelines still behave as documented.

What happens when a long-term memory invariant check fails during a scheduled workspace audit?▼

When a memory invariant check fails, the audit emits a single rolled-up Drift incident that aggregates the failures, making review and remediation straightforward with recommended fix paths.

Can I use memory drift detection to verify operational pipeline behavior after promotion and cleanup runs?▼

Yes, operational drift detection confirms the memory pipeline is behaving as documented after promotion and cleanup runs, catching freehand writes and stuck items before they spread.

Do I need filesystem inspection access to check workspace wiki coverage and daily notes for memory invariants?▼

Yes, filesystem inspection of workspace configuration is required to check daily notes, promote queues, and workspace wiki coverage for memory invariants and operational drift.