agentleFS
Sign inStart free
TheKontextCoTheKontextCo/kontext-claude-plugin/skills/save-skill/SKILL.md

save-skill

Skill1 starsChanged 3 months agoMITView on GitHub

Save a reusable Agent Skill to Kontext so it is available from any MCP client

2 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions2 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 2

    1. MosoFin/mosofin-mcp-plugin★ 3same name
    2. MosoFin/mosofin-plugins★ 3same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository9 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 0 are distinctive, and 6 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 6

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read SKILL.md. Its frontmatter name and description become the Skill's identity in Kontext, so check they are actually present and that the …

    line 20
  2. Very specific:

    Never call save_skill with a partial file list.

    line 28
  3. Very specific:

    Call list_skills first. Saving the same name replaces the stored package outright.

    line 35
  4. Very specific:

    If a Skill with this name already exists, get_skill and tell the user what will be replaced before you overwrite it.

    line 37
  5. Very specific:

    If the local copy is *older* than the stored one, stop and say so rather than silently reverting their work.

    line 39
  6. Very specific:

    Call save_skill, then report the name, the file count, and the markdownLink.

    line 47

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Save a Skill to Kontext

Package and store the Skill: $ARGUMENTS

Kontext keeps complete, portable Skill packages, so a Skill saved from this repository is retrievable from every MCP client the user connects.

Assemble the package

  1. Locate the Skill root — the directory holding SKILL.md. $ARGUMENTS may be a path or a name; with a name, glob for **/skills/<name>/SKILL.md and **/<name>/SKILL.md.
  2. Read SKILL.md. Its frontmatter name and description become the Skill's identity in Kontext, so check they are actually present and that the description states when to use the Skill, not just what it does.
  3. Glob the whole package and read every supporting text file — references, examples, scripts. Paths are relative to the Skill root.

files is the authoritative snapshot, not a patch: it must carry the root SKILL.md plus every supporting file, and any path present on a previous save but omitted now is deleted. Never call save_skill with a partial file list.

Binary assets cannot be stored. If the package depends on one, save the rest and tell the user which file was dropped and that the Skill will not be complete without it.

Check for an existing copy

Call list_skills first. Saving the same name replaces the stored package outright.

  • If a Skill with this name already exists, get_skill and tell the user what will be replaced before you overwrite it.
  • If the local copy is older than the stored one, stop and say so rather than silently reverting their work. read_skill_file pulls a single stored file when you need to compare one rather than the whole package.
  • To retire a Skill rather than replace it, use manage_skill — archive is reversible, deletion is not and needs a preview plus explicit confirmation.

Save and confirm

Call save_skill, then report the name, the file count, and the markdownLink.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free