memory-audit

Audits AgentOS/Claude Code memory backend and local file health.

3|1|Updated May 21, 2026
One-click install
npx skills add https://github.com/qwwiwi/agentos-skills-public --skill memory-audit-qwwiwi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: memory-audit
Source: https://github.com/qwwiwi/agentos-skills-public/tree/main/skills/memory-audit
Command: npx skills add https://github.com/qwwiwi/agentos-skills-public --skill memory-audit-qwwiwi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you quickly verify whether an AgentOS/Claude Code agent’s memory backends and local memory state are functioning correctly, especially after significant changes.

Core Features & Use Cases

  • Memory backend self-check: Validates connectivity and surfaces issues by checking inbox, active tasks, and agent status/heartbeat fields.
  • Local memory file audit: Detects missing memory files and flags unusually large files that may indicate rotation/maintenance risk.
  • Skills and workflow consistency review: Highlights deprecated paths/usages (e.g., older memory-cli references) to prevent broken coordination.
  • Obsidian sync & cron visibility: Checks cron presence, expected sync scripts, sync logs, and vault folder structure to catch pipeline failures.

Quick Start

Run the memory-audit skill when you want to verify the current state of the agent’s memory backend and local memory files after major updates.

Frequently Asked Questions about memory-audit

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

FAQPage Schema
How do I verify agent memory backend connectivity and health after a system update?

To verify agent memory backend connectivity, run a memory audit to validate inbox, active tasks, status, and heartbeat fields, producing an actionable report that surfaces critical failures for immediate follow-up.

What does checking local memory files reveal about maintenance risks?

Checking local memory files detects missing memory files and flags unusually large files, highlighting rotation or maintenance risks that could impact agent health and operational stability.

How do I detect deprecated paths and broken references in my agent memory workflows?

Detecting deprecated paths requires reviewing skills and workflow consistency to highlight older memory-cli references, preventing broken coordination and ensuring memory pipelines function correctly.

Can I use memory audit to check Obsidian sync configuration and cron presence?

Yes, you can use memory audit to check Obsidian sync configuration, verifying cron presence, expected sync scripts, sync logs, and vault folder structure to catch pipeline failures.

When should I run an agent memory health check?

You should run an agent memory health check after large system changes, major updates, or when you request memory checks such as audit memory or verify memory to ensure operational stability.

Why does my agent memory audit report show critical failures?

Critical failures in an agent memory audit report indicate issues with memory backend connectivity, missing local memory files, deprecated paths, or broken cron and Obsidian sync configurations needing immediate follow-up.