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

update-plugin

Skill2 starsChanged 5 months agoMITView on GitHub

Author-only maintenance skill for the odere-pro marketplace repo. Updates a listed plugin's entry: refreshes its description/keywords/homepage/license from the source repo's plugin.json, and can repoint it to a different odere-pro repo (--repo) or rename it (--name). Regenerates the README, updates CHANGELOG, runs gates, opens a PR. Invoke explicitly as /update-plugin <name>. Edits files.

  • Commits and pushes

3 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

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

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 0

    Distinctive

    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:

    Update a listed plugin's entry, all the way to a PR.

    line 16
  2. Very specific:

    Sync docs: Run bash .claude/skills/add-plugin/scripts/sync-readme.sh and bash .claude/skills/add-plugin/scripts/sync-site.sh (gate …

    line 34
  3. Very specific:

    Verify: Run bash tests/gates/run-all.sh and claude plugin validate .

    line 38
  4. Very specific:

    If any step fails (the target is blocked on re-vet, a gate goes red, claude plugin validate errors, or the PR push fails), stop and roll …

    line 51

“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “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

/update-plugin

Update a listed plugin's entry, all the way to a PR. Covers refresh (re-pull metadata from the plugin's plugin.json), replace/repoint (--repo <owner/repo>), and rename (--name).

$ARGUMENTS: the existing entry name, plus optional --repo <owner/repo> and --name <new-name>.

Steps

  1. Confirm it's listed. The entry <name> must exist in .claude-plugin/marketplace.json; if not, tell the user to use /add-plugin and stop.
  2. Re-vet + curate. Delegate to the plugin-onboarder subagent in update mode for the target repo (the --repo override, or the entry's current source.repo): it runs vet-candidate.sh --skip-listed-check <repo> and, if clean, returns a refreshed description / keywords proposal. If blocked (e.g. the target now ships its own marketplace.json, or the owner isn't odere-pro), print the blockers and stop. If --description or --keywords were supplied by the caller, they override the subagent's values when passed to update-entry.sh in step 3.
  3. Apply. Run bash .claude/skills/add-plugin/scripts/update-entry.sh <name> [--repo …] [--name …] [--description "…"] [--keywords a,b] with the curated values. It re-vets and replaces the entry in place.
  4. Sync docs. Run bash .claude/skills/add-plugin/scripts/sync-readme.sh and bash .claude/skills/add-plugin/scripts/sync-site.sh (gate 18-pages-in-sync fails if the Pages site/ drifts from the manifest), then add a CHANGELOG.md bullet under ## [Unreleased] (e.g. - Update \<name>` …`).
  5. Verify. Run bash tests/gates/run-all.sh and claude plugin validate . — both green.
  6. PR. Branch feat/update-<name>, git add the manifest + README + CHANGELOG + site/, commit feat: update <name> in the odere-pro marketplace (human-authored), push -u, gh pr create. Report the PR URL.

Boundaries

  • The entry must already exist (this never adds). odere-pro repos only; never edits the plugin's repo.
  • Touches only .claude-plugin/marketplace.json, README.md, CHANGELOG.md, and the generated site/; never sets version/sha/commit.

Failure handling

If any step fails (the target is blocked on re-vet, a gate goes red, claude plugin validate errors, 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 6; the second git restore … discards the working-tree edits from steps 3–4. 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.