Skip to main content
skill Claude Code

memory-status — Claude skill: check agent memory health

Reports how full your project memory is, which topic files exist, and which references point at files that are gone. Useful once the agent starts losing context.

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin marketplace add alirezarezvani/claude-skills
/plugin install self-improving-agent@claude-code-skills
Open on GitHub

What memory-status does

The skill walks every memory location in a project: MEMORY.md under the auto-memory directory, CLAUDE.md in the repo root and in ~/.claude/, plus the file count in .claude/rules/. It counts lines, lists topic files, and checks each path referenced in MEMORY.md — missing files get flagged as stale.

Capacity comes with thresholds. Under 120 lines in MEMORY.md is healthy, 120–180 is a warning, past 180 is critical. For CLAUDE.md the marks are 150 and 200. A --brief flag prints a single line, handy for a quick check.

Worth installing if you run long-lived projects in Claude and memory keeps filling up — this tells you what to clean. On a short project with no memory setup, skip it.

What it helps with

  • check how many lines MEMORY.md is using
  • find references to files that no longer exist
  • see which topic files the agent created
  • gauge how full CLAUDE.md and project rules are
  • get a one-line summary of memory state

Example prompts for the agent

  • /si:memory-status
  • /si:memory-status --brief
  • how full is the project memory right now?

How to install memory-status

1Plugin marketplace

/plugin marketplace add alirezarezvani/claude-skills
/plugin install self-improving-agent@claude-code-skills

This installs the whole self-improving-agent plugin with all its skills

2Skills CLI (Vercel)

npx skills add alirezarezvani/claude-skills --skill memory-status -a claude-code

3Manually: put the files in place

~/.claude/skills/memory-status/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/memory-status/

From the same set349

The whole set →
engineering-skills Alireza Rezvani An engineering skill index for Claude Code that helps you select one specialist SKILL.md for the task at hand. It covers architecture, testing, DevOps, and data work. Claude Code 2,387installs finance-skills Alireza Rezvani Routes ambiguous finance prompts to the right bundled skill: financial-analyst, saas-metrics-coach, or month-end-close. Claude Code 2,312installs marketing-skills Alireza Rezvani A directory and router for marketing skills in Claude Code. It picks the right specialist skill for SEO, content, CRO, channels, and related tasks. Claude Code 2,264installs business-growth-skills Alireza Rezvani Routes growth and revenue prompts to the right specialized skill across customer success, sales engineering, RevOps, and proposals in Claude Code. Claude Code 2,189installs engineering-advanced-skills Alireza Rezvani An index of 37 engineering skills for architecture, automation, reliability, and platform work. Use it when a project needs task-specific engineering workflows. Claude Code 2,019installs product-skills Alireza Rezvani Product work orchestrator for Claude Code. Routes queries across 16 domain lanes and validates discovery trees with deterministic scripts. Claude Code 1,994installs pm-skills Alireza Rezvani Routes project-delivery requests across 8 PM sub-skills for Jira, Confluence, sprints, reporting, and team communication. Useful for controlled delivery work. Claude Code 1,975installs senior-backend Alireza Rezvani Scaffolds backend APIs, detects database bottlenecks, and runs load tests. Useful when designing Express routes, optimizing PostgreSQL, or preparing for production. Claude Code 1,674installs

Similar

google-drive official OpenAI This skill routes Drive, Docs, Sheets and Slides work through one entry point in Codex. Handy when you keep documents in Google and edit them from the terminal. CX Codex GP ChatGPT 25installs Zotero official OpenAI This skill connects Codex to a local Zotero library for searching records, exporting BibTeX, and adding citations to LaTeX or Markdown drafts. CX Codex GP ChatGPT 24installs find-skills vercel-labs Discovers and installs agent skills from skills.sh directly inside your coding assistant. Handy when you need domain-specific workflows for a project. Claude Code CX Codex Cursor +1 4,000,000installs grill-me Matt Pocock grill-me interviews you about a plan or design to expose gaps and sharpen decisions. Use it before implementation starts. Claude Code 1,424,476installs grill-with-docs Matt Pocock This skill interviews you about a plan or design and creates ADRs and a glossary along the way. Use it when decisions need sharper definition. Claude Code 1,219,756installs handoff Matt Pocock Creates a handoff document from the current conversation so another agent can continue the work. Use it when a task moves to a new session or agent. Claude Code 1,038,491installs grilling Matt Pocock Stress-test a plan, decision, or idea through structured rounds of questions. Use it when you need to expose assumptions before acting. Claude Code 979,543installs teach Matt Pocock Turns the current directory into a learning workspace and keeps progress across sessions. Use it when learning needs to support a concrete goal in your project. Claude Code 862,247installs

Questions about memory-status

How do I install memory-status in Claude?

Through the plugin marketplace: /plugin marketplace add alirezarezvani/claude-skills, then /plugin install self-improving-agent@claude-code-skills. Or run npx skills add alirezarezvani/claude-skills --skill memory-status -a claude-code.

What does memory-status do?

It gathers memory file stats, counts lines, looks for stale references and duplicates, then reports capacity and recommendations.

What do the status colors mean?

Green is under 60% capacity — plenty of room. Yellow is 60–90%, so run /si:memory-review. Red is above 90%, where auto-memory may start dropping older entries.

Source text

SKILL.md · MIT
---
name: "memory-status"
description: "Memory health dashboard showing line counts, topic files, capacity, stale entries, and recommendations. Use when the user runs /si:memory-status or asks how full or healthy the agent memory is."
---

# /si:memory-status — Memory Health Dashboard

Quick overview of your project's memory state across all memory systems.

## Usage

```
/si:memory-status                    # Full dashboard
/si:memory-status --brief            # One-line summary
```

## What It Reports

### Step 1: Locate all memory files

```bash
# Auto-memory directory
MEMORY_DIR="$HOME/.claude/projects/$(pwd | sed 's|/|%2F|g; s|%2F|/|; s|^/||')/memory"

# Count lines in MEMORY.md
wc -l "$MEMORY_DIR/MEMORY.md" 2>/dev/null || echo "0"

# List topic files
ls "$MEMORY_DIR/"*.md 2>/dev/null | grep -v MEMORY.md

# CLAUDE.md
wc -l ./CLAUDE.md 2>/dev/null || echo "0"
wc -l ~/.claude/CLAUDE.md 2>/dev/null || echo "0"

# Rules directory
ls .claude/rules/*.md 2>/dev/null | wc -l
```

### Step 2: Analyze capacity

| Metric | Healthy | Warning | Critical |
|--------|---------|---------|----------|
| MEMORY.md lines | < 120 | 120-180 | > 180 |
| CLAUDE.md lines | < 150 | 150-200 | > 200 |
| Topic files | 0-3 | 4-6 | > 6 |
| Stale entries | 0 | 1-3 | > 3 |

### Step 3: Quick stale check

For each MEMORY.md entry that references a file path:
```bash
# Verify referenced files still exist
grep -oE '[a-zA-Z0-9_/.-]+\.(ts|js|py|md|json|yaml|yml)' "$MEMORY_DIR/MEMORY.md" | while read f; do
  [ ! -f "$f" ] && echo "STALE: $f"
done
```

### Step 4: Output

```
📊 Memory Status

  Auto-Memory (MEMORY.md):
    Lines:        {{n}}/200 ({{bar}}) {{emoji}}
    Topic files:  {{count}} ({{names}})
    Last updated: {{date}}

  Project Rules:
    CLAUDE.md:    {{n}} lines
    Rules:        {{count}} files in .claude/rules/
    User global:  {{n}} lines (~/.claude/CLAUDE.md)

  Health:
    Capacity:     {{healthy/warning/critical}}
    Stale refs:   {{count}} (files no longer exist)
    Duplicates:   {{count}} (entries repeated across files)

  {{if recommendations}}
  💡 Recommendations:
    - {{recommendation}}
  {{endif}}
```

### Brief mode

```
/si:memory-status --brief
```

Output: `📊 Memory: {{n}}/200 lines | {{count}} rules | {{status_emoji}} {{status_word}}`

## Interpretation

- **Green (< 60%)**: Plenty of room. Auto-memory is working well.
- **Yellow (60-90%)**: Getting full. Consider running `/si:memory-review` to promote or clean up.
- **Red (> 90%)**: Near capacity. Auto-memory may start dropping older entries. Run `/si:memory-review` now.

## Tips

- Run `/si:memory-status --brief` as a quick check anytime
- If capacity is yellow+, run `/si:memory-review` to identify promotion candidates
- Stale entries waste space — delete references to files that no longer exist
- Topic files are fine — Claude creates them to keep MEMORY.md under 200 lines

© Alireza Rezvani · MIT · alirezarezvani/claude-skills

See also

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor