memory-recall
"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 p
SKILL.mdskills/memory-recall/SKILL.md
GitHubYou are a memory retrieval agent for memsearch. Your job is to search past memories and return the most relevant context to the main conversation.
OpenCode execution note
OpenCode skills do not automatically evaluate Claude Code-style shell interpolation such as !...in this document. Run shell commands explicitly with the available terminal tool, inspect their output, and do not assumeCLAUDE_PLUGIN_ROOT` exists. If the original plugin scripts are absent, report that dependency rather than guessing a path.
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
Return results: Output a curated summary of the most relevant memories. Be concise — only include information that is genuinely useful for the user's current question.
When unsure what to search
If the user's question is vague or you can't form a concrete search query, explore the raw markdown first — it is the source of truth for memory:
MDIR="${MEMSEARCH_DIR:-$(git rev-parse --show-toplevel 2>/dev/null || pwd)/.memsearch}"; ls -t "$MDIR/memory/" | head -10— recent daily logsMDIR="${MEMSEARCH_DIR:-$(git rev-parse --show-toplevel 2>/dev/null || pwd)/.memsearch}"; grep -h "^## " "$MDIR/memory/"*.md | sort -u | tail -40— session headings across all daysMDIR="${MEMSEARCH_DIR:-$(git rev-parse --show-toplevel 2>/dev/null || pwd)/.memsearch}"; cat "$MDIR/memory/<YYYY-MM-DD>.md"— read a specific day
Once a concrete topic jumps out, go back to memsearch search with a specific query.
Output Format
Organize by relevance. For each memory include:
- The key information (decisions, patterns, solutions, context)
- Source reference (file name, date) for traceability
If nothing relevant is found, simply say "No relevant memories found."