How do I install the Developing Claude Code Plugins skill?

Run npx skillmds@latest add diegosouzapw/developing-claude-code-plugins in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Developing Claude Code Plugins safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Developing Claude Code Plugins?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Developing Claude Code Plugins free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Developing Claude Code Plugins?

diegosouzapw (@diegosouzapw) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Developing Claude Code Plugins by diegosouzapw

Name: Developing Claude Code Plugins
Rating: 4.5 (4 reviews)
Author: diegosouzapw

Developing Claude Code Plugins

Build, test, and distribute Claude Code plugins with slash commands, agents, skills, hooks, MCP servers, and LSP servers. MUST be loaded when creating, reviewing, debugging, or distributing plugins. Use PROACTIVELY when user mentions plugins, extensions, marketplaces, or wants to add custom commands/agents to Claude Code.

diegosouzapw Updated Sep 8, 2026 54 repo stars

File contents

1. Plugin Structure Is Sacred

my-plugin/
├── .claude-plugin/
│   └── plugin.json          # ONLY manifest here (required)
├── commands/                 # Slash commands (plugin root)
├── agents/                   # Subagent definitions (plugin root)
├── skills/                   # Agent Skills (plugin root)
├── hooks/
│   └── hooks.json           # Event handlers (plugin root)
├── .mcp.json                # MCP server configs (plugin root)
└── .lsp.json                # LSP server configs (plugin root)

CRITICAL: Never put commands/, agents/, skills/, or hooks/ inside .claude-plugin/. Only plugin.json goes there.

2. Namespacing Prevents Conflicts

Plugin commands use format /plugin-name:command-name. The name field in plugin.json becomes the namespace prefix. Choose names carefully - they're public-facing.

3. Use ${CLAUDE_PLUGIN_ROOT} for Paths

All paths in hooks, MCP servers, and scripts must use ${CLAUDE_PLUGIN_ROOT} to reference plugin files. Plugins are copied to a cache directory, so relative paths like ../ won't work.

4. Test with --plugin-dir During Development

claude --plugin-dir ./my-plugin

This loads your plugin without installation. Restart Claude Code after changes.

Create a new plugin
Add a component (command, agent, skill, hook, MCP, LSP)
Test or debug a plugin
Create a marketplace for distribution
Something else

Wait for response before proceeding.

After reading the workflow, follow it exactly.

Validate plugin structure:

claude plugin validate ./my-plugin

Test plugin loads:

claude --plugin-dir ./my-plugin

Verify components appear:

Commands: /help shows plugin commands
Agents: /agents lists plugin agents
MCP: /mcp shows server status

Report to user:

"Plugin validates: ✓"
"Commands registered: X"
"Ready for testing"

Structure: plugin-structure.md Components: commands.md, agents.md, skills.md, hooks.md, mcp-lsp.md Distribution: marketplace.md Issues: troubleshooting.md

Workflow	Purpose
create-plugin.md	Create new plugin from scratch
add-component.md	Add command, agent, skill, hook, MCP, or LSP
test-debug-plugin.md	Test locally and fix issues
create-marketplace.md	Create and host plugin marketplace

---name: developing-claude-code-pluginsdescription: Build, test, and distribute Claude Code plugins with slash commands, agents, skills, hooks, MCP servers, and LSP servers. MUST be loaded when creating, reviewing, debugging, or distributing plugins. Use PROACTIVELY when user mentions plugins, extensions, marketplaces, or wants to add custom commands/agents to Claude Code.---<essential_principles>Plugins extend Claude Code with reusable functionality: custom slash commands, agents, skills, hooks, MCP servers, and LSP servers. Unlike standalone `.claude/` configurations, plugins are namespaced, versioned, and distributable through marketplaces.**1. Plugin Structure Is Sacred**```my-plugin/├── .claude-plugin/│ └── plugin.json # ONLY manifest here (required)├── commands/ # Slash commands (plugin root)├── agents/ # Subagent definitions (plugin root)├── skills/ # Agent Skills (plugin root)├── hooks/│ └── hooks.json # Event handlers (plugin root)├── .mcp.json # MCP server configs (plugin root)└── .lsp.json # LSP server configs (plugin root)```**CRITICAL**: Never put commands/, agents/, skills/, or hooks/ inside `.claude-plugin/`. Only `plugin.json` goes there.**2. Namespacing Prevents Conflicts**Plugin commands use format `/plugin-name:command-name`. The `name` field in plugin.json becomes the namespace prefix. Choose names carefully - they're public-facing.**3. Use `${CLAUDE_PLUGIN_ROOT}` for Paths**All paths in hooks, MCP servers, and scripts must use `${CLAUDE_PLUGIN_ROOT}` to reference plugin files. Plugins are copied to a cache directory, so relative paths like `../` won't work.**4. Test with `--plugin-dir` During Development**```bashclaude --plugin-dir ./my-plugin```This loads your plugin without installation. Restart Claude Code after changes.</essential_principles><intake>**What would you like to do?**1. Create a new plugin2. Add a component (command, agent, skill, hook, MCP, LSP)3. Test or debug a plugin4. Create a marketplace for distribution5. Something else**Wait for response before proceeding.**</intake><routing>| Response | Workflow ||----------|----------|| 1, "new", "create", "build", "start", "plugin" | `workflows/create-plugin.md` || 2, "add", "component", "command", "agent", "skill", "hook", "mcp", "lsp" | `workflows/add-component.md` || 3, "test", "debug", "fix", "error", "not working", "broken" | `workflows/test-debug-plugin.md` || 4, "marketplace", "distribute", "share", "publish" | `workflows/create-marketplace.md` || 5, other | Clarify intent, then route to appropriate workflow |**After reading the workflow, follow it exactly.**</routing><verification_loop>**After Every Change:**1. Validate plugin structure:```bashclaude plugin validate ./my-plugin```2. Test plugin loads:```bashclaude --plugin-dir ./my-plugin```3. Verify components appear:- Commands: `/help` shows plugin commands- Agents: `/agents` lists plugin agents- MCP: `/mcp` shows server statusReport to user:- "Plugin validates: ✓"- "Commands registered: X"- "Ready for testing"</verification_loop><reference_index>All in `references/`:**Structure:** plugin-structure.md**Components:** commands.md, agents.md, skills.md, hooks.md, mcp-lsp.md**Distribution:** marketplace.md**Issues:** troubleshooting.md</reference_index><workflows_index>All in `workflows/`:| Workflow | Purpose ||----------|---------|| create-plugin.md | Create new plugin from scratch || add-component.md | Add command, agent, skill, hook, MCP, or LSP || test-debug-plugin.md | Test locally and fix issues || create-marketplace.md | Create and host plugin marketplace |</workflows_index><success_criteria>A well-built plugin:- Has valid plugin.json manifest in `.claude-plugin/`- Components are in correct directories (commands/, agents/, skills/, hooks/)- All paths use `${CLAUDE_PLUGIN_ROOT}` variable- Passes `claude plugin validate`- Loads correctly with `--plugin-dir`- Commands appear in `/help` output</success_criteria>

Frequently asked questions