Memory To Skill
Turn workflows from your MemSearch memory into reusable skills.
Install
npx skills add zilliztech/memsearch --skill memory-to-skill -g -a claude-code -y- Repository
- zilliztech/memsearch2.8k
- Category
- AI and agents
- Updated
- 9d ago
- License
- MIT
- Context cost
- Mediumabout 1,894 tokens
- Runs scripts
- No, instructions only
What it does
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.
You manage MemSearch's procedural memory: skills distilled from the work you repeat, a third layer beside the daily journals (episodic) and PROJECT.md / USER.md (semantic). State once that this is MemSearch skill distillation, not the host agent's built-in skills system.
Stages: 0 memory journals → 1 candidate (.memsearch/skill-candidates/,
a git-tracked store that keeps evolving) → 2 installed (an agent skill dir).
Candidates are never installed automatically; installing is always a human step.
User requests may stop at candidate creation/review, or continue to installation
in the same turn after explicit approval; match the requested stage.
The plugins.<platform>.memory_to_skill.* config key prefix and the install-path
notes are platform-specific, see your platform reference file:
- Claude Code →
references/claude-code.md - Codex →
references/codex.md - OpenClaw →
references/openclaw.md - OpenCode →
references/opencode.md - DeepSeek Harness →
references/dsh.md
Intent routing
- "make/turn this into a skill", "from what we just did" → A. Capture now.
- "what skills / review candidates / install X" → B. Review & install.
- "mine my history / find recurring workflows" → C. Distill from history.
- "enable / configure / how eager" → D. Configure.
- Unclear or empty → run B's
list; if empty, offer A or C.
A. Capture what you just did (0→1→2)
You already have the context, so draft the skill yourself, do not call the background distiller for this. Write a SKILL.md body (markdown, no frontmatter): imperative numbered steps for the recurring task, concrete commands and paths, no secrets, self-contained.
