agentleFS
PierrickMartosPierrickMartos/Leadership-Skills/.claude/skills/add-plugin/SKILL.md

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

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
  1. Very specific:

    Add a new plugin to the marketplace by updating .claude-plugin/marketplace.json, .cursor-plugin/marketplace.json and README.md.

    line 6
  2. Very specific:

    Add a new entry to the plugins array with name, source, and description

    line 12
  3. Distinctive:

    Use kebab-case for the plugin name

    line 13
  4. Very specific:

    Write the updated .claude-plugin/marketplace.json 6b.

    line 16
  5. Very specific:

    Update the README ## Plugins section (or create it after ## Install and before ## Usage).

    line 19
  6. Distinctive:

    Use "1 skill" (singular) when count is 1, "N skills" (plural) otherwise.

    line 34
  7. Very specific:

    Update the total skill count in the subtitle line (e.g.

    line 36
  8. Distinctive:

    Write the updated README.md

    line 37
  9. Distinctive:

    If $ARGUMENTS is provided, treat it as the plugin name or GitHub repo to add.

    line 39

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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:

  1. Read .claude-plugin/marketplace.json
  2. Add a new entry to the plugins array with name, source, and description
  3. Use kebab-case for the plugin name
  4. For GitHub sources use: { "source": "github", "repo": "owner/repo" }
  5. For local plugins use a relative path starting with ./
  6. Write the updated .claude-plugin/marketplace.json 6b. Read .cursor-plugin/marketplace.json. Add the same entry to its plugins array. Write the updated .cursor-plugin/marketplace.json
  7. Read README.md
  8. Update the README ## Plugins section (or create it after ## Install and before ## Usage). Each plugin is rendered as a <details> dropdown. Count the number of skills/*/SKILL.md files 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)".

  1. Update the total skill count in the subtitle line (e.g. 11 leadership skills for Claude Code, Cursor, and Claude Cowork.). Count all skills/*/SKILL.md files across all plugin directories to get the new total.
  2. Write the updated README.md

If $ARGUMENTS is provided, treat it as the plugin name or GitHub repo to add.

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.