Stats
Actions
Tags
From recall
Detects context loss in conversations, proactively suggests /recall commands, shares highlights across sessions, flags findings, and translates natural language to recall operations for the recall plugin.
How this skill is triggered — by the user, by Claude, or both
Slash command
/recall:recall-assistantThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
You have access to the **recall plugin** — a cross-session, cross-project conversation recall system backed by SQLite. This skill guides you on when and how to use it proactively.
You have access to the recall plugin — a cross-session, cross-project conversation recall system backed by SQLite. This skill guides you on when and how to use it proactively.
IMPORTANT: All behaviors below are gated. Before taking any proactive action described here, check whether the user has enabled this skill by verifying skill_enabled is true. If not enabled, do nothing — the user interacts with the plugin only via explicit /recall commands.
When skill_enabled is true, watch for signals that you have lost earlier conversation context. The user may configure which signal categories are active via detection_signals (default: all three).
Watch for the user saying things like:
When you detect these: suggest a specific recall command based on what the user is looking for.
Example:
I may have lost context on the warp divergence discussion. Let me check — I'll run
/recall search "warp divergence"to recover what we covered.
Watch for your own behavior indicating context loss:
When you detect these: pause, acknowledge the potential gap, and suggest a recall command before continuing.
Example:
Before I answer — I have a feeling we may have covered this earlier and I may have lost that context. Let me check
/recall last10to make sure I'm not repeating myself.
Watch for environmental cues:
When you detect these: proactively suggest recovering context before proceeding with complex work.
Example:
This session has been going a while and context may have been compacted. Want me to run
/recall searchon the current topic to make sure I haven't lost anything important?
When skill_enabled is true and you know the session has active connections to other sessions:
You should consider highlighting a finding when you:
Do NOT suggest highlighting for:
Suggest the highlight and wait for confirmation:
This warp shuffle fix could be useful to your other sessions working on kernel optimization. Want me to flag it? I'd run:
/recall highlight "warp shuffle eliminates divergence in reduction kernel"
Run the highlight command directly, then briefly note what you did:
Flagged for connected sessions: "warp shuffle eliminates divergence in reduction kernel"
When skill_enabled is true, translate natural language about other sessions into recall commands.
When the user says things like:
Suggest the appropriate connect command:
If the user provides a session ID:
I'll connect to that session. Running:
/recall connect abc123 "kernel optimization"
If the user doesn't provide a session ID:
Want me to connect to the most recent active session in this project?
/recall connect --latest "kernel optimization"
Never auto-run connect or disconnect. Always suggest and wait for the user to confirm.
When skill_enabled is true and the session has active connections:
You have active connections — it might be worth checking
/recall inboxfor any relevant findings from your other sessions before we dive in.
Never auto-run inbox. Always suggest.
When suggesting recall commands, use these:
/recall — interactive menu/recall last5 / /recall last10 — recent exchanges/recall search <keyword> — search current session/recall search <keyword> --all — search all sessions in project/recall search <keyword> --global — search across all projects/recall search <keyword> --project <name> — search specific project/recall around <time> — exchanges around a time/recall sessions — list all sessions/recall sessions --all — list sessions across all projects/recall sessions --project <name> — list sessions in specific project/recall session <id> last10 — browse a past session/recall stats — storage statistics/recall tag <name> — tag current session/recall tags — list all tags/recall search --tag <name> — find by tag/recall highlight "summary" — flag a finding/recall connect <session-id> "topic" — watch a session/recall connect --latest "topic" — watch most recent active session/recall disconnect <session-id> — stop watching/recall inbox — view new highlights from connections/recall config skill_enabled true — enable this skill/recall config detection_signals explicit,behavioral,temporal — configure which signals are active/recall config auto_run_highlight true — auto-flag findings without asking/recall config check_mode decay — enable decay-based polling/recall config delivery_mode inject — auto-inject highlights as system messages/recall config auto_highlight true — enable heuristic highlight detectionnpx claudepluginhub bledden/claude-recall-pluginRoutes recall intents (e.g., "思い出して", "resume", "続き") to the correct memory path: resume pack, decisions/patterns, checkpoint-bridge, session list, or keyword search. Useful for resuming work or retrieving past context.
Recalls, searches, and analyzes past conversations using recent_chats.py, search_conversations.py, and lenses like retro, find-gaps, extract-decisions for context restoration and retrospectives.