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
- marinvch/Cortextheir own version, first seen Nov 1, 2026
- garbageek/claude-pluginstheir own version, first seen Oct 13, 2026
- PierrickMartos/Leadership-Skillstheir own version, first seen Apr 28, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- PierrickMartos/Leadership-Skills★ 4same name
- garbageek/claude-plugins★ 1same name
- marinvch/Cortex★ 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 repository11 other files it gives its agents.
- .claude/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- .claude-plugin/CLAUDE.mdCLAUDE.md
- .claude/teams/CLAUDE.mdCLAUDE.md
- docs/CLAUDE.mdCLAUDE.md
- .github/CLAUDE.mdCLAUDE.md
- site/CLAUDE.mdCLAUDE.md
- add-pluginSkill
- list-pluginsSkill
- remove-pluginSkill
- vet-pluginSkill
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
- Very specific: line 16
Update a listed plugin's entry, all the way to a PR.
- Very specific: line 34
Sync docs: Run bash .claude/skills/add-plugin/scripts/sync-readme.sh and bash .claude/skills/add-plugin/scripts/sync-site.sh (gate …
- Very specific: line 38
Verify: Run bash tests/gates/run-all.sh and claude plugin validate .
- Very specific: line 51
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 …
“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.
Files
/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
- Confirm it's listed. The entry
<name>must exist in.claude-plugin/marketplace.json; if not, tell the user to use/add-pluginand stop. - Re-vet + curate. Delegate to the
plugin-onboardersubagent in update mode for the target repo (the--repooverride, or the entry's currentsource.repo): it runsvet-candidate.sh --skip-listed-check <repo>and, if clean, returns a refresheddescription/keywordsproposal. If blocked (e.g. the target now ships its ownmarketplace.json, or the owner isn'todere-pro), print the blockers and stop. If--descriptionor--keywordswere supplied by the caller, they override the subagent's values when passed toupdate-entry.shin step 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. - Sync docs. Run
bash .claude/skills/add-plugin/scripts/sync-readme.shandbash .claude/skills/add-plugin/scripts/sync-site.sh(gate18-pages-in-syncfails if the Pagessite/drifts from the manifest), then add aCHANGELOG.mdbullet under## [Unreleased](e.g.- Update \<name>` …`). - Verify. Run
bash tests/gates/run-all.shandclaude plugin validate .— both green. - PR. Branch
feat/update-<name>,git addthe manifest + README + CHANGELOG +site/, commitfeat: 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 generatedsite/; never setsversion/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.
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
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.

