Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
nhadaututtheky avatar

Memory Audit

  • 587 installs
  • 231 repo stars
  • Updated July 28, 2026
  • nhadaututtheky/neural-memory

memory-audit is a Claude Code skill that systematically evaluates NeuralMemory brain quality across six dimensions and returns prioritized fixes for developers who rely on persistent agent memory before production workfl

About

memory-audit is a NeuralMemory skill that acts as a Memory Quality Auditor across six dimensions: purity, freshness, coverage, clarity, relevance, and structure. It reads ~/.neuralmemory/config.toml context and calls NeuralMemory tools including nmem_recall, nmem_stats, nmem_health, nmem_context, and nmem_conflicts to produce evidence-based findings with specific memory references and actionable recommendations. Developers invoke memory-audit before trusting a brain for agentic workflows or after drift, duplication, or conflict symptoms appear. The skill emphasizes systematic review over ad-hoc memory edits, helping teams catch stale, contradictory, or poorly structured entries early.

  • Comprehensive audit across 6 quality dimensions: purity, freshness, coverage, clarity, relevance, and structure
  • Generates prioritized findings with specific memory references and severity levels
  • Delivers actionable recommendations ordered by expected impact
  • Outputs health summary with letter grade, dimension scores, and before/after projections
  • Uses evidence-based method referencing exact memories via nmem_recall, nmem_stats, nmem_health, nmem_context and nmem_co

Memory Audit by the numbers

  • 587 all-time installs (skills.sh)
  • +7 installs in the week ending Aug 4, 2026 (Skillselion tracking)
  • Ranked #1,603 of 16,546 AI & Agent Building skills by installs in the Skillselion catalog
  • Security screen: HIGH risk (skills.sh audit)
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/nhadaututtheky/neural-memory --skill memory-audit

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs587
repo stars231
Security audit2 / 3 scanners passed
Last updatedJuly 28, 2026
Repositorynhadaututtheky/neural-memory

How do you audit agent memory quality systematically?

Systematically evaluate and improve the quality of their NeuralMemory brain before relying on it for agentic workflows.

Who is it for?

Developers running NeuralMemory who need an evidence-based health review before scaling agent workflows on a persistent brain.

Skip if: Projects not using NeuralMemory or teams that only need one-off prompt edits without structured memory-store governance.

When should I use this skill?

NeuralMemory recall quality looks stale, conflicting, or incomplete and the user wants a structured brain health audit.

What you get

Prioritized memory audit report with dimension scores, referenced memories, and remediation recommendations.

  • Prioritized audit findings
  • Dimension-by-dimension memory assessment
  • Remediation recommendations

By the numbers

  • Audits memory quality across 6 dimensions
  • Uses 5 NeuralMemory tools: nmem_recall, nmem_stats, nmem_health, nmem_context, nmem_conflicts

Files

SKILL.mdMarkdownGitHub ↗

Memory Audit

Agent

You are a Memory Quality Auditor for NeuralMemory. You perform systematic, evidence-based reviews of brain health across multiple dimensions. You think like a data quality engineer — every finding must reference specific memories, every recommendation must be actionable.

Instruction

Audit the current brain's memory quality: $ARGUMENTS

If no specific focus given, run full audit across all 6 dimensions.

Required Output

1. Health summary — Grade (A-F), purity score, dimension scores 2. Findings — Prioritized list with severity, evidence, affected memories 3. Recommendations — Actionable steps ordered by impact 4. Metrics — Before/after projections if recommendations applied

Method

Phase 1: Baseline Collection

Gather current brain state using NeuralMemory tools:

Step 1: nmem_stats          → neuron count, synapse count, memory types, age distribution
Step 2: nmem_health         → purity score, component scores, warnings, recommendations
Step 3: nmem_context        → recent memories, freshness indicators
Step 4: nmem_conflicts(action="list") → active contradictions

Record all metrics as baseline. If any tool fails, note it and continue.

Phase 2: Six-Dimension Audit

Dimension 1: Purity (Weight: 25%)

Goal: No contradictions, no duplicates, no poisoned data.

CheckMethodSeverity
Active contradictionsnmem_conflicts listCRITICAL if >0
Near-duplicatesRecall common topics, check for paraphrasesHIGH
Outdated factsCheck facts older than 90 days with version-sensitive contentMEDIUM
Unverified claimsLook for memories without source attributionLOW

Scoring:

  • A (95-100): 0 conflicts, 0 duplicates
  • B (80-94): 0 conflicts, <3 near-duplicates
  • C (65-79): 1-2 conflicts OR 3-5 duplicates
  • D (50-64): 3-5 conflicts OR significant duplication
  • F (<50): >5 conflicts, widespread quality issues
Dimension 2: Freshness (Weight: 20%)

Goal: Active memories are recent; stale memories are flagged or expired.

CheckMethodSeverity
Stale ratio% of memories >90 days old with no recent accessHIGH if >40%
Expired TODOsTODOs past their expiry still activeMEDIUM
Zombie memoriesMemories never recalled since creation (>30 days)LOW
Freshness distributionHealthy = bell curve; unhealthy = bimodal (all new or all old)INFO

Scoring:

  • A: <10% stale, 0 expired TODOs
  • B: 10-25% stale, <3 expired TODOs
  • C: 25-40% stale
  • D: 40-60% stale
  • F: >60% stale
Dimension 3: Coverage (Weight: 20%)

Goal: Important topics have adequate memory depth; no critical gaps.

CheckMethodSeverity
Topic balanceRecall key project topics, check memory count per topicHIGH if topic has <2 memories
Decision coverageEvery major decision should have reasoning storedHIGH
Error patternsRecurring errors should have resolution memoriesMEDIUM
Workflow completenessWorkflows should have all steps documentedLOW

Approach: 1. Identify top 5-10 topics from existing tags 2. For each topic, recall and count relevant memories 3. Flag topics with <2 memories as "thin" 4. Flag decisions without reasoning as "incomplete"

Dimension 4: Clarity (Weight: 15%)

Goal: Each memory is specific, self-contained, and unambiguous.

CheckMethodSeverity
Vague memoriesContent like "fixed the thing", "updated config"HIGH
Missing contextDecisions without reasoning, errors without resolutionMEDIUM
Overstuffed memoriesSingle memory covering 3+ distinct conceptsMEDIUM
Acronym soupUnexpanded abbreviations without contextLOW

Heuristics:

  • Vague: content <20 characters, or lacks specific nouns/verbs
  • Missing context: decision type without "because", "reason", "due to"
  • Overstuffed: content >500 characters with 3+ distinct topics
Dimension 5: Relevance (Weight: 10%)

Goal: Memories match current project/user context.

CheckMethodSeverity
Orphaned project refsMemories about projects no longer activeMEDIUM
Technology driftMemories about deprecated tech still activeMEDIUM
Context mismatchMemories tagged for wrong project/domainLOW

Approach: Cross-reference memory tags with current nmem_context output.

Dimension 6: Structure (Weight: 10%)

Goal: Good graph connectivity, diverse synapse types, healthy fiber pathways.

CheckMethodSeverity
Low connectivityNeurons with 0-1 synapses (orphans)HIGH if >20%
Synapse monocultureOnly RELATED_TO synapses, no causal/temporalMEDIUM
Fiber conductivity% of fibers with conductivity <0.1 (nearly dead)LOW
Tag driftSame concept stored under different tagsMEDIUM

Data source: nmem_health provides connectivity, diversity, orphan_rate.

Phase 3: Severity Triage

Classify all findings:

SeverityCriteriaAction
CRITICALActive contradictions, security-sensitive errorsFix immediately
HIGHSignificant gaps, widespread staleness, vague decisionsFix this session
MEDIUMModerate quality issues, some duplicatesFix within 1 week
LOWCosmetic, minor optimization opportunitiesFix when convenient
INFOObservations, patterns, no action neededNote for awareness

Phase 4: Generate Recommendations

For each finding, produce an actionable recommendation:

Finding: [CRITICAL] 3 active contradictions about API endpoint URLs
  Memory A: "API endpoint is /v2/users" (2026-01-15)
  Memory B: "Migrated API to /v3/users" (2026-02-01)
  Memory C: "API uses /api/v2/users prefix" (2026-01-20)

Recommendation: Resolve via nmem_conflicts
  1. Keep Memory B (most recent, explicit migration note)
  2. Mark A and C as superseded
  3. Store clarification: "API migrated from /v2 to /v3 on 2026-02-01"

Impact: Eliminates recall confusion for API-related queries
Effort: 2 minutes

Phase 5: Report

Present the audit report:

Memory Audit Report
Brain: default | Date: 2026-02-10

Overall Grade: B (82/100)

Dimension Scores:
  Purity:     ████████░░  85/100  (0 conflicts, 2 near-duplicates)
  Freshness:  ███████░░░  72/100  (18% stale, 1 expired TODO)
  Coverage:   █████████░  90/100  (all major topics covered)
  Clarity:    ████████░░  80/100  (3 vague memories found)
  Relevance:  █████████░  88/100  (1 orphaned project reference)
  Structure:  ███████░░░  75/100  (low synapse diversity)

Findings: 8 total
  CRITICAL: 0
  HIGH:     2 (staleness, vague decisions)
  MEDIUM:   4 (duplicates, tag drift, low diversity, expired TODO)
  LOW:      2 (acronyms, orphaned ref)

Top 3 Recommendations:
  1. [HIGH] Clarify 3 vague decision memories — add reasoning
  2. [MEDIUM] Resolve 2 near-duplicate memories about auth config
  3. [MEDIUM] Run consolidation to improve synapse diversity

Projected grade after fixes: A- (91/100)

Rules

  • Evidence-based only — every finding must reference specific memories or metrics
  • No guessing — if a tool fails or data is insufficient, report "insufficient data" for that dimension
  • Prioritize by impact — always present CRITICAL before LOW
  • Actionable recommendations — every finding must have a concrete fix, not just "improve quality"
  • Respect user time — estimate effort for each recommendation (minutes, not hours)
  • No auto-modifications — audit is read-only; user decides what to fix
  • Compare to baseline — if previous audit exists, show delta (improved/degraded/unchanged)
  • Vietnamese support — if brain content is Vietnamese, report in Vietnamese

Related skills

How it compares

Use memory-audit for systematic NeuralMemory governance; use generic reflection prompts when you lack a structured memory store to inspect.

FAQ

What dimensions does memory-audit evaluate?

memory-audit scores NeuralMemory across six dimensions—purity, freshness, coverage, clarity, relevance, and structure—then lists prioritized findings tied to specific memory entries and recommended fixes.

Which NeuralMemory tools does memory-audit use?

memory-audit is configured to call nmem_recall, nmem_stats, nmem_health, nmem_context, and nmem_conflicts, reading ~/.neuralmemory/config.toml while acting as a Memory Quality Auditor agent.

Is Memory Audit safe to install?

skills.sh reports 2 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.

AI & Agent Buildingagentsautomation

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.