Complete AI Training
Sign inBecome a member

Your job's AI kit

Get your AI kit

Tell us who you are and what you do. We show you your kit right away and email you the link: skills, prompts, AI agents, MCP servers and courses for your job.

500+ jobs ready, and we make a kit for any other job. No payment needed to look.

Skill Β· Office Productivity

Status

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.

Agency SkillsLicense: MITAdded Sep 29, 2026
Use it in my AI

How to use it

  1. Start your plan and connect your AI once
  2. Add the skill to your AI, one time only: press Copy skill and paste it into your AI's instructions: a project in ChatGPT, Claude or Grok, a Gem in Gemini, an agent in Microsoft 365 Copilot, or a rule in Cursor. It stays there for every new chat. In Kimi, paste it at the start of a new chat.
  3. Ask for the task in your own words, or say it directly:
Use the Status skill to help me with this.
SKILL.md2 files in this skill

/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

MetricHealthyWarningCritical
MEMORY.md lines< 120120-180> 180
CLAUDE.md lines< 150150-200> 200
Topic files0-34-6> 6
Stale entries01-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: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