Individual skill
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 the host agent's own skills system.
plugins/claude-code/skills/memory-to-skill/SKILL.md
Source commit 369ae1da48b76b4e87e7481a61642f4b2dbeb894
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 7, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 2,836
- Repository last updated
- Nov 6, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent-memory Repository topic
- claude-code Repository topic
- claude-code-plugin Repository topic
- memory Repository topic
- openclaw Repository topic
- rag Repository topic
- agent Repository topic
- embeddings Repository topic
- milvus Repository topic
- semantic-search Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 8,083 bytesSKILL.mdcore · 8,083 bytesSKILL.mdcore · 8,083 bytesSKILL.mdcore · 8,083 bytesSKILL.mdcore · 8,083 bytesSKILL.mdcore · 8,083 bytesSKILL.mdcore · 8,083 bytesreferences/claude-code.mddoc · 706 bytesreferences/codex.mddoc · 706 bytesreferences/dsh.mddoc · 850 bytesreferences/openclaw.mddoc · 702 bytesreferences/opencode.mddoc · 1,331 bytes
Read excerpt
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:
