creating-a-plugin_skill

Overview

This skill helps you create and package a Claude Code plugin that groups reusable components—commands, agents, skills, hooks, and MCP servers—so they can be installed and reused across projects. It defines the required plugin manifest, recommended directory layout, and clear templates for each component type. Use it to standardize plugin structure and speed up local testing and deployment.

How this skill works

It inspects and guides the required .claude-plugin/plugin.json manifest and optional files and directories (commands/, agents/, skills/, hooks/, .mcp.json). It describes manifest fields, discovery rules, frontmatter formats for markdown components, hook event patterns, and MCP server config variables. It also provides minimal templates and a local development workflow including installation via file:/// and using a dev marketplace.

When to use it

• You have reusable commands, agents, or skills you want to share across projects
• You need a predictable plugin layout and manifest for local testing or distribution
• You want to register hooks or MCP servers that integrate external tools
• You are organizing multiple plugins in a local development marketplace
• You need guidance on naming, discovery rules, and manifest variables

Best practices

• Use kebab-case for plugin, command, agent, and skill names to ensure correct mapping
• Keep skill files token-efficient and focused—one excellent example beats many mediocre ones
• Include only a minimal plugin.json (name required) and add recommended fields like version and description
• Prefer auto-discovery by placing components in standard directories; list explicit paths only when needed
• Use ${CLAUDE_PLUGIN_ROOT} in manifests to reference plugin files reliably during runtime

Example use cases

• Create a code-review agent with tools Read, Grep, and Bash, then expose it for auto-delegation
• Bundle several slash commands (commands/*.md) for repo maintenance tasks like review-pr or build
• Add hooks to run a formatter after edits or to run setup scripts at session start
• Define an MCP server in .mcp.json to expose a local database tool or web scraper to plugins
• Assemble a dev marketplace to test multiple local plugins and install them via /plugin install file:///