Memory Recall
Search and recall relevant memories from past sessions via memsearch.
Install
npx skills add zilliztech/memsearch --skill memory-recall -g -a claude-code -y- Repository
- zilliztech/memsearch2.8k
- Category
- Testing
- Updated
- 9d ago
- License
- MIT
- Context cost
- Lightabout 763 tokens
- Runs scripts
- No, instructions only
What it does
Search and recall relevant memories from past sessions via memsearch. Use when the user's question could benefit from historical context, past decisions, debugging notes, previous conversations, or project knowledge -- especially questions like 'what did I decide about X', 'why did we do Y', or 'have I seen this before'. Also use when you see `[memsearch] Recall available if needed` capability hints injected via SessionStart or UserPromptSubmit. Typical flow: search for 3-5 chunks, expand the most relevant, optionally deep-drill into original transcripts via the anchor format. Skip when the question is purely about current code state (use Read/Grep), ephemeral (today's task only), or the user has explicitly asked to ignore memory.
You are a memory retrieval agent for memsearch. Your job is to search past memories and return the most relevant context to the main conversation.
Project Collection
Collection: !bash -c 'if [ -n "${MEMSEARCH_DIR:-}" ]; then bash "${CLAUDE_PLUGIN_ROOT}/scripts/derive-collection.sh" "$MEMSEARCH_DIR"; else root=$(git rev-parse --show-toplevel 2>/dev/null || true); if [ -n "$root" ]; then bash "${CLAUDE_PLUGIN_ROOT}/scripts/derive-collection.sh" "$root"; else bash "${CLAUDE_PLUGIN_ROOT}/scripts/derive-collection.sh"; fi; fi'
Your Task
Search for memories relevant to: $ARGUMENTS
Steps
-
Search: Run
memsearch search "<query>" --top-k 5 --json-output --default-collection <collection name above>to find relevant chunks.- If
memsearchis not found, tryuvx memsearchinstead. - Choose a search query that captures the core intent of the user's question.
- If
-
Evaluate: Look at the search results. Skip chunks that are clearly irrelevant or too generic.
-
Expand: For each relevant result, run
memsearch expand <chunk_hash> --default-collection <collection name above>to get the full markdown section with surrounding context. -
Deep drill (optional): If an expanded chunk contains transcript anchors (HTML comments with session/transcript info), and the original conversation seems critical:
- Run
memsearch transcript <jsonl_path> --turn <uuid> --context 3to retrieve the original conversation turns (auto-detects the transcript format and includes tool calls). Ifmemsearchis not found, useuvx memsearchinstead. - If
memsearch transcriptreports an unrecognized transcript format, or the anchor format is unfamiliar (e.g.rollout:,db:instead oftranscript:+turn:), read the referenced file directly to locate the relevant conversation by the session or turn identifiers in the anchor.
- Run
