Unofficial plugin-dev plugin marketplace. Originally created by Daisy Hollman at Anthropic, now maintained by Steve Nims.
npx claudepluginhub sjnims/plugin-devComprehensive toolkit for developing Claude Code plugins. Includes 10 expert skills covering hooks, MCP integration, LSP servers, commands, agents, marketplaces, and best practices, plus a guide skill for navigation. AI-assisted plugin creation and validation.
Claude Code plugins for the Slidev presentation framework
Bundled plugins for actuating and debugging the Chrome browser.
Claude Code marketplace entries for the plugin-safe Antigravity Awesome Skills library and its compatible editorial bundles.
A comprehensive toolkit for developing Claude Code plugins with expert guidance on hooks, MCP integration, plugin structure, and marketplace publishing.
The plugin-dev toolkit provides 10 specialized skills, 3 validation agents, and 4 slash commands to help you build high-quality Claude Code plugins:
Each component follows progressive disclosure: lean core documentation with detailed references and working examples available when needed.
The plugin includes utility scripts for validation and testing. These require:
| Tool | Version | Purpose |
|---|---|---|
| bash | 3.2+ | Shell scripting (macOS default works) |
| jq | 1.6+ | JSON parsing and validation |
| grep | - | Pattern matching (with -E support) |
| sed | - | Stream editing (GNU or BSD) |
Check your environment:
bash --version | head -1
jq --version
grep --version 2>&1 | head -1
Note:
jqmay need to be installed. macOS:brew install jq, Linux:apt install jq
Add this marketplace and install the plugin:
/plugin marketplace add sjnims/plugin-dev
/plugin install plugin-dev@sjnims/plugin-dev
Or for development, use directly:
claude --plugin-dir /path/to/plugin-dev/plugins/plugin-dev
New to plugin development? Start with the guided entry point:
/plugin-dev:start
This will help you choose between creating a plugin (most users) or a marketplace (for distributing multiple plugins).
You can also learn progressively by asking questions. Skills load automatically:
Plan your plugin structure:
Add MCP integration (if needed):
Implement hooks (if needed):
Skills load automatically when you ask relevant questions. Each skill includes core documentation, reference guides, working examples, and utility scripts.