memory-review
Review the file-based memory store via the Agent Monitor Config Explorer API: the user and project CLAUDE.md plus per-project auto-memory files under ~/.claude/projects/<slug>/memory/*.md. Groups by project, shows the index (MEMORY.md) vs per-fact files, and flags stale or oversized facts. Reads /api/cc-config/memory and /api/cc-config/file?path=. Use when curating agent memory.
npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill memory-review --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Memory Review Curate the user's file-based agent memory: the long-form CLAUDE.md files plus the per-project auto-memory store — read through the Agent Monitor dashboard at `http://localhost:4820`. ## Input The user provides: **$ARGUMENTS** This may be: - empty — review the whole memory store across every project (default). - a project slug (e.g. `-Users-david-WebstormProjects-foo`) — restrict the review to that one project's auto-memory dir. - "claude-md" — review only the user/project CLAUDE.md files. ## Data Sources | Endpoint | Returns | |----------|---------| | `GET /api/cc-config/memory` | `{ items:[…] }`. CLAUDE.md entries: `{ scope:"user"\|"project", file, size, mtime, preview }`. Auto-memory entries: `{ scope:"auto-memory", project, name, isIndex, file, size, mtime, frontmatter, preview }` | | `GET /api/cc-config/file?path=<abs>` | full body of one file: `{ ok, file, size, mtime, truncated, text }` — use to read a fact in full before recommending an edit | ## Report Sections ### 1. CLAUDE.md overview List the user and project CLAUDE.md entries with `scope`, `size` (KB), and last-modified (`mtime`). Note any that are `truncated` (over 256 KB) — these are oversized and wort
- Input
- Data Sources
- Report Sections
- 1. CLAUDE.md overview
- 2. Per-project auto-memory, grouped
- 3. Index vs per-fact consistency
- 4. Stale & oversized facts
- Editing memory (mutations)
- Output
curl -s -X PUT http://localhost:4820/api/cc-config/file \ curl -s -X DELETE http://localhost:4820/api/cc-config/file \
What does the memory-review skill do?
Review the file-based memory store via the Agent Monitor Config Explorer API: the user and project CLAUDE.md plus per-project auto-memory files under ~/.claude/projects/<slug>/memory/*.md. Groups by project, shows the index (MEMORY.md) vs per-fact files, and flags stale or oversized facts. Reads /api/cc-config/memory and /api/cc-config/file?path=. Use when curating agent memory.
How do I install it?
Run `npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill memory-review --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From hoangsonww/Claude-Code-Agent-Monitor, a repository with 869 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.