Status
Run a memory health dashboard on MEMORY.md, CLAUDE.md, and rules so long-running agent projects stay under capacity limits.
Overview
status is a journey-wide agent skill that surfaces MEMORY.md, CLAUDE.md, and rules capacity and stale-entry signals—usable whenever a solo builder needs to audit agent memory before committing to more automated work.
Install
npx skills add https://github.com/alirezarezvani/claude-skills --skill statusWhat is this skill?
- Full or --brief dashboard for auto-memory, CLAUDE.md, and .claude/rules
- Capacity table with healthy/warning/critical thresholds for MEMORY.md and CLAUDE.md line counts
- Topic file count guidance (0–3 healthy, >6 critical)
- Stale entry detection by verifying file paths referenced in MEMORY.md still exist
- Structured 4-step workflow: locate files, analyze capacity, stale check, formatted output
- Capacity table with 4 metrics: MEMORY.md lines, CLAUDE.md lines, topic files, stale entries
- Healthy thresholds: MEMORY.md <120 lines, CLAUDE.md <150 lines
Adoption & trust: 1.5k installs on skills.sh; 17.5k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
Your Claude project memory files have grown without visibility into line limits, topic sprawl, or references to files that no longer exist.
Who is it for?
Solo builders running multi-week Claude Code repos with auto-memory, custom rules, and recurring /si:status hygiene checks.
Skip if: One-off prompts with no persistent MEMORY.md or teams that manage knowledge only in external wikis without Claude memory files.
When should I use this skill?
When you need a memory health dashboard, line counts, topic file inventory, or stale entry recommendations for Claude project memory.
What do I get? / Deliverables
You get a structured memory health report with severity bands and stale paths so you can trim or reorganize before the next coding sprint.
- Memory status dashboard or --brief summary
- Stale path list when references break
- Capacity severity recommendations
Recommended Skills
Journey fit
Useful at every journey phase - explore requirements and options before committing to a direction.
Where it fits
Check whether bloated MEMORY.md will crowd out scope docs before you lock MVP boundaries.
Run --brief after merging large features to see if topic file count crossed the warning band.
Scan stale path references after a refactor so review prompts do not cite deleted modules.
Monthly dashboard pass to split topic files before MEMORY.md hits the critical line threshold.
Audit memory before encoding new marketing or support playbooks into CLAUDE.md.
How it compares
Use instead of manually wc -l and grep across memory paths—this skill packages the thresholds and reporting ritual.
Common Questions / FAQ
Who is status for?
Solo and indie builders who persist project context in Claude auto-memory, CLAUDE.md, and .claude/rules and need a quick health readout.
When should I use status?
Use it during Operate iterate before big refactors, after deleting modules, when sessions feel bloated, or in Validate scope when memory size affects what the agent can load; also anytime you want /si:status --brief before a long Build or Ship push.
Is status safe to install?
It reads local project and user Claude paths; confirm scope on the Security Audits panel on this page and avoid running stale checks on paths you do not intend to expose to the agent.
SKILL.md
READMESKILL.md - Status
# /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 ```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: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:review` to promote or clean up. - **Red (> 90%)**: Near capacity. Auto-memory may start dropping older entries. Run `/si:review` now. ## Tips - Run `/si:status --brief` as a quick check anytime - If capacity is yellow+, run `/si: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