Install
1
Install the plugin
$
npx claudepluginhub alirezarezvani/claude-skills --plugin self-improving-agent

Want just this skill?

Add to a custom plugin, then install with one command.

Description

Memory health dashboard showing line counts, topic files, capacity, stale entries, and recommendations.

Tool Access

This skill uses the workspace's default tool permissions.

Skill Content

/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
Stats
Stars5871
Forks688
Last CommitMar 9, 2026
Actions

Similar Skills

cache-components

Expert guidance for Next.js Cache Components and Partial Prerendering (PPR). **PROACTIVE ACTIVATION**: Use this skill automatically when working in Next.js projects that have `cacheComponents: true` in their next.config.ts/next.config.js. When this config is detected, proactively apply Cache Components patterns and best practices to all React Server Component implementations. **DETECTION**: At the start of a session in a Next.js project, check for `cacheComponents: true` in next.config. If enabled, this skill's patterns should guide all component authoring, data fetching, and caching decisions. **USE CASES**: Implementing 'use cache' directive, configuring cache lifetimes with cacheLife(), tagging cached data with cacheTag(), invalidating caches with updateTag()/revalidateTag(), optimizing static vs dynamic content boundaries, debugging cache issues, and reviewing Cache Component implementations.

138.4k