Agent skill
claude-plugin-creator
Claude Code plugin creation guide. Use when creating new plugins, adding commands/skills/hooks/MCP servers to plugins, or setting up marketplace distribution. Triggers on "create plugin", "add command", "add skill", "add hook", "plugin structure".
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/data/claude-plugin-creator
SKILL.md
Claude Code Plugin Creator
Guide for creating Claude Code plugins with correct structure and components.
Plugin Structure
my-plugin/
├── .claude-plugin/
│ └── plugin.json # Required: Plugin metadata
├── commands/ # Optional: Slash commands
│ └── my-command.md
├── skills/ # Optional: Agent skills
│ └── my-skill/
│ └── SKILL.md
├── hooks/ # Optional: Event handlers
│ └── hooks.json
└── .mcp.json # Optional: MCP servers
Quick Start
1. Create Plugin Directory
mkdir -p my-plugin/.claude-plugin
2. Create plugin.json
{
"name": "my-plugin",
"description": "Plugin description",
"version": "1.0.0",
"author": { "name": "Your Name" }
}
3. Add Components
- Commands: See commands.md
- Skills: See skills.md
- Hooks: See hooks.md
- MCP Servers: See mcp.md
Adding to Marketplace
For this repository, add plugin to .claude-plugin/marketplace.json:
{
"plugins": [
{
"name": "my-plugin",
"source": "./my-plugin",
"description": "Plugin description"
}
]
}
Validation
Run validation script before committing:
./validate-plugin.sh my-plugin
Component Reference
| Component | Location | Format | Trigger |
|---|---|---|---|
| Commands | commands/*.md |
Markdown + frontmatter | User: /command |
| Skills | skills/*/SKILL.md |
Markdown + frontmatter | Auto (context) |
| Hooks | hooks/hooks.json |
JSON | Events |
| MCP | .mcp.json |
JSON | Auto |
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?