Memory status
Skill alirezarezvani/claude-skills/engineering-team/self-improving-agent/skills/memory-status
345 Claude Code skills & agent skills & plugins (30+ Agents, 70+ custom commands, 330+ skills, customizable references, scripts)for Claude Code, Codex, Gemini CLI, Cursor, and 8 more coding agents β engineering, marketing, product, compliance, C-level advisory, research, business operations, commercial & finance, and your daily productivity skills.
npx -y skills add alirezarezvani/claude-skills --skill memory-statusAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
What its author says it does
Copied from the file, not written here
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.
SKILL.md
2.8 KB, as published. Nobody here has run it
/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-reviewto promote or clean up. - Red (> 90%): Near capacity. Auto-memory may start dropping older entries. Run
/si:memory-reviewnow.
Tips
- Run
/si:memory-status --briefas a quick check anytime - If capacity is yellow+, run
/si:memory-reviewto 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