Phx Investigate
oliver-kriska/claude-elixir-phoenix
Investigate Elixir/Phoenix bugs root-cause first. An agent skill from oliver-kriska/claude-elixir-phoenix.
Search and recall relevant memories from past sessions via memsearch.
Install Memory Recall
$ npx skills add zilliztech/memsearch --skill memory-recall -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install zilliztech/memsearch memory-recall --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/zilliztech/memsearch.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/openclaw/skills/memory-recall .claude/skills/memory-recall && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "memory-recall" agent skill from https://github.com/zilliztech/memsearch/tree/main/plugins/openclaw/skills/memory-recall into .claude/skills/memory-recall/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "memory-recall", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/zilliztech/memsearch/tree/main/plugins/openclaw/skills/memory-recallType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add zilliztech/memsearch --skill memory-recall -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install zilliztech/memsearch memory-recall --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/zilliztech/memsearch.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/openclaw/skills/memory-recall .agents/skills/memory-recall && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "memory-recall" agent skill from https://github.com/zilliztech/memsearch/tree/main/plugins/openclaw/skills/memory-recall into .agents/skills/memory-recall/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "memory-recall", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add zilliztech/memsearch --skill memory-recall -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install zilliztech/memsearch memory-recall --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/zilliztech/memsearch.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/openclaw/skills/memory-recall .cursor/skills/memory-recall && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "memory-recall" agent skill from https://github.com/zilliztech/memsearch/tree/main/plugins/openclaw/skills/memory-recall into .cursor/skills/memory-recall/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "memory-recall", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/zilliztech/memsearch.git --path plugins/openclaw/skills/memory-recall--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add zilliztech/memsearch --skill memory-recall -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install zilliztech/memsearch memory-recall --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/zilliztech/memsearch.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/openclaw/skills/memory-recall .gemini/skills/memory-recall && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "memory-recall" agent skill from https://github.com/zilliztech/memsearch/tree/main/plugins/openclaw/skills/memory-recall into .gemini/skills/memory-recall/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "memory-recall", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install zilliztech/memsearch memory-recallInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add zilliztech/memsearch --skill memory-recall -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/zilliztech/memsearch.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/openclaw/skills/memory-recall .github/skills/memory-recall && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "memory-recall" agent skill from https://github.com/zilliztech/memsearch/tree/main/plugins/openclaw/skills/memory-recall into .github/skills/memory-recall/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "memory-recall", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add zilliztech/memsearch --skill memory-recall -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install zilliztech/memsearch memory-recall --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/zilliztech/memsearch.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/openclaw/skills/memory-recall .opencode/skills/memory-recall && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "memory-recall" agent skill from https://github.com/zilliztech/memsearch/tree/main/plugins/openclaw/skills/memory-recall into .opencode/skills/memory-recall/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "memory-recall", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
memory-recall- GitHub stars
- 2.7k
- Token cost
- ~807 tokens
- SKILL.md length
- 325 words
- Files
- 1
- Skills in repo
- 4
- Repo updated
- First seen
- Licence
- MIT
At a glance
Search and recall relevant memories from past sessions via memsearch.
- Works in 3 steps: memory_search — Start here → memory_get — When search results aren't… → memory_transcript — When you need the…
- The users question could benefit from historical context
- SKILL.md covers Tools (use progressively), Decision guide, Tips and When unsure what to search
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Memory Recall is an agent skill from 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…
Its SKILL.md is about 810 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in AI & LLM Engineering. It works with Milvus and DeepSeek. The repository describes itself as: A persistent, unified memory layer for all your AI agents (e.g. Claude Code, Codex, DSH), backed by Markdown and Milvus. The licence is MIT.
When your agent uses it
- The users question could benefit from historical context
- Debugging notes
- Previous conversations
- Project knowledge -- especially questions like what did I decide about X
Example prompts
- “what did I decide about X”
- “why did we do Y”
- “have I seen this before”
- “/memory-recall”
Workflow steps
3 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 2a4652f. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Memory Recall loads about 807 tokens when it runs. Until then it costs about 183 tokens; SKILL.md has 325 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from zilliztech/memsearch at commit 2a4652f, republished under its MIT licence (© zilliztech). 325 words, ~807 tokens.
Download SKILL.mdSave it as
.claude/skills/memory-recall/SKILL.md (or your agent's skills folder).- name
- memory-recall
- description
- 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.
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"
- If the anchor format is unfamiliar (e.g.
rollout:,turn:,db:instead oftranscript:), try reading the referenced file directly to explore its structure and locate the relevant conversation by the session or turn identifiers in the anchor.
Decision guide
| User intent | Tools to use |
|---|---|
| Quick recall ("did we discuss X?") | memory_search only |
| Need details ("what was the solution?") | memory_search → memory_get |
| Need original dialogue ("show me the exact conversation") | memory_search → memory_get → memory_transcript |
Tips
- memory_search returns chunk_hash — pass it to memory_get for expansion
- memory_get may reveal
<!-- session:UUID transcript:PATH -->anchors — pass the path to memory_transcript - If memory_search returns no results, try rephrasing with different keywords
- Results are sorted by relevance (hybrid BM25 + vector search)
When unsure what to search
The SessionStart injection already shows you a heading-level preview of recent memory files — skim it first to spot concrete topics (dates, session numbers, task names). If that preview doesn't surface an obvious query, try broad keywords like overview, recent work, or a topic guess — hybrid BM25 + vector retrieval will surface chunks that share any of the terms, and you can iterate from there.
© zilliztech, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in plugins/openclaw/skills/memory-recall of zilliztech/memsearch.
Open the folder on GitHubat commit 2a4652f
Compare with similar skills
Memory Recall next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Memory Recall this skillzilliztech/memsearch | 2.7k | — | ~807 | Automated safety check: Pass | MIT | |
| Phx Investigateoliver-kriska/claude-elixir-phoenix | 565 | — | ~1k | Automated safety check: Pass | MIT | |
| Evals Contextzgsm-ai/costrict | 4.4k | 1 repos | ~1.9k | Automated safety check: Pass | Apache-2.0 | |
| Visionxiincs/claude-code-vision-skill | 170 | — | ~1.2k | Automated safety check: Pass | MIT | |
| Oracle Agent Team OrchestratorBald0Wang/DeepSeek-Oracle | 187 | — | ~551 | Automated safety check: Pass | None | |
| Dsh PlaybookZSeven-W/dsh-crew | 156 | — | ~1.1k | Automated safety check: Pass | MIT |
Similar skills
Evals Context
zgsm-ai/costrict
Provides context about the CoStrict evals system structure in this monorepo.
Vision
xiincs/claude-code-vision-skill
Call vision models (Doubao, Qwen, DeepSeek, OpenAI) to analyze images.
Oracle Agent Team Orchestrator
Bald0Wang/DeepSeek-Oracle
Orchestrate DeepSeek Oracle multi-agent workflows by routing user intents to specialist oracle skills, enforcing safety gates, and composing one unified answer with follow-up questions and action…
Dsh Playbook
ZSeven-W/dsh-crew
How to dispatch well — choosing flash vs pro, writing self-contained briefs, parallelism, verifying results, and guardrails
LLM Pipeline Profiler Analysis
BBuf/AI-Infra-Auto-Driven-SKILLS
Breaks LLM torch profiler traces down by forward pass, layer and kernel, with timing tables and Perfetto time ranges for the layers you want to inspect.
More from zilliztech/memsearch
Memory Config
zilliztech/memsearch
Diagnose and configure MemSearch memory behavior. An agent skill from zilliztech/memsearch.
Memory To Skill
zilliztech/memsearch
Turn workflows from your MemSearch memory into reusable skills.
Memory Recall
zilliztech/memsearch
Search and recall relevant memories from past sessions via memsearch.
Related
Questions about Memory Recall
What does Memory Recall do?
Search and recall relevant memories from past sessions via memsearch. Memory Recall is an agent skill from zilliztech/memsearch. Search and recall relevant memories from past sessions via memsearch.
When should I use Memory Recall?
Memory Recall fits situations like: the users question could benefit from historical context; debugging notes; previous conversations; project knowledge -- especially questions like what did I decide about X.
How do I install Memory Recall in Claude Code?
Run `npx skills add zilliztech/memsearch --skill memory-recall -a claude-code`. Or copy the skill folder (plugins/openclaw/skills/memory-recall in zilliztech/memsearch) into .claude/skills/memory-recall in your project. Claude Code loads it when a task matches its description.
How do I install Memory Recall in Codex?
Run `npx skills add zilliztech/memsearch --skill memory-recall -a codex`. Or copy the skill folder (plugins/openclaw/skills/memory-recall in zilliztech/memsearch) into .agents/skills/memory-recall in your project. Codex loads it when a task matches its description.
Can I use Memory Recall in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add zilliztech/memsearch --skill memory-recall -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/memory-recall, .gemini/skills/memory-recall, .github/skills/memory-recall and .opencode/skills/memory-recall in your project.
What does Memory Recall need to run?
SKILL.md names no scripts, command-line tools or credentials: Memory Recall is instructions for the agent only.
Does Memory Recall access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Memory Recall safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Memory Recall use?
Memory Recall is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Memory Recall use?
About 807 tokens (SKILL.md is roughly 3.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Memory Recall?
Skills that share tags, products or a category with Memory Recall: Phx Investigate (oliver-kriska/claude-elixir-phoenix, 565 stars), Evals Context (zgsm-ai/costrict, 4.4k stars), Vision (xiincs/claude-code-vision-skill, 170 stars) and Oracle Agent Team Orchestrator (Bald0Wang/DeepSeek-Oracle, 187 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Memory Recall?
zilliztech (a GitHub organization) maintains it in zilliztech/memsearch, which has 2,727 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on September 24, 2026.
Source: zilliztech/memsearch on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.