memory-recalllisted
Install: claude install-skill shandar/memory-map
# Memory Recall
Load and intelligently summarise stored memory so a session can pick up exactly where the
last one ended.
Works in **claude.ai** (reads via `memory_user_edits` view) and **Claude Code**
(reads `~/.claude/memory.md`). Detected automatically.
---
## Scope
**Check first (Claude Code).** Before anything else, run `test -f STATUS.md` in the cwd. If it
exists and the request was an open "where did I/we leave off", "catch me up", or "what was I
doing", switch to the memory-map skill in READ mode and stop here.
- No project named and no `STATUS.md` in the cwd → this skill: the cross-project briefing.
- A project is named, or the cwd has a `STATUS.md` → memory-map READ mode restores that project.
- When this skill runs anyway (for example "what do you remember") in a Claude Code folder that
has a `STATUS.md`, mention it in the briefing so the user can ask for the full project restore.
---
## Step 0 — Detect environment
| Signal | Environment | Load |
|--------|-------------|------|
| `memory_user_edits` tool is available | claude.ai | `references/claude-ai.md` |
| Not available / running in terminal | Claude Code | `references/claude-code.md` |
Read the relevant reference file before proceeding.
---
## Core Protocol
### Step 1 — Read the full memory store
Use the environment-appropriate read command (see references) to fetch all stored entries.
### Step 2 — Sort entries by relevance to the current request
Memory entries fall into priority tiers:
**Ti