recall-context
Show what memory files are loaded and available in the current session.
@davegoldblattInstall SkillDevelopment
Skill
/recall-status
Show memory system health — word counts, stale entries, hook status, recommendations.
Claude Code
$ npx -y skills add davegoldblatt/total-recall --skill recall-status --agent claude-code
Codex
$ npx skills add davegoldblatt/total-recall --skill recall-status -a codex -y
Cursor
$ npx skills add davegoldblatt/total-recall --skill recall-status -a cursor -y
Gemini CLI
$ npx skills add davegoldblatt/total-recall --skill recall-status -a gemini-cli -y
GitHub Copilot
$ npx skills add davegoldblatt/total-recall --skill recall-status -a github-copilot -y
OpenCode
$ npx skills add davegoldblatt/total-recall --skill recall-status -a opencode -y
Windsurf
$ npx skills add davegoldblatt/total-recall --skill recall-status -a windsurf -y
SKILL.md
recall-status.SKILL.mddescription: Show memory system health — word counts, stale entries, hook status, recommendations.
Show the health and status of the memory system.
What To Do
1. Check Memory System Exists
If CLAUDE.local.md and memory/ directory don't exist:
Memory system not initialized. Run /recall-init to set up.
2. Gather Metrics
**CLAUDE.local.md (Working Memory):**
- Word count (target: under 1500)
- Last updated date
- Number of open loops listed
**Daily Logs (memory/daily/):**
- Total number of files
- Date range (oldest to newest)
- Total size
- Entries in last 7 days
**Registers (memory/registers/):**
- Number of register files
- Total size
- Count entries with `last_verified` dates older than 30 days (stale)
- Count entries marked `[superseded]`
**Archive (memory/archive/):**
- Number of files
- Total size
**Entry IDs (memory/.recall/metadata.json):**
- Count entries with `^tr` IDs (tagged) vs without (untagged) across managed files (CLAUDE.local.md, registers, archive)
- Count metadata.json entries total
- Count pinned entries
- Count snoozed entries (with active snooze)
- Count superseded entries
**Hooks:**
- Check .claude/settings.json or .claude/settings.local.json for SessionStart and PreCompact hook config
3. Display Status
Memory System Status
────────────────────
Working Memory: [N] words ([N]% of 1500 limit)
(CLAUDE.local.md) Last updated: [date]
Open loops: [N]
Protocol: .claude/rules/total-recall.md ✓
Schema: memory/SCHEMA.md ✓
Daily logs: [N] files, [size] total
Range: [oldest] → [newest]
Last 7 days: [N] entries
Registers: [N] files, [size] total
Stale entries (>30 days): [N]
Superseded entries: [N]
Archive: [N] files, [size] total
Entry IDs: [N] tagged / [M] untagged
metadata.json: [N] entries
Pinned: [N], Snoozed: [N], Superseded: [N]
Hooks:
SessionStart [✓ configured / ✗ not configured]
PreCompact [✓ configured / ✗ not configured]4. Recommendations
Based on metrics, suggest actions:
- If working memory > 1200 words: "Working memory approaching limit — consider archiving stale items"
- If stale entries > 0: "Run /recall-maintain to verify [N] stale entries"
- If no daily log in 3+ days: "No recent daily logs — memory capture may have gaps"
- If open loops > 5: "Consider reviewing open loops — some may be resolved"
- If registers are empty: "Registers are empty — use /recall-promote to populate from daily logs"
- If working memory stale (7+ days): "Working memory may be stale — review for accuracy"
- If hooks not configured: "Consider configuring SessionStart/PreCompact hooks for automated memory loading and flush"
- If untagged entries > 0: "Run /recall-init-ids to tag [N] untagged entries (required for /recall-maintain)"
- If superseded entries in metadata > 0: "Run /recall-maintain to clean up [N] superseded entries"
Read more
description: Show memory system health — word counts, stale entries, hook status, recommendations.
Show the health and status of the memory system.
What To Do
1. Check Memory System Exists
If CLAUDE.local.md and memory/ directory don't exist:
Memory system not initialized. Run /recall-init to set up.
2. Gather Metrics
**CLAUDE.local.md (Working Memory):**
- Word count (target: under 1500)
- Last updated date
- Number of open loops listed
**Daily Logs (memory/daily/):**
- Total number of files
- Date range (oldest to newest)
- Total size
- Entries in last 7 days
**Registers (memory/registers/):**
- Number of register files
- Total size
- Count entries with `last_verified` dates older than 30 days (stale)
- Count entries marked `[superseded]`
**Archive (memory/archive/):**
- Number of files
- Total size
**Entry IDs (memory/.recall/metadata.json):**
- Count entries with `^tr` IDs (tagged) vs without (untagged) across managed files (CLAUDE.local.md, registers, archive)
- Count metadata.json entries total
- Count pinned entries
- Count snoozed entries (with active snooze)
- Count superseded entries
**Hooks:**
- Check .claude/settings.json or .claude/settings.local.json for SessionStart and PreCompact hook config
3. Display Status
Memory System Status
────────────────────
Working Memory: [N] words ([N]% of 1500 limit)
(CLAUDE.local.md) Last updated: [date]
Open loops: [N]
Protocol: .claude/rules/total-recall.md ✓
Schema: memory/SCHEMA.md ✓
Daily logs: [N] files, [size] total
Range: [oldest] → [newest]
Last 7 days: [N] entries
Registers: [N] files, [size] total
Stale entries (>30 days): [N]
Superseded entries: [N]
Archive: [N] files, [size] total
Entry IDs: [N] tagged / [M] untagged
metadata.json: [N] entries
Pinned: [N], Snoozed: [N], Superseded: [N]
Hooks:
SessionStart [✓ configured / ✗ not configured]
PreCompact [✓ configured / ✗ not configured]4. Recommendations
Based on metrics, suggest actions:
- If working memory > 1200 words: "Working memory approaching limit — consider archiving stale items"
- If stale entries > 0: "Run /recall-maintain to verify [N] stale entries"
- If no daily log in 3+ days: "No recent daily logs — memory capture may have gaps"
- If open loops > 5: "Consider reviewing open loops — some may be resolved"
- If registers are empty: "Registers are empty — use /recall-promote to populate from daily logs"
- If working memory stale (7+ days): "Working memory may be stale — review for accuracy"
- If hooks not configured: "Consider configuring SessionStart/PreCompact hooks for automated memory loading and flush"
- If untagged entries > 0: "Run /recall-init-ids to tag [N] untagged entries (required for /recall-maintain)"
- If superseded entries in metadata > 0: "Run /recall-maintain to clean up [N] superseded entries"
Stats
202
Stars
14
Forks
Quiet
Maintenance
Shell
Language
Last commit
Created
Ships withdavegoldblatt-recall
A memory system for Claude Code that remembers what matters and forgets what doesn't.
20210 skills
Stars on GitHub
Momentum
- stars in total
- 202
Other skills on davegoldblatt-recall.
@davegoldblattInstall Skillrecall-forget
Mark memory entries as superseded. Preserves history, does not delete.
@davegoldblattInstall Skillrecall-init-ids
Add durable IDs to memory entries. Required before /recall-maintain can run.
@davegoldblattInstall Skillrecall-init
Scaffold the Total Recall memory directory structure in this project.
@davegoldblattInstall Skillrecall-maintain
Pressure-based memory cleanup. Demotes, archives, or pins entries when working memory exceeds budget.
@davegoldblattInstall SkillMore skills from other plugins.
Auto-invoked
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
@obraInstall Skillask-matt
Ask which skill or flow fits your situation. A router over the skills in this repo.
@mattpocockInstall SkillAuto-invoked
Questions about recall-status.
- Which coding agents can use recall-status?
- recall-status installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.