/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
- Run the line below. It pulls the whole folder into
~/.claude/skills/memory-status, including the files SKILL.md points to. - 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-statusFor 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)
- On this page open ⋯ → Download .md.
- Save it as SKILL.md in a folder, zip the folder, then Customize → Skills → + → Create skill → Upload a skill.
- Pick the file and Save. Claude shows the name and description and runs a security scan.
- Check the skill is switched on.
- Start a new chat and describe your job in plain words. The AI follows the skill from there.
ChatGPT or another app
- ChatGPT: make a Project and paste it into Instructions.
- 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.
Paste into Claude, ChatGPT or Cursor.
Source of /si:memory-status — Memory Health Dashboard
Show the full text104 lines
| name | description |
|---|---|
| memory-status | 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
# 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
| 1 | |
| 2 | name "memory-status" |
| 3 | 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." |
| 4 | |
| 5 | |
| 6 | # /si:memory-status — Memory Health Dashboard |
| 7 | |
| 8 | Quick 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 | |
| 22 | # Auto-memory directory |
| 23 | MEMORY_DIR="$HOME/.claude/projects/$(pwd | sed 's|/|%2F|g; s|%2F|/|; s|^/||')/memory" |
| 24 | |
| 25 | # Count lines in MEMORY.md |
| 26 | wc -l "$MEMORY_DIR/MEMORY.md" 2>/dev/null || echo "0" |
| 27 | |
| 28 | # List topic files |
| 29 | ls "$MEMORY_DIR/"*.md 2>/dev/null | grep -v MEMORY.md |
| 30 | |
| 31 | # CLAUDE.md |
| 32 | wc -l ./CLAUDE.md 2>/dev/null || echo "0" |
| 33 | wc -l ~/.claude/CLAUDE.md 2>/dev/null || echo "0" |
| 34 | |
| 35 | # Rules directory |
| 36 | ls .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 | |
| 50 | For each MEMORY.md entry that references a file path: |
| 51 | |
| 52 | # Verify referenced files still exist |
| 53 | grep -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" |
| 55 | done |
| 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 | |
| 90 | Output: `📊 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
Knowledge Graph Memory ServerA basic implementation of persistent memory using a local knowledge graph. This lets Claude remember information about the user across…DaskDistributed computing for larger-than-RAM pandas/NumPy workflows. Use when you need to scale existing pandas/NumPy code beyond memory or across clusters. Best for parallel file processing, distributed ML, integration with existing pandas code. For out-of-core analytics on single machine use vaex; for in-memory speed use polars.PrimeKG Knowledge Graph SkillQuery the Precision Medicine Knowledge Graph (PrimeKG) for multiscale biological data including genes, drugs, diseases, phenotypes, and more.Memory forensicsMaster memory forensics techniques including memory acquisition, process analysis, and artifact extraction using Volatility and related tools. Use when analyzing memory dumps, investigating incidents, or performing malware analysis from RAM captures.
Browse more free Claude skills or everything in Operations.