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:20260529.d24ebb1Pins git:20260529.d24ebb1 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- zilliztech/memsearch
- Path
plugins/openclaw/skills/memory-recall/SKILL.md- Versions recorded
- 5
- Latest version
- git:20260529.d24ebb1, committed May 29, 2026
- First version recorded
- Mar 30, 2026
- Size
- 3,250 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] Memory available` hints injected via SessionStart or UserPromptSubmit. Typical flow: search for 3-5 chunks, expand the most relevant…
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 have three memory tools for progressive recall. Start with search, go deeper only when needed. ## Tools (use progressively) ### 1. memory_search — Start here Semantic search across all past conversation memories. - Returns: chunk summaries with dates, topics, chunk_hash identifiers - Use for: "What did we discuss about X?", "Have I asked about Y before?" ### 2. memory_get — When search results aren't detailed enough Expands a specific chunk_hash to show the full markdown section with surrounding context. - Input: chunk_hash from memory_search results - Returns: full section text, may include transcript anchors (<!-- session:UUID transcript:PATH -->) - Use for: "Show me the details", "I need more context on that result" ### 3. memory_transcript — When you need the exact original conversation Parses the original session transcript to retrieve the raw dialogue. - Input: transcript_path from the anchor comment in memory_get results - Returns: formatted conversation with [User]/[Assistant] labels and tool calls - Use for: "What exactly did I say?", "Show me the original conversation" …
Read the whole file at its exact version.
How to install
mdr add zilliztech/memsearch/memory-recall@sha256:a47d29a961a2a78cThe line at the top of this page pins the label git:20260529.d24ebb1, 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_uydc22ypgz3mm7ax)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Mar 30, 2026 and May 29, 2026, about one every 15 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260529.d24ebb1 latest | 2026-05-29 | d24ebb1 | 3,250 B | A | view · diff |
| git:20260416.7a4f84b | 2026-04-16 | 7a4f84b | 3,251 B | A | view · diff |
| git:20260416.6de05ec | 2026-04-16 | 6de05ec | 2,813 B | A | view · diff |
| git:20260331.f2cbc6b | 2026-03-31 | f2cbc6b | 2,296 B | A | view · diff |
| git:20260330.3457213 | 2026-03-30 | 3457213 | 2,046 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 (3250 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_uydc22ypgz3mm7ax GET https://markdownregistry.com/api/v1/resolve?ref=zilliztech/memsearch/memory-recall GET https://markdownregistry.com/api/v1/blob/a47d29a961a2a78cb1da8fa794a3fde7954e406c5e9d473e89b1a6b1852342f7
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