memory-health-audit

Audits memory system health by cross-correlating retrieval logs, diary, learnings, and memory files.

Updated May 3, 2026
One-click install
npx skills add https://github.com/spikelab/multiplai-cc-mktplace --skill memory-health-audit-spikelab
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: memory-health-audit
Source: https://github.com/spikelab/multiplai-cc-mktplace/tree/main/plugins/multiplai-context/skills/memory-health-audit
Command: npx skills add https://github.com/spikelab/multiplai-cc-mktplace --skill memory-health-audit-spikelab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Over time an AI memory system accumulates bloated files, stale content, routing gaps, and learnings that never get captured — with no visibility into what is actually working. This Skill performs a full cross-source audit of the memory system so you can see what is overloaded, what is never retrieved, and what to restructure. ## Core Features & Use Cases - Cross-source correlation: Analyzes retrieval logs, session diary, learnings, and the memory corpus together to surface systemic patterns like overloaded files, wasteful retrievals, and learning gaps. - Utilisation and routing precision metrics: Runs deterministic scripts to estimate which memory sections were actually used (not just loaded) and how often suggested skills were invoked. - Longitudinal tracking: Saves dated assessment snapshots and compares against previous audits to show whether past changes improved the system. - Use Case: Run monthly to answer "how's memory doing" — get prioritized recommendations such as which files to split, which routing domains to tighten, and which stale sections need review, each backed by concrete metrics. ## Quick Start Ask the assistant to run a memory health audit and report what patterns it has noticed about the memory system.

Frequently Asked Questions about memory-health-audit

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

FAQPage Schema
How do I audit my AI memory system health?

Run the memory health audit, which parses retrieval logs, diary entries, learnings, and memory files in parallel, then cross-correlates the results into findings and recommendations. The full assessment is saved as a dated snapshot for longitudinal comparison.

What is the difference between memory-health-audit and the health check command?

The /multiplai-context:health check verifies infrastructure — files exist, config is wired, nothing is stale. This audit goes further by cross-correlating all four data sources to surface systemic patterns like overloaded files, routing gaps, and learning extraction failures.

How often should I run a memory health audit?

Monthly cadence is recommended, after at least 50 routing decisions have accumulated since the last assessment. Each run saves a dated snapshot so deltas between assessments show whether changes improved the system.

Does the memory audit delete or modify my memory files?

No. The audit only proposes changes — it never writes to memory. High-cost-per-use sections are flagged as candidates for a human to review, and only the dream-remember command can edit memory files.

Why does the audit say retrieval frequency is not enough?

Retrieval counts show what was loaded, not what was used — a section loaded on every prompt but relevant on none scores best by that metric. The utilisation table and skill routing precision reports provide the counterweight using two separate estimators.