add-plugin
Skill2 starsChanged 5 months agoMITView on GitHub
Author-only maintenance skill for the odere-pro marketplace repo. Adds an odere-pro plugin to the registry end to end: vets the candidate repo, inserts a well-formed entry into .claude-plugin/marketplace.json, regenerates the README table, updates CHANGELOG, runs the gate suite, then opens a PR. Invoke explicitly as /add-plugin <repo> [--name <name>]. Edits files.
- Commits and pushes
7 other projects use a version of this.
Adopted by
Most recently taken up by
- SumitShinde0702/aipaysdktheir own version, first seen Nov 16, 2026
- github/plugin-marketplace-startertheir own version, first seen Nov 15, 2026
- cTuningLabs/cmetatheir own version, first seen Nov 8, 2026
- worldliberty/agentpay-sdktheir own version, first seen Nov 1, 2026
- fastrepl/anarlogtheir own version, first seen Oct 8, 2026
- fastrepl/hyprnotetheir own version, first seen Oct 8, 2026
Other versions7 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 7
- fastrepl/anarlog★ 9.9ksame name
- fastrepl/hyprnote★ 9.9ksame name
- worldliberty/agentpay-sdk★ 460same name
- cTuningLabs/cmeta★ 9same name
- github/plugin-marketplace-starter★ 7same name
- PierrickMartos/Leadership-Skills★ 4same name
- SumitShinde0702/aipaysdk★ 2same 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
- list-pluginsSkill
- remove-pluginSkill
- update-pluginSkill
- vet-pluginSkill
The file
We split this skill into the rules it gives an agent
9 rules. 0 are common, 0 are distinctive, and 9 are very specific to this project.
0
Common
Most of the 7 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
9
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 16
Add an odere-pro plugin to this marketplace, all the way to a PR.
- Very specific: line 29
If --description or --keywords were supplied by the caller, they override the subagent's curated values when passed to add-entry.sh in step …
- Very specific: line 31
Stop on blockers: If the proposal is not ok, print each blocker and the fix and stop — make no edits.
- Very specific: line 35
Insert the entry: Run bash ${CLAUDE_SKILL_DIR}/scripts/add-entry.sh <repo> [--name …] [--description "…"] [--keywords a,b], passing the …
- Very specific: line 39
Sync docs: Run bash ${CLAUDE_SKILL_DIR}/scripts/sync-readme.sh to regenerate the README Plugins table and bash …
- Very specific: line 43
Verify: Run bash tests/gates/run-all.sh and claude plugin validate .
- Very specific: line 45
PR.: Create a branch feat/add-<name>, git add the manifest + README + CHANGELOG + site/, commit feat: list <name> in the odere-pro …
- Very specific: line 53
Never sets version/sha/commit on an entry.
- Very specific: line 57
If any step fails (a blocker surfaces, a gate goes red, claude plugin validate errors, or the PR push fails), stop and roll back so the …
“Common” is measured: kept by at least 6 in 10 of the 7 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
/add-plugin
Add an odere-pro plugin to this marketplace, all the way to a PR. The deterministic file surgery is
done by the bundled scripts under ${CLAUDE_SKILL_DIR}/scripts/; this skill orchestrates and handles
judgment (curated description / keywords). The full process and contract are in
docs/adding-plugins.md.
$ARGUMENTS is the candidate repo (<repo> defaults the owner to odere-pro, or pass owner/repo),
plus optional --name <name> to override the entry name.
Steps
- Vet + curate. Delegate to the
plugin-onboardersubagent with the repo argument. It runsvet-candidate.sh, and if clean, returns a structured proposal:repo,name, a marketplace-qualitydescription,homepage,license,keywords, and anyblockers. If--descriptionor--keywordswere supplied by the caller, they override the subagent's curated values when passed toadd-entry.shin step 3. - Stop on blockers. If the proposal is not
ok, print each blocker and the fix and stop — make no edits. The most common blocker: the candidate still ships its own.claude-plugin/marketplace.json(theodere-proname collision). Tell the user to remove it in that repo first (the same change made for claude-oop-excellence / claude-calibration), then re-run. Seedocs/adding-plugins.md. - Insert the entry. Run
bash ${CLAUDE_SKILL_DIR}/scripts/add-entry.sh <repo> [--name …] [--description "…"] [--keywords a,b], passing the curated description/keywords. The script re-vets, refuses duplicates, and writes the entry withjq --indent 2. - Sync docs. Run
bash ${CLAUDE_SKILL_DIR}/scripts/sync-readme.shto regenerate the README Plugins table andbash ${CLAUDE_SKILL_DIR}/scripts/sync-site.shto regenerate the Pagessite/(gate18-pages-in-syncfails ifsite/drifts from the manifest), then add aCHANGELOG.mdbullet under## [Unreleased](e.g.- List \<name>`.`). - Verify. Run
bash tests/gates/run-all.shandclaude plugin validate . --strict. Both must be green before continuing. - PR. Create a branch
feat/add-<name>,git addthe manifest + README + CHANGELOG +site/, commitfeat: list <name> in the odere-pro marketplace(human-authored — no AI attribution), push-u, andgh pr createwith a short body. Report the PR URL.
Boundaries
- odere-pro repos only; never edits a candidate's own repository (block-with-instructions).
- Touches only
.claude-plugin/marketplace.json,README.md,CHANGELOG.md, and the generatedsite/. - Never sets
version/sha/commiton an entry; the scripts and themarketplace-guardhook enforce it.
Failure handling
If any step fails (a blocker surfaces, 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.

