Skills

memory-to-skill

memory-to-skill is a skill in zilliztech/memsearch, last changed 20 Oct 2026. It can run shell commands. Our pattern check flagged nothing at commit 65d8b22 on 27 Oct 2026.

Pattern check: nothing flagged · commit 65d8b22 · 27 Oct 2026

Install
Licence
MIT
Repo stars
2.8k
Folder last changed
20 Oct 2026 (opens in a new tab)
Publisher
zilliztech
Files
6 files
Checked
65d8b22 (opens in a new tab) · 27 Oct 2026

Install

Each tab says whether it installs commit 65d8b22, the one we checked, or the latest version.

No tab for your agent? Use Any agent for OpenCode, Goose, Windsurf (Devin Desktop), Zed, Roo Code, Factory Droid, Junie, Amp and Antigravity, and Claude Code for Cline. Kiro needs the folder copied by hand.

Pinned to commit 65d8b22, the one we checked.

From your project's root folder:

tmp="$(mktemp -d)" &&
  git clone -q --depth 1 --filter=blob:none --no-checkout https://github.com/zilliztech/memsearch.git "$tmp" &&
  git -C "$tmp" fetch -q --depth 1 origin 65d8b220d4265f70441785aa22203f0e85ea3ec6 &&
  git -C "$tmp" sparse-checkout set -- plugins/dsh/skills/memory-to-skill &&
  git -C "$tmp" checkout -q 65d8b220d4265f70441785aa22203f0e85ea3ec6 &&
  mkdir -p .claude/skills &&
  mkdir .claude/skills/memory-to-skill &&
  cp -R "$tmp"/plugins/dsh/skills/memory-to-skill/. .claude/skills/memory-to-skill/ &&
  rm -rf "$tmp"

If Claude Code was already running and this created the skills folder, run /reload-skills.

Claude Code docs (opens in a new tab)

What it can touch

From the files and frontmatter at commit 65d8b22. This is how much a skill can do, not whether it is risky.

What it can touch: Scripts or outside hosts

  • Runs shell commands

    Its instructions or files give the agent commands to run on your computer.

Pattern check

Pattern check: nothing flagged · commit 65d8b22 · 27 Oct 2026

We checked every text file in this skill, at commit 65d8b22 on 27 Oct 2026, against 45 published patterns such as download-and-run commands, hidden text and credential access. We don't run the skill, we don't read the web pages it points to, and we can't judge everything its instructions might lead an agent to do. In published tests, pattern checks like this one missed most malicious skills. Read the skill before you install it — especially anything it asks you to download or run.

How the check worksReport an incorrect finding

Format check

Each agent reads SKILL.md a little differently. We check the file against each one's published rules; we don't run the skill in any agent.

  • Agent Skills specFails

    The open format from agentskills.io, held to what the strictest agents enforce, so one folder loads everywhere.

    • Error

      The file doesn't start with a --- line, so it has no frontmatter. The spec requires a name and description there. F3

      Fix: Start the file with ---, then name: and description: lines, then a closing --- line.

  • Claude CodePasses with warnings

    Claude Code reads its own extra fields, ignores unknown ones, and still loads a skill whose frontmatter is broken, without its fields.

    • Warning

      The file doesn't start with a --- line, so it has no frontmatter. Claude Code reads it all as instructions: the name falls back to the folder and the description to the first line. F3

      Fix: Start the file with ---, then name: and description: lines, then a closing --- line.

  • Claude apps & API uploadFails

    Uploading to claude.ai or the Claude API, or packaging with Anthropic's script, accepts only the six spec fields and stops on anything else.

    • Error

      The file doesn't start with a --- line, so it has no frontmatter. Anthropic's validator stops with "No YAML frontmatter found". F3

      Fix: Start the file with ---, then name: and description: lines, then a closing --- line.

  • OpenAI (Codex & API)Fails

    Codex finds SKILL.md by its exact name and needs a description; OpenAI's Skills API checks the frontmatter against the spec and caps uploads.

    • Error

      The file doesn't start with a --- line, so it has no frontmatter. Codex can't find a name or description and skips the skill. F3

      Fix: Start the file with ---, then name: and description: lines, then a closing --- line.

  • VS Code & CopilotPasses with warnings

    VS Code reads skills one folder below .github/skills, .claude/skills or .agents/skills and falls back to the folder name when the name is missing or differs; GitHub's Copilot docs require the exact name SKILL.md.

    • Warning

      The file doesn't start with a --- line, so it has no frontmatter. VS Code lists the skill under its folder name with no description for the agent to match. F3

      Fix: Start the file with ---, then name: and description: lines, then a closing --- line.

SKILL.md

Files

6 files

PathSize
SKILL.md (opens in a new tab)7.7 KB
references/claude-code.md (opens in a new tab)706 B
references/codex.md (opens in a new tab)706 B
references/dsh.md (opens in a new tab)850 B
references/openclaw.md (opens in a new tab)702 B
references/opencode.md (opens in a new tab)1.3 KB

More from zilliztech/memsearch

  • memory-recall

    zilliztech/memsearch

    Search and recall relevant memories from past sessions via memsearch. Use when the user's question could benefit from historical context, past decisions, debugging notes, previous conversations, or project knowledge -- especially questions like 'what did I decide about X', 'why did we do Y', or 'have I seen this before'. Also use when you see `[memsearch] Recall available if needed` capability hints injected via SessionStart or UserPromptSubmit. Typical flow: search for 3-5 chunks, expand the most relevant, optionally deep-drill into original transcripts via the anchor format. Skip when the question is purely about current code state (use Read/Grep), ephemeral (today's task only), or the user has explicitly asked to ignore memory.

    • Runs shell commands
    • Pre-approves tools
    • +1 more
    Pattern check: 2 items to review

    MIT · 2.8k repo stars · Updated 8 Sept 2026

  • memory-recall

    zilliztech/memsearch

    Search and recall relevant memories from past sessions via memsearch. Use when the user's question could benefit from historical context, past decisions, debugging notes, previous conversations, or project knowledge -- especially questions like 'what did I decide about X', 'why did we do Y', or 'have I seen this before'. Also use when you see `[memsearch] Recall available if needed` capability hints injected via SessionStart or UserPromptSubmit. Typical flow: search for 3-5 chunks, expand the most relevant, optionally deep-drill into original transcripts via the anchor format. Skip when the question is purely about current code state (use Read/Grep), ephemeral (today's task only), or the user has explicitly asked to ignore memory.

    • Runs shell commands
    Pattern check: Nothing flagged

    MIT · 2.8k repo stars · Updated 8 Sept 2026

  • memory-recall

    zilliztech/memsearch

    • Runs shell commands
    Pattern check: Nothing flagged

    MIT · 2.8k repo stars · Updated 26 Oct 2026

  • memory-recall

    zilliztech/memsearch

    Search and recall relevant memories from past sessions via memsearch. Use when the user's question could benefit from historical context, past decisions, debugging notes, previous conversations, or project knowledge -- especially questions like 'what did I decide about X', 'why did we do Y', or 'have I seen this before'. Also use when you see `[memsearch] Memory available` hints injected via SessionStart or UserPromptSubmit. Typical flow: search for 3-5 chunks, expand the most relevant, optionally deep-drill into original transcripts via the anchor format. Skip when the question is purely about current code state (use Read/Grep), ephemeral (today's task only), or the user has explicitly asked to ignore memory.

    • Instructions only
    Pattern check: Nothing flagged

    MIT · 2.8k repo stars · Updated 29 May 2026

  • memory-recall

    zilliztech/memsearch

    Search and recall relevant memories from past sessions via MemSearch. Use for past decisions, debugging notes, previous conversations, and project knowledge, especially when the context includes a MemSearch memory hint. Skip purely current-code questions or when the user asks to ignore memory.

    • Instructions only
    Pattern check: Nothing flagged

    MIT · 2.8k repo stars · Updated 20 Oct 2026

  • memory-to-skill

    zilliztech/memsearch

    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.

    • Runs shell commands
    Pattern check: Nothing flagged

    MIT · 2.8k repo stars · Updated 20 Oct 2026

All skills in zilliztech/memsearch