add-plugin
Skill4 starsChanged 7 months agoMITView on GitHub
Add a new plugin entry to the marketplace catalog. Use when registering a new plugin in marketplace.json.
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
- odere-pro/claude-software-3-0-marketplace★ 2same 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 repository4 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- link-for-testingSkill
- update-pluginSkill
- validate-marketplaceSkill
The file
We split this skill into the rules it gives an agent
9 rules. 0 are common, 4 are distinctive, and 5 are very specific to this project.
0
Common
Most of the 7 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 6
Add a new plugin to the marketplace by updating .claude-plugin/marketplace.json, .cursor-plugin/marketplace.json and README.md.
- Very specific: line 12
Add a new entry to the plugins array with name, source, and description
- Distinctive: line 13
Use kebab-case for the plugin name
- Very specific: line 16
Write the updated .claude-plugin/marketplace.json 6b.
- Very specific: line 19
Update the README ## Plugins section (or create it after ## Install and before ## Usage).
- Distinctive: line 34
Use "1 skill" (singular) when count is 1, "N skills" (plural) otherwise.
- Very specific: line 36
Update the total skill count in the subtitle line (e.g.
- Distinctive: line 37
Write the updated README.md
- Distinctive: line 39
If $ARGUMENTS is provided, treat it as the plugin name or GitHub repo to add.
“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 a new plugin to the marketplace by updating .claude-plugin/marketplace.json, .cursor-plugin/marketplace.json and README.md.
The user will provide: plugin name, source (GitHub repo, relative path, or npm package), and a short description.
Steps:
- Read
.claude-plugin/marketplace.json - Add a new entry to the
pluginsarray withname,source, anddescription - Use kebab-case for the plugin name
- For GitHub sources use:
{ "source": "github", "repo": "owner/repo" } - For local plugins use a relative path starting with
./ - Write the updated
.claude-plugin/marketplace.json6b. Read.cursor-plugin/marketplace.json. Add the same entry to itspluginsarray. Write the updated.cursor-plugin/marketplace.json - Read
README.md - Update the README
## Pluginssection (or create it after## Installand before## Usage). Each plugin is rendered as a<details>dropdown. Count the number ofskills/*/SKILL.mdfiles in the plugin directory to determine the skill count. Use this format:
<details>
<summary><strong><code>plugin-name</code></strong> (N skills) — Short plugin description.</summary>
Claude Code: `/plugin install plugin-name@leadership-skills`
| Skill | Purpose |
|-------|---------|
| `skill-name` | Skill description. |
</details>Use "1 skill" (singular) when count is 1, "N skills" (plural) otherwise. If the plugin has no skills yet, use "(0 skills)".
- Update the total skill count in the subtitle line (e.g.
11 leadership skills for Claude Code, Cursor, and Claude Cowork.). Count allskills/*/SKILL.mdfiles across all plugin directories to get the new total. - Write the updated README.md
If $ARGUMENTS is provided, treat it as the plugin name or GitHub repo to add.
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.

