memory-health

Audit Claude Code's MEMORY.md index for size, orphaned files, broken links, and stale entries.

61|1|Updated Jun 26, 2026
One-click install
npx skills add https://github.com/alexknowshtml/claude-memory-health --skill memory-health-alexknowshtml
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: memory-health
Source: https://github.com/alexknowshtml/claude-memory-health/tree/main
Command: npx skills add https://github.com/alexknowshtml/claude-memory-health --skill memory-health-alexknowshtml

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires claude, bun, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill addresses the issue of signal dilution and silent truncation in Claude Code's MEMORY.md index, ensuring that the most valuable context loads every session.

Core Features & Use Cases

  • Audit MEMORY.md: Checks for size, orphaned files, broken links, and staleness candidates.
  • Demote to Cold Storage: Moves lower-priority notes to cold storage to keep the index focused.
  • Autonomous Demotion: Runs headlessly with Claude CLI to demote entries without user interaction.

Quick Start

Run the /memory-health command in Claude Code to audit your MEMORY.md index.

Frequently Asked Questions about memory-health

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

FAQPage Schema
How do I audit a Claude Code MEMORY.md file for broken links and stale entries?

Auditing a Claude Code MEMORY.md file involves checking the index for size limits, orphaned files, broken links, and stale entries. Running the /memory-health command scans the index and identifies these issues to prevent signal dilution and silent truncation.

Why does my Claude Code memory index get truncated silently during sessions?

Claude Code memory index truncation happens silently when the MEMORY.md file exceeds size limits, causing signal dilution. Auditing the index checks for size constraints and orphaned files to ensure the most valuable context loads every session.

What is autonomous demotion to cold storage in Claude Code memory management?

Autonomous demotion to cold storage is a memory management process that moves lower-priority notes out of the active index. It runs headlessly using the Claude CLI to demote stale entries without user interaction, keeping the index focused.

Do I need Bun installed to run memory index audits for Claude Code?

Running memory index audits for Claude Code requires both the Claude Code environment and Bun installed. These dependencies are necessary to execute the scripts that check for orphaned files, broken links, and perform autonomous demotion.

How do I move lower-priority notes to cold storage in Claude Code?

To move lower-priority notes to cold storage in Claude Code, use the autonomous demotion feature. This process runs headlessly with the Claude CLI to automatically identify and demote stale entries, keeping the MEMORY.md index optimized.

What's the best way to maintain a Claude Code MEMORY.md index for long-term projects?

The best way to maintain a Claude Code MEMORY.md index is regular auditing for size, broken links, and staleness. Implementing autonomous demotion to cold storage moves lower-priority notes automatically, preventing signal dilution across long-term sessions.