New: Earn 20% as an AgentAlley affiliate. Share your link and earn on every sale you refer. Join now New: Earn 20% as an affiliate. Join now

Memory health dashboard showing line counts, topic files

/si:memory-status — Memory Health Dashboard

by alirezarezvani · MIT license · ★ 26,349 on GitHub · updated Aug 30

/si:memory-status — Memory Health Dashboard cover

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.

---
name: "memory-status"
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."
---

# /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

Overview

Quick overview of your project's memory state across all memory systems.

Manual install (npx, ZIP)
Claude Codenpx skills add alirezarezvani/claude-skills --skill memory-status -g -a claude-code
Claude Code (manual)mkdir -p ~/.claude/skills && curl -sL https://codeload.github.com/alirezarezvani/claude-skills/tar.gz/19392f7a0826 \ | tar -xz -C ~/.claude/skills --strip-components=4 claude-skills-19392f7a0826/engineering-team/self-improving-agent/skills/memory-status
Windows (PowerShell)New-Item -ItemType Directory -Force "$HOME\.claude\skills" | Out-Null; Invoke-WebRequest "https://m.agentalley.io/zip/399dd9e36431d514a6b4/memory-status.zip" -OutFile "$env:TEMP\memory-status.zip"; Expand-Archive "$env:TEMP\memory-status.zip" -DestinationPath "$HOME\.claude\skills" -Force
Claude.ai / desktopDownload the ZIP and upload it under Settings → Capabilities → Skills.
Codex, Cursor, other agentsPoint them at SKILL.md. The other files are plain text.

Connects with Agent Alley MCP · agentalley.io/mcp

Files included

  • SKILL.md2.8 KB
Read the files here
alirezarezvani/19392f71 file
SKILL.md
Show the full text104 lines

/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-review to promote or clean up.
  • Red (> 90%): Near capacity. Auto-memory may start dropping older entries. Run /si:memory-review now.

Tips

  • Run /si:memory-status --brief as a quick check anytime
  • If capacity is yellow+, run /si:memory-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
1---
2name: "memory-status"
3description: "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 
8Quick 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```bash
22# Auto-memory directory
23MEMORY_DIR="$HOME/.claude/projects/$(pwd | sed 's|/|%2F|g; s|%2F|/|; s|^/||')/memory"
24 
25# Count lines in MEMORY.md
26wc -l "$MEMORY_DIR/MEMORY.md" 2>/dev/null || echo "0"
27 
28# List topic files
29ls "$MEMORY_DIR/"*.md 2>/dev/null | grep -v MEMORY.md
30 
31# CLAUDE.md
32wc -l ./CLAUDE.md 2>/dev/null || echo "0"
33wc -l ~/.claude/CLAUDE.md 2>/dev/null || echo "0"
34 
35# Rules directory
36ls .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 
50For each MEMORY.md entry that references a file path:
51```bash
52# Verify referenced files still exist
53grep -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"
55done
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 
90Output: `📊 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 
View all files on GitHub →

Details

Updated
Aug 30, 2026
License
MIT
Stars on the repo
★ 26,349
Checked
Source
alirezarezvani/claude-skills ↗
Creator
alirezarezvani · 363 listings
View creator

Similar skills

See all →
SkillExport the Obsidian wiki's knowledge graph to structuredWiki Export — Knowledge Graph ExportAr9av/obsidian-wiki · by Ar9avExport the Obsidian wiki's knowledge graph to structured formats for use in external tools. Use this skill when the user says "export wiki", "export graph", "export to JSON", "export to Gephi", export to Neo4j", "export to Postgres", "export to SQL", "graphml", "visualize wiki", knowledge graph export", "export to OKF", "OKF bundle", "open knowledge format", export as markdown bundle", or wants to use their wiki data in another tool. Outputs graph.json, graph.graphml, cypher.txt (Neo4j), postgres.sql (Postgres), and graph.html (interactive browser visualization) into a wiki-export/ directory at the vault root, plus an optional OKF (Open Knowledge Format) markdown bundle under wiki-export/okf/.★ 3.5k GitHub starsSkillImport a wiki knowledge graph into the current vaultWiki Import — Reconstruct Pages from an ExportAr9av/obsidian-wiki · by Ar9avImport a wiki knowledge graph into the current vault — either from a graph.json export file (stubs) or from an OKF (Open Knowledge Format) markdown bundle (full page bodies). Use this skill when the user says "import wiki", "import from export", "load graph.json", import vault", "import OKF bundle", "import OKF", "load OKF", "import markdown bundle", /wiki-import", or wants to transfer pages from one vault to another using the output of wiki-export.★ 3.5k GitHub starsSkillYour team's shared, AI-ready knowledge base/company-brain — Team-shared AI-ready knowledge basecoreyhaines31/makerskills · by coreyhaines31Your team's shared, AI-ready knowledge base — people, companies, meetings, SOPs, and decisions structured so an agent can answer on your team's behalf. Team-scope sibling to second-brain. Modes — capture, compile (wiki pages + INDEX.md), query (trust-weighted, saved to outputs/), review (verify / deprecate / supersede stale captures), lint, connect, search. Structured raw dirs (people/, companies/, meetings/, sops/, decisions/, customer-language/, sales-objections/). Every capture stamps author, timestamp, and trust status. Optional sync from call transcripts, Slack/email exports, CRM. Vault at ${COMPANY_BRAIN_VAULT:-$HOME/Documents/CompanyBrain}/. Triggers on "/company-brain," "/cb," "capture this into the team brain," "log this meeting," "save this SOP," "compile the company wiki," "query the team brain," "what does the team know about X," "review the company brain," "lint the company brain," "who's the internal expert on X.★ 855 GitHub starsSkillGive Claude a permanent, searchable long-term memoryAI Brain — persistent memory for Claude via ObsidianOotto-AI/claude-content-skills · by Ootto-AIGive Claude a permanent, searchable long-term memory using an Obsidian vault as the store. At the end of a session, summarize what mattered and save it as a Markdown note in your "AI Brain" vault; at the start of a session (or on demand), read back only the relevant past notes. Local markdown you own — connected via the Filesystem MCP. Trigger with "wrap up", "save this session", or "remember this".★ 139 GitHub starsSkillFind prior Claude Code and Codex sessions with an indexed/recall: session memory engineParcha-ai/parcha-skills · by Parcha-aiFind prior Claude Code and Codex sessions with an indexed local search engine, then continue the work, repeat it with fresh inputs, or distill it into a skill. Runs from Claude Code, Codex, or pi; the current index covers Claude Code and Codex transcripts. Use when the user names Recall, says "find that conversation where…", "what did we do last time about…", "continue what we did yesterday on X", "what did codex do on this branch", "turn what we did about Y into a skill", or "remember when you…". Not for searching code (use grep on the repo) or for facts already in MEMORY.md.★ 62 GitHub starsMCPA basic implementation of persistent memory using a localKnowledge Graph Memory Servermodelcontextprotocol/servers · by modelcontextprotocolA basic implementation of persistent memory using a local knowledge graph. This lets Claude remember information about the user across…★ 90.5k GitHub stars

More from alirezarezvani

SkillResume a paused experiment/ar:ar-resume — Resume Experimentalirezarezvani/claude-skills · by alirezarezvaniResume a paused experiment. Checkout the experiment branch, read results history, continue iterating. Use when the user runs /ar:ar-resume or asks to pick up a previously started autoresearch experiment.★ 26.3k GitHub starsSkillShow experiment dashboard with results, active loops/ar:ar-status — Experiment Dashboardalirezarezvani/claude-skills · by alirezarezvaniShow experiment dashboard with results, active loops, and progress. Use when the user runs /ar:ar-status or asks how an autoresearch experiment is going.★ 26.3k GitHub starsSkillStart an autonomous experiment loop with user-selected/ar:loop — Autonomous Experiment Loopalirezarezvani/claude-skills · by alirezarezvaniStart an autonomous experiment loop with user-selected interval (10min, 1h, daily, weekly, monthly). Uses CronCreate for scheduling. Use when the user runs /ar:loop or asks to run an autoresearch experiment continuously on a schedule.★ 26.3k GitHub starsSkillRun a single experiment iteration/ar:run — Single Experiment Iterationalirezarezvani/claude-skills · by alirezarezvaniRun a single experiment iteration. Edit the target file, evaluate, keep or discard. Use when the user runs /ar:run or asks for one manual autoresearch iteration.★ 26.3k GitHub starsSkillSet up a new autoresearch experiment interactively/ar:setup — Create New Experimentalirezarezvani/claude-skills · by alirezarezvaniSet up a new autoresearch experiment interactively. Collects domain, target file, eval command, metric, direction, and evaluator. Use when the user runs /ar:setup or asks to start optimizing a file with the autoresearch loop.★ 26.3k GitHub starsSkill/cs:boardroom <brief/cs:boardroom — Multi-Role Boardroom Deliberationalirezarezvani/claude-skills · by alirezarezvani/cs:boardroom <brief> — 6-phase multi-role deliberation across the C-suite with Phase 2 isolation, critic pre-screen, and synthesis. Outputs a board memo. Use when a decision spans multiple executive domains — e.g. a pricing change touching finance, positioning, and product, or a raise-vs-cut runway call.★ 26.3k GitHub stars