How do I test my custom plugin locally?

You can test your plugin by launching Claude with the --plugin-dir flag followed by the path to your plugin directory, which enables immediate debugging of your components.

Where should I place my plugin component directories?

All component directories, such as /commands, /agents, and /skills, must be placed at the plugin root level rather than inside the .claude-plugin folder.

Can I integrate external tools using MCP?

Yes, this skill provides the schema and patterns for .mcp.json files, allowing you to connect external Model Context Protocol servers to your custom plugins.

What is a Claude Code plugin?

A Claude Code plugin is a specialized package containing metadata, commands, agents, and skills that extend Claude's functionality for specific development tasks or domains.

How do I distribute my finished plugin to my team?

Plugins can be distributed via GitHub repositories or by creating a marketplace.json file that lists your plugins, allowing others to install them using the /plugin marketplace add command.

Claude Code Plugin Builder

Name: Claude Code Plugin Builder
Author: zellycloud

byzellycloud

Developer Tools

Streamlines the creation, configuration, and distribution of Claude Code plugins using standardized architectural patterns and best practices.

About

The moai-plugin-builder skill provides a comprehensive development framework for extending Claude Code's core capabilities. It guides developers through the complex requirements of plugin architecture, ensuring that manifests, slash commands, autonomous agents, and domain-specific skills are correctly structured. By providing templates for Model Context Protocol (MCP) and Language Server Protocol (LSP) integrations, as well as advanced hook configurations, this skill enables the rapid development of production-ready tools that integrate seamlessly with the Claude CLI ecosystem.

Key Features

Event-driven hook implementation for tool and session lifecycles
Detailed configuration for MCP and LSP server integrations
Automated plugin.json manifest generation and validation patterns
Custom marketplace creation and plugin distribution workflows
0 GitHub stars
Standardized directory structures for commands, agents, and skills

Use Cases

Architecting enterprise-grade plugins with complex multi-agent workflows
Setting up private organizational marketplaces for internal developer tools
Migrating standalone configurations into portable, sharable plugin formats

About

Key Features

Event-driven hook implementation for tool and session lifecycles
Detailed configuration for MCP and LSP server integrations
Automated plugin.json manifest generation and validation patterns
Custom marketplace creation and plugin distribution workflows
0 GitHub stars
Standardized directory structures for commands, agents, and skills

Use Cases

Architecting enterprise-grade plugins with complex multi-agent workflows
Setting up private organizational marketplaces for internal developer tools
Migrating standalone configurations into portable, sharable plugin formats