Plugin Developer Toolkit
Install It
/plugin install plugin-dev@claude-plugins-official
That’s it. You now have 7 new skills available under the /plugin-dev: namespace.
The 7 Skills
Hook Development
All 9 hook event types: PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification.
Use: /plugin-dev:hook-development
MCP Server Integration
Connect external services via Model Context Protocol — stdio, SSE, HTTP, WebSocket protocols all covered.
Use: /plugin-dev:mcp-integration
Plugin Structure & Settings
Directory layout, plugin.json manifest, settings configuration, .local.md patterns for user-configurable plugins.
Use: /plugin-dev:plugin-structure
Slash Command Creation
Custom /commands, YAML frontmatter fields, dynamic arguments, bash execution, interactive user prompts.
Use: /plugin-dev:command-development
Agent Development
Creating autonomous subagents: system prompts, tools configuration, triggering conditions, isolation modes.
Use: /plugin-dev:agent-development
Skill Authoring
Writing effective SKILL.md files: frontmatter options, context modes, model selection, progressive disclosure patterns.
Use: /plugin-dev:skill-development
Plugin Validation
Validate your plugin before publishing: structure checks, frontmatter validation, hook testing, marketplace readiness.
Use: /plugin-dev:plugin-validator
Guided Creation: 8 Phases
The fastest way to build a new plugin is the guided workflow:
> /plugin-dev:create-plugin
This launches an 8-phase creation process:
-
Discovery
Claude interviews you about the workflow you want to automate. What do you do manually today? What are the inputs and outputs?
-
Planning
Claude designs the plugin architecture: which components you need (skills, agents, hooks, MCP), how they connect.
-
Design
Claude drafts the skill/agent system prompts and hook logic. You review and adjust before any files are created.
-
Implementation
Claude generates all plugin files: directory structure,
plugin.json,SKILL.mdfiles, agent definitions, hook config. -
Validation
Claude validates the structure against plugin spec — catches missing fields, incorrect frontmatter, broken references.
-
Testing
Claude generates test scenarios and walks you through local testing with
claude --plugin-dir ./your-plugin. -
Documentation
Claude generates a README with install instructions, usage guide, and contribution notes.
-
Publishing
Claude prepares the plugin for marketplace submission or team distribution.
Ask Questions Naturally
You don’t have to use the guided flow. Just ask questions and the right skill auto-loads:
> How do I create a PreToolUse hook that blocks edits to production files?
Claude loads the hook-development skill and gives you a working implementation.
> What's the difference between context: main and context: fork in a SKILL.md?
Claude loads the skill-development skill and explains the fork isolation mode.
> I want my plugin to connect to a Jira instance. What's the best approach?
Claude loads the MCP integration skill and walks you through the Jira MCP server setup.
Use It to Build RHDP Skills
The plugin-dev toolkit is how you’d build new RHDP marketplace skills. Here’s the connection:
/plugin-dev:skill-development to generate the SKILL.md. The toolkit knows the RHDP SKILL.md format.
/plugin-dev:agent-development and /plugin-dev:hook-development to generate the files.
Validate Before Publishing
Before submitting a skill to the RHDP marketplace or sharing with your team:
> /plugin-dev:plugin-validator
This checks:
plugin.jsonhas all required fields (name, version, description, author)- All referenced files exist
- SKILL.md frontmatter is valid
- Agent definitions have required sections (Role, Instructions)
- Hooks use correct event names and exit codes
- No secrets or credentials in any files
Local Testing Workflow
# Test your plugin locally (without installing to marketplace)
claude --plugin-dir ./my-plugin
# Test multiple plugins together
claude --plugin-dir ./my-plugin --plugin-dir ./another-plugin
# Reload without restarting
> /reload-plugins
When a local --plugin-dir plugin has the same name as an installed marketplace plugin, the local copy takes precedence for that session — useful for testing updates.