SkillAgentSearch skills...

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.

Install / Use

npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill memory-review

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

87/100

Category

Operations

Supported Platforms

Claude Code
Zed

Our assessment of memory-review

memory-review scores 87/100 on our quality scale, 457th of 763 Operations skills we index.

Its SKILL.md is 3.8 KB long, well organised into 10 sections with 2 code examples: a solid amount of guidance for an agent.

With 1,015 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
26/30
Structure
18/20
Description
15/15
Adoption
13/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so memory-review is actively maintained.
  • Our last check on 2026-10-11 found the source still online.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-10-07. Automated pattern scan on 2026-10-07. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

memory-review compared with similar skills

All 4 of these similar skills score higher than memory-review; compare them before choosing.

SkillScoreStarsUpdatedFormat
memory-review (this skill)by hoangsonww871.0k2mo agoSKILL.md
Agent-Reachby Panniantong100114.0ktodayCLAUDE.md
headroomby headroomlabs-ai10080.5ktodayCLAUDE.md
Scraplingby D4Vinci100104.9k5d agoMCP Server
crawl4aiby unclecode10087.7k2d agoMCP Server

Frequently asked questions

How do I install memory-review?
Run npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill memory-review. The install tabs above show the steps for each supported agent.
Which AI agents does memory-review work with?
It is written for Claude Code and Zed, as a SKILL.md file. Other agents that read the same format can often use it too.
Is memory-review safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is memory-review still maintained?
The repository was last updated about 2 months ago, so memory-review is actively maintained.

name: memory-review description: > 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.

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 worth splitting into auto-memory facts.

2. Per-project auto-memory, grouped

Group scope: "auto-memory" items by project. For each project show the index (isIndex: true, typically MEMORY.md) first, then the per-fact files. For each fact show name, frontmatter.description if present, size, and mtime.

3. Index vs per-fact consistency

Within each project, compare the index (MEMORY.md) against the per-fact files present. Flag facts that exist on disk but are not referenced by the index, and index entries that point at files which no longer appear in /memory.

4. Stale & oversized facts

Flag facts whose mtime is old relative to the rest of the store (stale — candidates to confirm or retire) and facts whose size is large (oversized — candidates to split into smaller, single-fact files). When the user wants to act on one, fetch its full body with GET /api/cc-config/file?path=<file> before recommending changes.

Editing memory (mutations)

Auto-memory files are editable through the Config Explorer. To create/overwrite a fact:

curl -s -X PUT http://localhost:4820/api/cc-config/file \
  -H 'Content-Type: application/json' \
  -d '{"scope":"auto-memory","type":"auto-memory","project":"<slug>","name":"<fact>.md","content":"..."}'

To delete a fact:

curl -s -X DELETE http://localhost:4820/api/cc-config/file \
  -H 'Content-Type: application/json' \
  -d '{"scope":"auto-memory","type":"auto-memory","project":"<slug>","name":"<fact>.md"}'

A timestamped backup is written automatically before any edit or delete. The user/project CLAUDE.md uses type:"memory" with a scope and no name. Never edit or delete a memory file without explicit per-action confirmation from the user — default to read-only review.

Output

  • Section 1 as a short table (Scope | File | Size | Modified | Truncated).
  • Section 2 grouped by project, index first, then facts.
  • Sizes in KB; timestamps as relative age; use ▲ for oversized / stale flags.
  • Cite only fields the API returned — never invent facts, names, or sizes.
  • If the dashboard is unreachable at http://localhost:4820, say so and tell the user to start it with npm start from the repo root.

Related Skills

View on GitHub
GitHub Stars1.0k
CategoryOperations
Updated2mo ago
Forks238

Languages

JavaScript

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions