agentleFS
odere-proodere-pro/claude-software-3-0-marketplace/.claude/skills/remove-plugin/SKILL.md

remove-plugin

Skill2 starsChanged 5 months agoMITView on GitHub

Author-only maintenance skill for the odere-pro marketplace repo. Removes a listed plugin from the registry end to end: deletes its entry from .claude-plugin/marketplace.json, regenerates the README table, updates CHANGELOG, runs the gate suite, then opens a PR. Invoke explicitly as /remove-plugin <name>. Edits files.

  • Commits and pushes

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 1 is distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

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

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

    Remove a listed plugin from the marketplace, all the way to a PR.

    line 16
  2. Very specific:

    Remove the entry: Run bash .claude/skills/add-plugin/scripts/remove-entry.sh <name>.

    line 21
  3. Very specific:

    Sync docs: Run bash .claude/skills/add-plugin/scripts/sync-readme.sh (regenerates the table.

    line 23
  4. Very specific:

    Verify: Run bash tests/gates/run-all.sh — it must be green.

    line 28
  5. Distinctive:

    If any step fails (the name isn't listed, a gate goes red, or the PR push fails), stop and roll back so the working tree is left exactly as …

    line 42

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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

/remove-plugin

Remove a listed plugin from the marketplace, all the way to a PR. $ARGUMENTS is the entry name (as it appears in .claude-plugin/marketplace.json / the README table).

Steps

  1. Remove the entry. Run bash .claude/skills/add-plugin/scripts/remove-entry.sh <name>. If the name isn't listed, the script errors — report that and stop (nothing to remove).
  2. Sync docs. Run bash .claude/skills/add-plugin/scripts/sync-readme.sh (regenerates the table; shows the placeholder if that was the last plugin) and bash .claude/skills/add-plugin/scripts/sync-site.sh (regenerates the Pages site/; gate 18-pages-in-sync fails if it drifts), then add a CHANGELOG.md bullet under ## [Unreleased] (e.g. - Remove \<name>` from the marketplace.`).
  3. Verify. Run bash tests/gates/run-all.sh — it must be green. (02-marketplace-shape accepts an empty registry, so removing the last entry is fine.)
  4. PR. Branch chore/remove-<name>, git add the manifest + README + CHANGELOG + site/, commit chore: remove <name> from the odere-pro marketplace (human-authored — no AI attribution), push -u, gh pr create with a short body. Report the PR URL.

Boundaries

  • Touches only .claude-plugin/marketplace.json, README.md, CHANGELOG.md, and the generated site/; never the plugin's own repo.
  • Removal is by entry name; to change a plugin instead of dropping it, use /update-plugin.

Failure handling

If any step fails (the name isn't listed, a gate goes red, or the PR push fails), stop and roll back so the working tree is left exactly as it started — never half applied. Undo both the staged and the working-tree state of the paths this skill touches:

git restore --staged .claude-plugin/marketplace.json README.md CHANGELOG.md site/
git restore .claude-plugin/marketplace.json README.md CHANGELOG.md site/

git restore --staged … first unstages anything git added in step 4; the second git restore … discards the working-tree edits from steps 1–2. Then report what failed and what you reverted. Do not commit or push a partial change.

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.