MemSearch Memory Config
Diagnoses and configures MemSearch's memory, indexing, and provider settings.
Test report
- Verdict
- Tested · Works
- Score
- Tested
- Jul 10, 2026
- Environment
- Claude Code 2.x (agent harness)
- Upstream re-checked
- Aug 10, 2026 · 5b5a2e3
Ran the skill's own diagnostic command block for real: memsearch and uv/uvx are both absent from this machine's PATH, which immediately pinpoints 'MemSearch isn't installed' as the root cause instead of baseline's generic troubleshooting guesses — but the documented uv fallback command itself (`uvx --from memsearch[onnx] memsearch --version`) breaks under zsh with 'no matches found: memsearch[onnx]' because the brackets aren't quoted, a real bug in the docs.
Scored on four weighted criteria — install, triggering, output vs. baseline, docs. How scoring works
- Installs cleanly 5/5
- Triggers reliably 5/5
- Output vs. baseline 8/10
- Docs & honesty 4/5
What MemSearch Memory Config does
Diagnoses and configures MemSearch, a third-party memory/indexing plugin for Claude Code, covering config scope (global vs project), provider routing, PROJECT.md/USER.md maintenance, and index health via the memsearch CLI. Triggers on MemSearch-specific requests — empty memory folders, provider switching, prompt overrides, migration questions — and explicitly states it is not Claude Code's own built-in memory system.
How to install MemSearch Memory Config
git clone https://github.com/zilliztech/memsearch
cd memsearch
mkdir -p ~/.claude/skills
cp -r plugins/claude-code/skills/memory-config ~/.claude/skills/memory-config
Skills live in ~/.claude/skills/ (global) or .claude/skills/
(per-project). Restart Claude Code after installing.
Commands — how to trigger MemSearch Memory Config
-
/memory-configDiagnoses and configures MemSearch's memory, indexing, and provider settings.
It also activates on plain-language prompts like these:
-
Diagnose why MemSearch isn't indexing my project memory -
Switch MemSearch's provider routing to a different provider -
Update PROJECT.md and USER.md for MemSearch configuration
Frequently asked questions
- Is the MemSearch Memory Config skill free?
- Yes. The skill itself is free from zilliztech/memsearch. SkillProof publishes the install command and an independent test verdict at no cost.
- Does MemSearch Memory Config work with Claude Code?
- We tested it with Claude Code 2.x (agent harness) on Jul 10, 2026. Verdict: Tested · Works. Ran the skill's own diagnostic command block for real: memsearch and uv/uvx are both absent from this machine's PATH, which immediately pinpoints 'MemSearch isn't installed' as the root cause instead of baseline's generic troubleshooting guesses — but the documented uv fallback command itself (`uvx --from memsearch[onnx] memsearch --version`) breaks under zsh with 'no matches found: memsearch[onnx]' because the brackets aren't quoted, a real bug in the docs.
- What is the MemSearch Memory Config SkillProof Score?
- 8.8/10 — installs cleanly 5/5, triggers reliably 5/5, output vs. baseline 8/10, docs & honesty 4/5.
- How do I install MemSearch Memory Config?
- Copy the install command from this page, run it in your terminal, and restart Claude Code. Skills live in ~/.claude/skills/ (global) or .claude/skills/ inside a project.
- Can I use MemSearch Memory Config with Cursor, Copilot, Gemini CLI, Codex or other AI tools?
- The SKILL.md format is native to Claude (Claude Code, Desktop, claude.ai). The instructions inside adapt to other assistants: Cursor rules, GitHub Copilot instructions, Windsurf rules, Custom GPTs, AGENTS.md for OpenAI Codex, and GEMINI.md for Google Gemini CLI — our conversion guides cover each, and the free converter on the tools page does the wrapping for you.