agentleFS
potterwhitepotterwhite/DeckHand/.claude/skills/plugin-dev/SKILL.md

plugin-dev

Skill1 starsChanged 25 days agoMITView on GitHub

Load this repo's plugin skills from the working tree instead of the installed marketplace snapshot. Use when a plugin skill here looks missing, stale or broken, when edits to SKILL.md have no effect, or when starting local plugin development.

4 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions4 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 4

    1. spences10/skills★ 15same name
    2. PrabhdeepSingh/claude-plugins★ 4same name
    3. changocr/agents-lab★ 0same name
    4. WSmithDR/cli-plugin-template★ 0same 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 repositoryOne other file it gives its agents.

The file

Files
SKILL.md

Load this repo's plugin skills locally

1. Check which copy is loaded

cat ~/.claude/plugins/installed_plugins.json

gitCommitSha ≠ the commit you are working on → a cached snapshot is loaded, not your working tree.

2. Mount the working tree

claude --plugin-dir ./plugins/<name>       # workflow plugins
claude --plugin-dir ./primitives/<name>    # primitives (core)

On a name clash the local copy wins for that session. No need to uninstall.

3. Invoke

/<plugin>:<dir under skills/>

This repo today: /release-please:setup, /appimage:install, /appimage:uninstall, /core:sudo-auth

4. Reload after edits

/reload-plugins

Four things mistaken for bugs

  • Plugin skills do not appear in /skills. Use /plugin.
  • Entries in /skills without a colon are personal skills in ~/.claude/skills/, unrelated to this repo.
  • Without --plugin-dir, editing the working tree and running /reload-plugins does nothing. Committing does nothing either.
  • Pushing to main ≠ users receive it. Bump version in <layer>/<name>/.claude-plugin/plugin.json (<layer> = plugins or primitives).

Before committing

claude plugin validate ./plugins/<name>     # or ./primitives/<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.