memory-recall

Solid

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] Memory available` 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.

AI & Automation 1,872 stars 175 forks Updated 2 days ago MIT

Install

View on GitHub

Quality Score: 89/100

Stars 20%
100
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

You are performing memory retrieval for memsearch. Search past memories and return the most relevant context to the current conversation. ## Project Collection Determine the collection name by running: ``` bash -c 'if [ -n "${MEMSEARCH_DIR:-}" ]; then bash __INSTALL_DIR__/scripts/derive-collection.sh "$MEMSEARCH_DIR"; else root=$(git rev-parse --show-toplevel 2>/dev/null || true); if [ -n "$root" ]; then bash __INSTALL_DIR__/scripts/derive-collection.sh "$root"; else bash __INSTALL_DIR__/scripts/derive-collection.sh; fi; fi' ``` ## Steps 1. **Search**: Run `memsearch search "<query>" --top-k 5 --json-output --collection <collection name from above>` to find relevant chunks. - If `memsearch` is not found, try `uvx memsearch` instead. - Choose a search query that captures the core intent of the user's question. 2. **Evaluate**: Look at the search results. Skip chunks that are clearly irrelevant or too generic. 3. **Expand**: For each relevant result, get the full context using one of these methods: - **Primary**: Run `memsearch expand <chunk_hash> --collection <collection name from above>` to get the full markdown section. - **Fallback** (if expand fails with a lock/permission error due to sandbox): Read the source file directly. The search results include `source` (file path) and `start_line`/`end_line` — use `cat <source_file>` or read the relevant line range to get the full context. This avoids the Milvus lock file issue. 4. **Deep drill (optional)**: If a...

Details

Author
zilliztech
Repository
zilliztech/memsearch
Created
3 months ago
Last Updated
2 days ago
Language
Python
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category