Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →zilliztech/memory-to-skill
Turn workflows from your MemSearch memory into reusable skills.
Passed 16 of 21 test cases with the skill, and 9 of 21 without it.
and 6 more in the full report
9 fixed9 passed either way4 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
What exact command string enables the background session-end distillation pass globally for the OpenClaw platform?
| Checked | Without skill | With skill |
|---|---|---|
| Uses `memsearch config set plugins.openclaw.memory_to_skill.enabled true` as the command. | Missed | Passed |
The instructions your model reads when the skill loads.
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:
references/claude-code.mdreferences/codex.mdreferences/openclaw.mdreferences/opencode.mdreferences/dsh.mdlist; if empty, offer A or C.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.
Be exact — do not guess. You have the live session for what you just did, so use the real commands, paths, and output, not approximations. If a detail is uncertain, verify it (re-read the relevant files or the transcript) or keep that step general — a wrong command is worse than a vague one. Then persist it as a candidate:
printf '%s' "## <title>\n\n1. ...\n2. ..." | memsearch skills add \
--name "<short-slug>" \
test cases passed, vs 9 / 21 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.