memory-recall SKILL.md skillA
memory-recall from zilliztech/memsearch is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add zilliztech/memsearch/memory-recall@git:20260908.4ad9ee4Pins git:20260908.4ad9ee4 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- zilliztech/memsearch
- Path
plugins/claude-code/skills/memory-recall/SKILL.md- Versions recorded
- 5
- Latest version
- git:20260908.4ad9ee4, committed Sep 8, 2026
- First version recorded
- Apr 16, 2026
- Size
- 3,880 bytes
- Repository stars
- 2,816
- License
- MIT
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…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
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
1. **Search**: Run `memsearch search "<query>" --top-k 5 --json-output --default-collection <collection name 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, run `memsearch expand <chunk_hash> --default-collection <collection name above>` to get the full markdown section with surrounding context.
…Read the whole file at its exact version.
How to install
mdr add zilliztech/memsearch/memory-recall@sha256:b9385e5c3d8c35eaThe line at the top of this page pins the label git:20260908.4ad9ee4, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_qrx2yfngyl5g6nzp)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Apr 16, 2026 and Sep 8, 2026, about one every 36 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260908.4ad9ee4 latest | 2026-09-08 | 4ad9ee4 | 3,880 B | A | view · diff |
| git:20260907.b82fc0a | 2026-09-07 | b82fc0a | 3,864 B | A | view · diff |
| git:20260828.2ed1cb6 | 2026-08-28 | 2ed1cb6 | 3,843 B | A | view · diff |
| git:20260430.41ccae5 | 2026-04-30 | 41ccae5 | 3,711 B | A | view · diff |
| git:20260416.7a4f84b | 2026-04-16 | 7a4f84b | 3,430 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (3880 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
zilliztech/memsearch · 2,816 stars · license MIT · pushed 2026-10-27 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_qrx2yfngyl5g6nzp GET https://markdownregistry.com/api/v1/resolve?ref=zilliztech/memsearch/memory-recall GET https://markdownregistry.com/api/v1/blob/b9385e5c3d8c35eae0cce2193dc8d3a7cf010670ced478e51eed2124409ff692
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from zilliztech/memsearch
Every file in zilliztech/memsearch