memory-audit

Re-research the AI memory landscape and diff findings against an existing architecture doc.

Updated May 16, 2026
One-click install
npx skills add https://github.com/RohanRaoCs/memory-architect --skill memory-audit-rohanraocs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: memory-audit
Source: https://github.com/RohanRaoCs/memory-architect/tree/main/skills/memory-audit
Command: npx skills add https://github.com/RohanRaoCs/memory-architect --skill memory-audit-rohanraocs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI memory frameworks, vector databases, and pricing change constantly, so an architecture decision made months ago may already be outdated. This Skill re-researches the current landscape, compares it against your existing memory architecture doc, and tells you whether your choices still hold. ## Core Features & Use Cases - Landscape Re-research: Searches changelogs, release notes, and benchmarks for every framework in your architecture doc, plus new entrants that did not exist when it was written. - Implementation Gap Analysis: Compares what the architecture doc specifies against the actual code in src/memory/ or app/memory/ and flags divergences. - Verdict Report: Writes a dated audit report with a HOLD, MINOR UPDATE, or REDESIGN verdict, cost estimate updates, and copy-pasteable upgrade commands. - Use Case: Three months after designing your support bot's memory stack with Mem0 and pgvector, run an audit to discover Mem0 shipped a breaking API change and a new framework now beats your benchmark claims. ## Quick Start Type /memory-audit in your AI assistant to re-research the memory landscape and audit your existing architecture doc.

Frequently Asked Questions about memory-audit

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

FAQPage Schema
How do I check if my AI memory framework is outdated?

Run /memory-audit in your AI assistant. It re-searches changelogs, release notes, and benchmarks for every framework in your architecture doc, then issues a HOLD, MINOR UPDATE, or REDESIGN verdict with specific findings.

How often should I audit my AI memory architecture?

Run the audit every two to three months. The AI memory landscape moves quickly, with frameworks shipping breaking API changes, deprecations, and new benchmark results that can invalidate earlier design decisions.

Can I run a memory architecture audit without web access?

Yes, pass the offline argument to skip web research. The audit then compares the architecture doc against your actual project code only, checking implementation gaps without evaluating external framework changes.

What happens if the architecture doc is missing during an audit?

The audit stops and tells you to run /memory-design first. It requires memory-design/architecture.md (or memory-architect/architecture.md on older installs) as the baseline spec to diff against.

Does the memory audit modify my existing architecture doc?

No, it writes a separate dated report at memory-design/audit-<date>.md and appends an entry to audit-log.json. Your original architecture doc remains unchanged; recommended updates are listed as copy-pasteable commands.