/si:memory-status — Memory Health Dashboard

Memory health dashboard showing line counts, topic files, capacity, stale entries, and recommendations.

How to use it

Claude Code
  1. Run the line below. It pulls the whole folder into ~/.claude/skills/memory-status, including the files SKILL.md points to.
  2. Describe your job in plain words. Claude Code follows the skill from there.
Claude Code — installs the whole folder, not just SKILL.md
npx degit alirezarezvani/claude-skills/engineering-team/self-improving-agent/skills/memory-status#main ~/.claude/skills/memory-status

For one project only, change the path to .claude/skills/memory-status. This skill also uses MEMORY.md — copying SKILL.md alone won't be enough. See the folder on GitHub.

Claude (web or desktop app)
  1. On this page open ⋯ → Download .md.
  2. Save it as SKILL.md in a folder, zip the folder, then Customize → Skills → + → Create skill → Upload a skill.
  3. Pick the file and Save. Claude shows the name and description and runs a security scan.
  4. Check the skill is switched on.
  5. Start a new chat and describe your job in plain words. The AI follows the skill from there.
ChatGPT or another app
  1. ChatGPT: make a Project and paste it into Instructions.
  2. Neither? Paste it at the top of a new chat — it works for that chat.
Not working?
  • Check which app you pasted it into — the steps above name the right one.
  • Some skills need the paid tier of Claude or ChatGPT.
Step-by-step guide with screenshots · Ask in the forum

Paste into Claude, ChatGPT or Cursor.

Source of /si:memory-status — Memory Health Dashboard

Show the full text104 lines
namedescription
memory-statusMemory 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
# 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:

# 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
1---
2name: "memory-status"
3description: "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."
4---
5 
6# /si:memory-status — Memory Health Dashboard
7 
8Quick overview of your project's memory state across all memory systems.
9 
10## Usage
11 
12```
13/si:memory-status # Full dashboard
14/si:memory-status --brief # One-line summary
15```
16 
17## What It Reports
18 
19### Step 1: Locate all memory files
20 
21```bash
22# Auto-memory directory
23MEMORY_DIR="$HOME/.claude/projects/$(pwd | sed 's|/|%2F|g; s|%2F|/|; s|^/||')/memory"
24 
25# Count lines in MEMORY.md
26wc -l "$MEMORY_DIR/MEMORY.md" 2>/dev/null || echo "0"
27 
28# List topic files
29ls "$MEMORY_DIR/"*.md 2>/dev/null | grep -v MEMORY.md
30 
31# CLAUDE.md
32wc -l ./CLAUDE.md 2>/dev/null || echo "0"
33wc -l ~/.claude/CLAUDE.md 2>/dev/null || echo "0"
34 
35# Rules directory
36ls .claude/rules/*.md 2>/dev/null | wc -l
37```
38 
39### Step 2: Analyze capacity
40 
41| Metric | Healthy | Warning | Critical |
42|--------|---------|---------|----------|
43| MEMORY.md lines | < 120 | 120-180 | > 180 |
44| CLAUDE.md lines | < 150 | 150-200 | > 200 |
45| Topic files | 0-3 | 4-6 | > 6 |
46| Stale entries | 0 | 1-3 | > 3 |
47 
48### Step 3: Quick stale check
49 
50For each MEMORY.md entry that references a file path:
51```bash
52# Verify referenced files still exist
53grep -oE '[a-zA-Z0-9_/.-]+\.(ts|js|py|md|json|yaml|yml)' "$MEMORY_DIR/MEMORY.md" | while read f; do
54 [ ! -f "$f" ] && echo "STALE: $f"
55done
56```
57 
58### Step 4: Output
59 
60```
61📊 Memory Status
62 
63 Auto-Memory (MEMORY.md):
64 Lines: {{n}}/200 ({{bar}}) {{emoji}}
65 Topic files: {{count}} ({{names}})
66 Last updated: {{date}}
67 
68 Project Rules:
69 CLAUDE.md: {{n}} lines
70 Rules: {{count}} files in .claude/rules/
71 User global: {{n}} lines (~/.claude/CLAUDE.md)
72 
73 Health:
74 Capacity: {{healthy/warning/critical}}
75 Stale refs: {{count}} (files no longer exist)
76 Duplicates: {{count}} (entries repeated across files)
77 
78 {{if recommendations}}
79 💡 Recommendations:
80 - {{recommendation}}
81 {{endif}}
82```
83 
84### Brief mode
85 
86```
87/si:memory-status --brief
88```
89 
90Output: `📊 Memory: {{n}}/200 lines | {{count}} rules | {{status_emoji}} {{status_word}}`
91 
92## Interpretation
93 
94- **Green (< 60%)**: Plenty of room. Auto-memory is working well.
95- **Yellow (60-90%)**: Getting full. Consider running `/si:memory-review` to promote or clean up.
96- **Red (> 90%)**: Near capacity. Auto-memory may start dropping older entries. Run `/si:memory-review` now.
97 
98## Tips
99 
100- Run `/si:memory-status --brief` as a quick check anytime
101- If capacity is yellow+, run `/si:memory-review` to identify promotion candidates
102- Stale entries waste space — delete references to files that no longer exist
103- Topic files are fine — Claude creates them to keep MEMORY.md under 200 lines
104 

Discussion

Alternatives

Also in Notes & knowledgeSee all 58 in Operations →