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

Memory Quality Auditor

  • 50 installs
  • 36 repo stars
  • Updated July 14, 2026
  • oimiragieo/agent-studio

Helps with security tasks.

About

memory-quality-auditor is a Claude Code skill for security. It helps solo builders move faster with AI-assisted development.

  • memory-quality-auditor
  • Security
  • AI-coding skill

Memory Quality Auditor by the numbers

  • 50 all-time installs (skills.sh)
  • Ranked #1,325 of 2,203 Security skills by installs in the Skillselion catalog
  • Data as of Aug 4, 2026 (Skillselion catalog sync)
npx skills add https://github.com/oimiragieo/agent-studio --skill memory-quality-auditor

Add your badge

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

Listed on Skillselion
Installs50
repo stars36
Last updatedJuly 14, 2026
Repositoryoimiragieo/agent-studio

What it does

Helps with security tasks.

Files

SKILL.mdMarkdownGitHub ↗

Memory Quality Auditor

Audit the memory system as a unified retrieval layer (STM/MTM/LTM files + index + spawn citation outcomes).

Scope

  • Retrieval drift signals
  • stale memory ratio
  • evidence injection coverage
  • citation usage/groundedness continuity

Workflow

1. Read memory artifacts and latest eval reports. 2. Compute quality metrics and threshold status. 3. Emit remediation backlog with TDD checks. 4. Record findings in memory and optional evolution recommendation.

Iron Laws

1. ALWAYS establish a baseline metric snapshot before auditing — drift is only meaningful relative to a prior measurement; auditing without a baseline produces absolute numbers that cannot identify regression. 2. NEVER close a memory finding without re-running the affected retrieval query — closing without verification creates false improvement metrics and masks persistent degradation. 3. ALWAYS include citation-groundedness checks in every audit run — uncited memory injections are the primary source of hallucination in agent spawns; skipping this check leaves the highest-risk failure mode undetected. 4. NEVER audit only the STM tier — degradation often originates in MTM/LTM promotion corruption; all three tiers must be sampled in every full audit cycle. 5. ALWAYS emit TDD-ready remediation items with a failing-test condition and expected metric threshold — vague findings ("memory quality is low") cannot be actioned by any agent.

Anti-Patterns

Anti-PatternWhy It FailsCorrect Approach
Auditing without a baselineCannot distinguish regression from steady-state; all findings are ambiguousSnapshot current metrics at session start; compute delta against the previous run
Closing findings without re-checkProduces false-positive resolution; degradation persists silently behind green metricsRe-run the specific retrieval query after each remediation; close only on confirmed green metric
Skipping citation groundednessCitation failures are the leading cause of agent hallucination; missing this check omits the highest-severity defect classInclude citation_coverage and grounded_ratio metrics in every audit report
Full-mode audit on every spawnFull audit is expensive; running it unconditionally inflates cost and slows workflowsUse --mode summary for routine checks; reserve --mode full for scheduled or triggered audits
Auditing STM onlyMTM/LTM corruption is invisible in STM-only scans; stale LTM entries contaminate future sessionsSample all three tiers: STM (current session), MTM (last 10 sessions), LTM (permanent summaries)

Memory Protocol (MANDATORY)

Before starting: Read .claude/context/memory/learnings.md

After completing:

  • New pattern → .claude/context/memory/learnings.md
  • Issue found → .claude/context/memory/issues.md
  • Decision made → .claude/context/memory/decisions.md
ASSUME INTERRUPTION: If it's not in memory, it didn't happen.

Related skills

Securityappsec

This week in AI coding

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

unsubscribe anytime.