Create and manage Claude Code plugins with proper structure, manifests, and marketplace integration. Use when creating plugins for a marketplace, adding plugin components (commands, agents, hooks), bumping plugin versions, or working with plugin.json/marketplace.json manifests.
95
93%
Does it follow best practices?
Impact
95%
1.41xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Plugin creation and marketplace registration
Script-based creation
100%
100%
Correct script args
50%
100%
Plugin manifest location
0%
100%
Manifest name field
100%
100%
Manifest version field
100%
100%
Manifest author field
100%
100%
Marketplace entry added
100%
100%
Marketplace source path
0%
100%
Marketplace category
100%
100%
Components at plugin root
0%
40%
Kebab-case marketplace name
100%
100%
Marketplace owner field
0%
100%
Version bumping and semantic versioning
Script usage
100%
100%
Script arguments
75%
100%
Breaking change → major
100%
100%
New feature → minor
100%
100%
Bug fix/docs → patch
100%
100%
Both locations updated
100%
100%
Conventional commit: feat
100%
100%
Conventional commit: fix
0%
0%
Conventional commit: breaking
0%
100%
Version format
100%
100%
Plugin component structure and naming
Namespaced command location
100%
100%
Command invocation format
0%
100%
Simple command location
100%
100%
Hooks file location
0%
100%
MCP file location
0%
100%
CLAUDE_PLUGIN_ROOT in hooks/MCP
0%
100%
Relative paths with ./
100%
100%
Components NOT in .claude-plugin
60%
100%
Skill SKILL.md file
100%
100%
Hooks events
100%
100%
Conventional commit type
100%
100%
3027f20
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.