agentleFS
Sign inStart free
jeongskjeongsk/claude-skills/.claude/skills/creating-plugins/SKILL.md

creating-plugins

Skill10 starsChanged 10 months agoMITView on GitHub

Guide for creating Claude Code plugins with commands, agents, skills, hooks, and MCP servers. Use when the user wants to create a new plugin, add plugin components (commands, agents, hooks), set up a plugin marketplace, or needs help with plugin.json configuration.

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 7 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Create Claude Code plugins to extend functionality with custom commands, agents, skills, hooks, and MCP servers.

    line 8
  2. Distinctive:

    Create a test marketplace:

    line 54

“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

Plugin Creator

Create Claude Code plugins to extend functionality with custom commands, agents, skills, hooks, and MCP servers.

Plugin Creation Workflow

1. Gather Requirements

Ask the user:

  • What functionality should the plugin provide?
  • Which components are needed? (commands, agents, hooks, MCP servers, skills)
  • Who is the target audience? (personal, team, public)

2. Create Plugin Structure

my-plugin/
├── .claude-plugin/
│   └── plugin.json      # Required
├── commands/            # Optional: slash commands
├── agents/              # Optional: sub-agents
├── skills/              # Optional: agent skills
├── hooks/               # Optional: event handlers
└── .mcp.json           # Optional: MCP servers

3. Write plugin.json

Minimal example:

{
  "name": "my-plugin",
  "description": "Brief description",
  "version": "1.0.0",
  "author": {"name": "Author Name"}
}

4. Add Components

Based on user requirements, add:

  • Commands: See commands.md for slash command format
  • Agents: See agents.md for agent definition format
  • Hooks: See hooks.md for event handler configuration
  • MCP Servers: See mcp-servers.md for server configuration

5. Test Locally

Create a test marketplace:

mkdir test-marketplace/.claude-plugin

Create test-marketplace/.claude-plugin/marketplace.json:

{
  "name": "test-marketplace",
  "owner": {"name": "Developer"},
  "plugins": [{"name": "my-plugin", "source": "./my-plugin"}]
}

Test commands:

/plugin marketplace add ./test-marketplace
/plugin install my-plugin@test-marketplace

Quick Reference

Command File (commands/hello.md)

---
description: Greet the user
---
# Hello Command
Greet the user warmly.

Agent File (agents/reviewer.md)

---
description: Code review specialist
capabilities: ["review", "suggestions"]
---
# Reviewer
Review code for quality and best practices.

Hooks (hooks/hooks.json)

{
  "hooks": {
    "PostToolUse": [{
      "matcher": "Write|Edit",
      "hooks": [{"type": "command", "command": "prettier --write $CLAUDE_FILE_PATH"}]
    }]
  }
}

References

Plugin Development

  • Plugins Guide - Complete plugin creation guide
  • Plugins Reference - Technical schemas and configurations
  • Plugin Structure - Directory layout and plugin.json schema
  • Marketplace - Plugin distribution

Plugin Components

  • Commands - Slash command format
  • Agents - Sub-agent definitions
  • Hooks - Event handlers
  • MCP Servers - External tool integration

Skills Development

  • Skills Overview - What skills are and how they work
  • Skills Best Practices - Writing effective skills
  • Skills Schema - SKILL.md format and validation

Download now (ZIP)

  • Other versions8 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 8

    1. emdash-cms/emdash★ 14ksame name
    2. jaktestowac/awesome-copilot-for-testers★ 118same name
    3. emdash-cms/skills★ 10same name
    4. EngDawood/emdash-claude-plugin★ 4same name
    5. EngDawood/emdash-claude-skills★ 4same name
    6. EngDawood/modern-emdash-cms★ 2same name
    7. rfdnxbro/claude-code-marketplace★ 2same name
    8. NothingFancyAI/skills★ 0same 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.

  • Used alongsideProjects with it also use building-emdash-site, emdash-cli and 4 more.

    Other files people use alongside this one.

    Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
    • EngDawoodSkill

      building-emdash-site

      Build and customize EmDash CMS sites on Astro. Use when creating pages, defining collections, writing seed files, querying content, rendering Portable Text, setting up menus/taxonomies/widgets, configuring deployment, or any task involving an EmDash-powered Astro site. Assumes basic Astro knowledge but provides all EmDash-specific patterns.

      Also in 4 projects that use this

    • EngDawoodSkill

      emdash-cli

      Use the EmDash CLI to manage content, schema, media, and more. Use this skill when you need to interact with a running EmDash instance from the command line — creating content, managing collections, uploading media, generating types, or scripting CMS operations.

      Also in 4 projects that use this

    • DerivativeLabsSkill

      adversarial-reviewer

      Argue against proposed actions to test judgment quality. Not \"is the code correct\" but \"should we be doing this at all?\" Aligned with robustness, not performance.. Use when: review, adversarial, challenge

      Also in 3 projects that use this

    • VercelSkill

      agent-browser

      Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.

      Also in 3 projects that use this

    • +2 more from EngDawood
  • In this repositoryOne other file it gives its agents.

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.

Check your setup, free