Skill

What To Do

Lists loaded memory files and scans disk for available memory context (schema, daily logs, registers, archive) in Claude Code sessions. Highlights gaps and suggests actions.

developer-tools

npx claudepluginhub davegoldblatt/total-recall

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Show what memory context is currently available in this session.

SKILL.md

Similar Skills

What To Do

181

Shows memory system health: working memory word counts/open loops, daily logs/registers/archive stats, stale/superseded entries, hooks status, with recommendations.

recall

mind

174

Search and manage Claude's persistent memory in a portable .claude/mind.mv2 file using Node.js scripts for semantic queries, Q&A, stats, and timelines. Useful for recalling past decisions, solutions, and code patterns across sessions.

mind

Manage Memory

Organizes, extracts, prunes, and verifies Claude Code persistent memory files: MEMORY.md index, topic extraction, staleness detection, accuracy checks. Use near 200-line limit, after insights, or project changes.

agent-almanac

Stats

Stars181

Forks8

Last CommitFeb 5, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Memory Context — Current Session ───────────────────────────────── Auto-loaded (deterministic): .claude/rules/total-recall.md ✓ Protocol rules CLAUDE.local.md ✓ Working memory ([N] words) On disk: memory/SCHEMA.md ✓ Protocol docs memory/daily/[today].md ✓ [N] entries memory/daily/[yesterday].md ✓ [N] entries memory/registers/open-loops.md ✓ [N] active items Available registers: people.md [N] entries projects.md [N] entries decisions.md [N] entries preferences.md [N] entries tech-stack.md [N] entries Archive: [N] files Hooks: SessionStart [configured/not configured] PreCompact [configured/not configured]

Show what memory context is currently available in this session.

What To Do

1. Check What's Auto-Loaded

These files load automatically via Claude Code's native mechanisms:

Via .claude/rules/ (deterministic):

.claude/rules/total-recall.md — memory protocol

Via CLAUDE.local.md (deterministic):

CLAUDE.local.md — working memory

2. Check What Exists On Disk

Read and report on what memory files are present:

Schema:

memory/SCHEMA.md — exists?

Daily Logs:

Today's log (memory/daily/[today].md) — exists? Entry count?
Yesterday's log — exists?

Registers:

List all .md files in memory/registers/ with entry counts

Archive:

List files in memory/archive/

3. Display

Memory Context — Current Session
─────────────────────────────────

Auto-loaded (deterministic):
  .claude/rules/total-recall.md   ✓  Protocol rules
  CLAUDE.local.md                 ✓  Working memory ([N] words)

On disk:
  memory/SCHEMA.md                ✓  Protocol docs
  memory/daily/[today].md         ✓  [N] entries
  memory/daily/[yesterday].md     ✓  [N] entries
  memory/registers/open-loops.md  ✓  [N] active items

Available registers:
  people.md           [N] entries
  projects.md         [N] entries
  decisions.md        [N] entries
  preferences.md      [N] entries
  tech-stack.md       [N] entries

Archive: [N] files

Hooks:
  SessionStart    [configured/not configured]
  PreCompact      [configured/not configured]

4. Highlight Gaps

If expected files are missing:

Missing:
  ✗ CLAUDE.local.md — run /recall-init to create
  ✗ No daily log for today — will be created on first /recall-write

5. Quick Actions

Use /recall-search <query> to pull context from any tier.
Use /recall-status for memory health metrics.