memory-to-skill
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 Claude Code's own skills system.
Profile →npx skills add zilliztech/memsearch --skill memory-to-skill --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
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 Claude Code'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. ## 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 SKIL
- Intent routing
- A. Capture what you just did (0→1→2)
- B. Review & install candidates (1→2)
- C. Mine history for recurring workflows (0→1)
- D. Configure
- Install paths
- Guardrails
printf '%s' "## <title>\n\n1. ...\n2. ..." | memsearch skills add \ memsearch skills status # pending candidate versions needing install memsearch skills list # add -j for sources / installed paths git -C .memsearch/skill-candidates log --oneline -5 2>/dev/null || true memsearch config get plugins.claude-code.memory_to_skill.paths 2>/dev/null || echo "[]" memsearch skills install <name> --path <configured-or-user-approved-path> memsearch config get plugins.claude-code.memory_to_skill.enabled 2>/dev/null || echo "false" enable the background pass globally (do not enable silently) memsearch config set plugins.claude-code.memory_to_skill.enabled true how eagerly history-mining distils (default 3; lower = more eager)
What does the memory-to-skill skill do?
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 Claude Code's own skills system.
How do I install it?
Run `npx skills add zilliztech/memsearch --skill memory-to-skill --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From zilliztech/memsearch, a repository with 2,420 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.