agentleFS
Sign inStart free
stacklokstacklok/toolhive-studio/.claude/skills/skill-editor/SKILL.md

skill-editor

Skill173 starsChanged 5 months agoApache-2.0View on GitHub

REQUIRED for editing any skill file. Ensures changes sync to Claude, Codex, and Cursor. Never edit .claude/skills/ files directly - always use this skill.

  • Deletes or force-pushes

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 3 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

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

    Read the current skill content from .claude/skills/<name>/SKILL.md

    line 32
  2. Distinctive:

    Always verify sync after editing:

    line 42
  3. Distinctive:

    No output means files are identical.

    line 49
  4. Very specific:

    Add references: - Create references/ directory for supporting docs

    line 56
  5. Distinctive:

    Remove from all three locations:

    line 60

≈ “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

Skill Editor

Edit existing AI agent skills while keeping Claude, Codex, and Cursor in sync.

Workflow

  1. Always edit Claude first - .claude/skills/<name>/SKILL.md is the canonical source
  2. Replicate with CLI - Copy changes to .codex/skills/ and .cursor/skills/
  3. Never edit Codex/Cursor directly - They are copies of Claude's version

Finding Existing Skills

List all skills:

ls -la .claude/skills/

Read a skill:

cat .claude/skills/<name>/SKILL.md

Editing a Skill

  1. Read the current skill content from .claude/skills/<name>/SKILL.md
  2. Make the requested changes
  3. Replicate to other agents:
    cp .claude/skills/<name>/SKILL.md .codex/skills/<name>/
cp .claude/skills/<name>/SKILL.md .cursor/skills/<name>/

Verification

Always verify sync after editing:

diff .claude/skills/<name>/SKILL.md .codex/skills/<name>/SKILL.md
diff .claude/skills/<name>/SKILL.md .cursor/skills/<name>/SKILL.md

No output means files are identical.

Common Edits

  • Update description - Improve auto-discovery keywords
  • Add instructions - Expand the skill's capabilities
  • Fix errors - Correct mistakes in the skill logic
  • Add references - Create references/ directory for supporting docs

Deleting a Skill

Remove from all three locations:

rm -rf .claude/skills/<name> .codex/skills/<name> .cursor/skills/<name>

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