memory-recall
memory-recall is a skill in zilliztech/memsearch, last changed 20 Oct 2026. It is instructions only: no scripts, no named hosts and no pre-approved tools. Our pattern check flagged nothing at commit 65d8b22 on 27 Oct 2026.
Pattern check: nothing flagged · commit 65d8b22 · 27 Oct 2026
InstallSearch and recall relevant memories from past sessions via MemSearch. Use for past decisions, debugging notes, previous conversations, and project knowledge, especially when the context includes a MemSearch memory hint. Skip purely current-code questions or when the user asks to ignore memory.
- Licence
- MIT
- Repo stars
- 2.8k
- Folder last changed
- 20 Oct 2026 (opens in a new tab)
- Publisher
- zilliztech
- Files
- 1 file
- Checked
- 65d8b22 (opens in a new tab) · 27 Oct 2026
Install
Each tab says whether it installs commit 65d8b22, the one we checked, or the latest version.
No tab for your agent? Use Any agent for OpenCode, Goose, Windsurf (Devin Desktop), Zed, Roo Code, Factory Droid, Junie, Amp and Antigravity, and Claude Code for Cline. Kiro needs the folder copied by hand.
Pinned to commit 65d8b22, the one we checked.
From your project's root folder:
tmp="$(mktemp -d)" &&
git clone -q --depth 1 --filter=blob:none --no-checkout https://github.com/zilliztech/memsearch.git "$tmp" &&
git -C "$tmp" fetch -q --depth 1 origin 65d8b220d4265f70441785aa22203f0e85ea3ec6 &&
git -C "$tmp" sparse-checkout set -- plugins/opencode/skills/memory-recall &&
git -C "$tmp" checkout -q 65d8b220d4265f70441785aa22203f0e85ea3ec6 &&
mkdir -p .claude/skills &&
mkdir .claude/skills/memory-recall &&
cp -R "$tmp"/plugins/opencode/skills/memory-recall/. .claude/skills/memory-recall/ &&
rm -rf "$tmp"If Claude Code was already running and this created the skills folder, run /reload-skills.
Pinned to commit 65d8b22, the one we checked.
Skills in the Claude apps belong to your account rather than to a project.
Make memory-recall.zip, with the skill folder at the top level:
tmp="$(mktemp -d)" &&
git clone -q --depth 1 --filter=blob:none --no-checkout https://github.com/zilliztech/memsearch.git "$tmp" &&
git -C "$tmp" fetch -q --depth 1 origin 65d8b220d4265f70441785aa22203f0e85ea3ec6 &&
git -C "$tmp" sparse-checkout set -- plugins/opencode/skills/memory-recall &&
git -C "$tmp" checkout -q 65d8b220d4265f70441785aa22203f0e85ea3ec6 &&
out="$(mktemp -d)" &&
cp -R "$tmp"/plugins/opencode/skills/memory-recall "$out"/memory-recall &&
(cd "$out" && zip -qr - memory-recall) > memory-recall.zip &&
rm -rf "$tmp" "$out"In Claude, open Customize > Skills, select +, then + Create skill > Upload a skill, and choose memory-recall.zip.
On Free, Pro and Max plans, turn on Code execution and file creation (Create and edit files in newer settings) under Settings > Capabilities.
Pinned to commit 65d8b22, the one we checked.
From your project's root folder:
tmp="$(mktemp -d)" &&
git clone -q --depth 1 --filter=blob:none --no-checkout https://github.com/zilliztech/memsearch.git "$tmp" &&
git -C "$tmp" fetch -q --depth 1 origin 65d8b220d4265f70441785aa22203f0e85ea3ec6 &&
git -C "$tmp" sparse-checkout set -- plugins/opencode/skills/memory-recall &&
git -C "$tmp" checkout -q 65d8b220d4265f70441785aa22203f0e85ea3ec6 &&
mkdir -p .agents/skills &&
mkdir .agents/skills/memory-recall &&
cp -R "$tmp"/plugins/opencode/skills/memory-recall/. .agents/skills/memory-recall/ &&
rm -rf "$tmp"Codex picks up new skills on its own; restart it if this one does not appear.
Pinned to commit 65d8b22, the one we checked.
From your project's root folder:
tmp="$(mktemp -d)" &&
git clone -q --depth 1 --filter=blob:none --no-checkout https://github.com/zilliztech/memsearch.git "$tmp" &&
git -C "$tmp" fetch -q --depth 1 origin 65d8b220d4265f70441785aa22203f0e85ea3ec6 &&
git -C "$tmp" sparse-checkout set -- plugins/opencode/skills/memory-recall &&
git -C "$tmp" checkout -q 65d8b220d4265f70441785aa22203f0e85ea3ec6 &&
mkdir -p .cursor/skills &&
mkdir .cursor/skills/memory-recall &&
cp -R "$tmp"/plugins/opencode/skills/memory-recall/. .cursor/skills/memory-recall/ &&
rm -rf "$tmp"Pinned to commit 65d8b22, the one we checked.
From your project's root folder:
tmp="$(mktemp -d)" &&
git clone -q --depth 1 --filter=blob:none --no-checkout https://github.com/zilliztech/memsearch.git "$tmp" &&
git -C "$tmp" fetch -q --depth 1 origin 65d8b220d4265f70441785aa22203f0e85ea3ec6 &&
git -C "$tmp" sparse-checkout set -- plugins/opencode/skills/memory-recall &&
git -C "$tmp" checkout -q 65d8b220d4265f70441785aa22203f0e85ea3ec6 &&
mkdir -p .github/skills &&
mkdir .github/skills/memory-recall &&
cp -R "$tmp"/plugins/opencode/skills/memory-recall/. .github/skills/memory-recall/ &&
rm -rf "$tmp"In a running Copilot CLI session, run /skills reload.
Or install it with gh skill, which also installs the commit we checked. Needs GitHub CLI 2.90 or later.
gh skill install zilliztech/memsearch plugins/opencode/skills/memory-recall/SKILL.md@65d8b220d4265f70441785aa22203f0e85ea3ec6 --agent github-copilot --scope projectPinned to commit 65d8b22, the one we checked.
From your project's root folder:
tmp="$(mktemp -d)" &&
git clone -q --depth 1 --filter=blob:none --no-checkout https://github.com/zilliztech/memsearch.git "$tmp" &&
git -C "$tmp" fetch -q --depth 1 origin 65d8b220d4265f70441785aa22203f0e85ea3ec6 &&
git -C "$tmp" sparse-checkout set -- plugins/opencode/skills/memory-recall &&
git -C "$tmp" checkout -q 65d8b220d4265f70441785aa22203f0e85ea3ec6 &&
mkdir -p .gemini/skills &&
mkdir .gemini/skills/memory-recall &&
cp -R "$tmp"/plugins/opencode/skills/memory-recall/. .gemini/skills/memory-recall/ &&
rm -rf "$tmp"In a running session, run /skills reload.
Or use Gemini CLI’s own installer. Installs the latest version, not the one we checked.
gemini skills install https://github.com/zilliztech/memsearch.git --path plugins/opencode/skills/memory-recall --scope workspacePinned to commit 65d8b22, the one we checked.
Codex, Cursor, Copilot, VS Code, Gemini CLI, OpenCode, Goose, Amp and Zed all read .agents/skills; Claude Code and Kiro list only their own folders.
From your project's root folder:
tmp="$(mktemp -d)" &&
git clone -q --depth 1 --filter=blob:none --no-checkout https://github.com/zilliztech/memsearch.git "$tmp" &&
git -C "$tmp" fetch -q --depth 1 origin 65d8b220d4265f70441785aa22203f0e85ea3ec6 &&
git -C "$tmp" sparse-checkout set -- plugins/opencode/skills/memory-recall &&
git -C "$tmp" checkout -q 65d8b220d4265f70441785aa22203f0e85ea3ec6 &&
mkdir -p .agents/skills &&
mkdir .agents/skills/memory-recall &&
cp -R "$tmp"/plugins/opencode/skills/memory-recall/. .agents/skills/memory-recall/ &&
rm -rf "$tmp"Or use the skills CLI from skills.sh. Installs the latest version, not the one we checked. The skills CLI reports installs to skills.sh unless you set DISABLE_TELEMETRY=1.
npx skills@1.7.4 add zilliztech/memsearch --skill memory-recallWhat it can touch
From the files and frontmatter at commit 65d8b22. This is how much a skill can do, not whether it is risky.
What it can touch: Instructions only
It is instructions only: no scripts, no named hosts and no pre-approved tools.
Pattern check
Pattern check: nothing flagged · commit 65d8b22 · 27 Oct 2026
We checked every text file in this skill, at commit 65d8b22 on 27 Oct 2026, against 45 published patterns such as download-and-run commands, hidden text and credential access. We don't run the skill, we don't read the web pages it points to, and we can't judge everything its instructions might lead an agent to do. In published tests, pattern checks like this one missed most malicious skills. Read the skill before you install it — especially anything it asks you to download or run.
Format check
Each agent reads SKILL.md a little differently. We check the file against each one's published rules; we don't run the skill in any agent.
Agent Skills specPasses with warnings
The open format from agentskills.io, held to what the strictest agents enforce, so one folder loads everywhere.
- Warning
Paths that may not work once the skill is installed: line 13: ../memory-config/references/opencode.md (outside the skill folder). B6
Fix: Use forward-slash paths relative to SKILL.md, and copy shared files into the skill.
- Note
There is no license field, so readers can't tell whether they may reuse the skill. O2
Fix: Add license: with an SPDX name such as MIT or Apache-2.0, or the name of a bundled licence file.
- Warning
Claude CodePasses with warnings
Claude Code reads its own extra fields, ignores unknown ones, and still loads a skill whose frontmatter is broken, without its fields.
- Warning
Paths that may not work once the skill is installed: line 13: ../memory-config/references/opencode.md (outside the skill folder). B6
Fix: Use forward-slash paths relative to SKILL.md, and copy shared files into the skill.
- Warning
Claude apps & API uploadPasses with warnings
Uploading to claude.ai or the Claude API, or packaging with Anthropic's script, accepts only the six spec fields and stops on anything else.
- Warning
Paths that may not work once the skill is installed: line 13: ../memory-config/references/opencode.md (outside the skill folder). B6
Fix: Use forward-slash paths relative to SKILL.md, and copy shared files into the skill.
- Note
The description is 294 characters. The claude.ai Help Center says 200 at most, though Anthropic's API docs and validator allow 1,024. D4
Fix: If the claude.ai upload refuses it, trim the description to 200 characters.
- Warning
OpenAI (Codex & API)Passes with warnings
Codex finds SKILL.md by its exact name and needs a description; OpenAI's Skills API checks the frontmatter against the spec and caps uploads.
- Warning
Paths that may not work once the skill is installed: line 13: ../memory-config/references/opencode.md (outside the skill folder). B6
Fix: Use forward-slash paths relative to SKILL.md, and copy shared files into the skill.
- Warning
VS Code & CopilotPasses with warnings
VS Code reads skills one folder below .github/skills, .claude/skills or .agents/skills and falls back to the folder name when the name is missing or differs; GitHub's Copilot docs require the exact name SKILL.md.
- Warning
Paths that may not work once the skill is installed: line 13: ../memory-config/references/opencode.md (outside the skill folder). B6
Fix: Use forward-slash paths relative to SKILL.md, and copy shared files into the skill.
- Warning
SKILL.md
Files
1 file
| Path | Size |
|---|---|
| SKILL.md (opens in a new tab) | 2.5 KB |
More from zilliztech/memsearch
memory-recall
zilliztech/memsearch
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.
- Runs shell commands
- Pre-approves tools
- +1 more
Pattern check: 2 items to reviewMIT · 2.8k repo stars · Updated 8 Sept 2026
memory-recall
zilliztech/memsearch
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.
- Runs shell commands
Pattern check: Nothing flaggedMIT · 2.8k repo stars · Updated 8 Sept 2026
memory-recall
zilliztech/memsearch
- Runs shell commands
Pattern check: Nothing flaggedMIT · 2.8k repo stars · Updated 26 Oct 2026
memory-recall
zilliztech/memsearch
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.
- Instructions only
Pattern check: Nothing flaggedMIT · 2.8k repo stars · Updated 29 May 2026
memory-to-skill
zilliztech/memsearch
Turn workflows from your MemSearch memory into reusable skills. Use when the user asks to make/create/extract/distill a skill from what they just did or from past work, review skill candidates, install a distilled skill, or 'turn this into a skill'. Manages MemSearch procedural-memory candidates under .memsearch/skill-candidates/, not the host agent's own skills system.
- Runs shell commands
Pattern check: Nothing flaggedMIT · 2.8k repo stars · Updated 20 Oct 2026
memory-to-skill
zilliztech/memsearch
Turn workflows from your MemSearch memory into reusable skills. Use when the user asks to make/create/extract/distill a skill from what they just did or from past work, review skill candidates, install a distilled skill, or 'turn this into a skill'. Manages MemSearch procedural-memory candidates under .memsearch/skill-candidates/, not the host agent's own skills system.
- Runs shell commands
- Pre-approves tools
Pattern check: 1 item to reviewMIT · 2.8k repo stars · Updated 20 Oct 2026
