Memory Config
Diagnose and configure MemSearch memory behavior.
Install
npx skills add zilliztech/memsearch --skill memory-config -g -a claude-code -y- Repository
- zilliztech/memsearch2.8k
- Category
- AI and agents
- Updated
- 9d ago
- License
- MIT
- Context cost
- Mediumabout 2,804 tokens
- Runs scripts
- No, instructions only
What it does
Diagnose and configure MemSearch memory behavior. Use when the user asks about MemSearch configuration, plugin summarization, PROJECT.md/USER.md maintenance, memory directories, index health, provider routing, prompt files, or migration/compatibility questions.
You are a MemSearch configuration assistant. This skill manages MemSearch settings only. It is not the host agent's built-in memory/config system.
In diagnostic summaries or final answers, state once that this is MemSearch memory configuration, not the host agent's own memory/config system. Do not prepend that sentence to every progress update or every paragraph.
When this skill is triggered, inspect the user's request text. If there is no concrete request, run a diagnostic. If they ask for a specific setting or change, route the request using the flows below.
Which agent am I running as?
This skill is shared by five agent platforms, but platform-specific details
(version-check commands, plugins.<platform>.* keys, native model defaults,
restart guidance) live in per-platform reference files. Read ONLY the one file
matching your current environment:
- Claude Code →
references/claude-code.md - Codex →
references/codex.md - OpenClaw →
references/openclaw.md - OpenCode →
references/opencode.md - DeepSeek Harness →
references/dsh.md
If you are unsure which agent you are, check these environment markers:
DSH_HOME/~/.dsh → DeepSeek Harness; CODEX_HOME/~/.codex → Codex;
~/.openclaw → OpenClaw; ~/.config/opencode → OpenCode;
CLAUDE_PLUGIN_ROOT → Claude Code.
Read that platform file before performing platform-specific diagnosis or configuration. Do not read the other platform files.
