status
alirezarezvani/claude-skills
Memory health dashboard showing capacity, stale entries, and recommendations for agent memory systems.
What is status?
Displays a quick overview of your project's memory state across all memory systems, including line counts, topic files, capacity utilization, and stale entries. Use this when you need to check how full or healthy the agent memory is, or when the user runs /si:status.
- Reports line counts in MEMORY.md, CLAUDE.md, and topic files
- Analyzes capacity against healthy/warning/critical thresholds
- Detects stale file references that no longer exist
- Identifies duplicate entries across memory files
- Provides actionable recommendations when memory is getting full
- Offers brief one-line summary mode with --brief flag
How to install status
npx skills add https://github.com/alirezarezvani/claude-skills --skill statusHow to use status
- 1.Run /si:status to display the full memory health dashboard
- 2.Run /si:status --brief for a one-line summary
- 3.Review the capacity bar and health status (green/yellow/red)
- 4.If yellow or red, run /si:review to clean up or promote entries
- 5.Delete stale entries that reference files no longer in the project
Use cases
- Check memory capacity before starting a new project phase
- Identify when to run /si:review to clean up or promote entries
- Monitor stale references that are wasting memory space
- Get a quick health status during active development
- Determine if auto-memory is approaching its 200-line limit
- Developers using Claude Code or Cursor with memory systems
- Teams managing project context across multiple sessions
- Anyone needing to monitor and optimize agent memory health
status FAQ
Green (< 60%) means plenty of room. Yellow (60-90%) means getting full and you should consider cleanup. Red (> 90%) means near capacity and auto-memory may start dropping older entries.
Stale entries are references to files that no longer exist in your project. They waste memory space and should be deleted.
Run it anytime as a quick check, especially before starting new work or if you suspect memory is getting full. Use --brief for a quick one-line summary.
Run /si:review to identify promotion candidates and clean up old entries. Delete stale references and consider archiving less-used information.
No, topic files are fine. Claude creates them automatically to keep MEMORY.md under 200 lines. More than 6 topic files may indicate the memory needs reorganization.
Full instructions (SKILL.md)
Source of truth, from alirezarezvani/claude-skills.
name: "status" description: "Memory health dashboard showing line counts, topic files, capacity, stale entries, and recommendations. Use when the user runs /si:status or asks how full or healthy the agent memory is."
/si:status — Memory Health Dashboard
Quick overview of your project's memory state across all memory systems.
Usage
/si:status # Full dashboard
/si: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: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:reviewto promote or clean up. - Red (> 90%): Near capacity. Auto-memory may start dropping older entries. Run
/si:reviewnow.
Tips
- Run
/si:status --briefas a quick check anytime - If capacity is yellow+, run
/si: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
Related skills
More from alirezarezvani/claude-skills and the wider catalog.

stress-test
Break business assumptions before the market does—stress-test revenue, market size, moats, and execution plans.

tdd-guide
Test-driven development skill for writing unit tests, generating test fixtures and mocks, analyzing coverage gaps, and guiding red-green-refactor workflows across Jest, Pytest, JUnit, Vitest, and Mocha. Use when the user asks to write tests, improve test coverage, practice TDD, generate mocks or stubs, or mentions testing frameworks like Jest, pytest, or JUnit.

tech-stack-evaluator
Technology stack evaluation and comparison with TCO analysis, security assessment, and ecosystem health scoring. Use when comparing frameworks, evaluating technology stacks, calculating total cost of ownership, assessing migration paths, or analyzing ecosystem viability.

testrail
Sync Playwright tests bidirectionally with TestRail test management.

ui-design-system
UI design system toolkit for Senior UI Designer including design token generation, component documentation, responsive design calculations, and developer handoff tools. Use when creating design systems, generating design tokens, maintaining visual consistency, or facilitating design-dev collaboration and developer handoff.

ux-researcher-designer
UX research and design toolkit for Senior UX Designer/Researcher including data-driven persona generation, journey mapping, usability testing frameworks, and research synthesis. Use when conducting user research, creating personas, mapping user journeys, planning usability tests, or validating designs.