agentleFS
Sign inStart free
nomograph-ainomograph-ai/rune/skill.md

rune

Skill0 starsChanged 7 months agoMITView on GitHub

Registry manager for skills, agents, and rules. Keeps .claude/skills/, .claude/agents/, and .claude/rules/ synced with central registries. Run check after modifying files, sync at session start.

  • Commits and pushes

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. szarkans/multi★ 24same name
    2. CorvidLabs/skills★ 1same 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 repository2 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 0 are distinctive, and 7 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.

  • 7

    Very specific

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

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

    When the user asks about skills: run rune ls to show status.

    line 21
  2. Very specific:

    Wait for explicit approval before running rune push <name>.

    line 47
  3. Very specific:

    If the user has skills, agents, or rules that are not yet managed by rune, help them migrate:

    line 65
  4. Very specific:

    Check if rune is set up: look for .claude/rune.toml.

    line 68
  5. Very specific:

    If it came from a registry, add it to the manifest with rune add <name> --from <registry> [-t type].

    line 71
  6. Very specific:

    If it was written locally and should be shared, suggest creating a registry (a git repo with skills/, agents/, rules/ dirs) and using rune …

    line 73
  7. Very specific:

    Run rune sync to verify everything resolves.

    line 80

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

rune -- registry manager

Manages skills, agents, and rules across projects via git-based registries. Skills are markdown files in .claude/skills/ that teach agents how to perform workflows. Agents are subagent definitions in .claude/agents/. Rules are conditional instructions in .claude/rules/. rune keeps them current.

When to invoke

  • After modifying any file in .claude/skills/, .claude/agents/, or .claude/rules/: run rune check to detect drift. If drifted, ask the user if they want to push.
  • At session start: muxr pre_create hook runs rune sync automatically. You do not need to run sync yourself.
  • When the user asks about skills: run rune ls to show status.
  • When adding an item: rune add <name> --from <registry> [-t type].

Commands

rune check                    # show drift for all items
rune check --file PATH        # check a specific file (used by hook)
rune sync                     # pull updates from all registries
rune push <name>              # push local changes back to registry
rune add <name> --from <reg>  # add a skill from a registry
rune add <name> -t agent      # add an agent
rune add <name> -t rule       # add a rule
rune ls                       # list items and sync status
rune init                     # create .claude/rune.toml for this project
rune setup                    # one-time: create config + install hook

After modifying a skill file

The PostToolUse hook fires automatically and shows drift. When you see drift output, present it to the user:

"I updated <name>.md. It now differs from the <registry> registry. Want me to push this change upstream so other projects get it?"

Wait for explicit approval before running rune push <name>. This is an external write -- the same approval gate as git push.

Output format

  tidy                     CURRENT                        registry: public
  voice                    DRIFTED  local is newer        registry: private
  mirror                   MISSING                        registry: public
  • CURRENT: local matches registry
  • DRIFTED: local and registry differ (direction shown)
  • MISSING: in manifest but not on disk (run sync)
  • REGISTRY MISSING: in manifest but not in registry

Organizing an existing .claude/ directory with rune

If the user has skills, agents, or rules that are not yet managed by rune, help them migrate:

  1. Check if rune is set up: look for .claude/rune.toml. If missing, run rune init.
  2. For each file in .claude/skills/, .claude/agents/, .claude/rules/:
    • If it came from a registry, add it to the manifest with rune add <name> --from <registry> [-t type].
    • If it was written locally and should be shared, suggest creating a registry (a git repo with skills/, agents/, rules/ dirs) and using rune push <name> after adding it to the manifest.
  3. Files in .claude/commands/ should be moved to .claude/skills/. Claude Code merged commands into skills in v2.1.3. Move the file to a skill directory: mkdir -p .claude/skills/<name> then mv .claude/commands/<name>.md .claude/skills/<name>/SKILL.md.
  4. Run rune sync to verify everything resolves.

Configuration

  • ~/.config/rune/config.toml -- registries (name, url, branch)
  • .claude/rune.toml -- per-project manifest (skills, agents, rules)

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