plugins-scaffolding

Create Claude Code plugins with plugin.json manifests and component structure.

34|3|Updated Oct 17, 2025
One-click install
npx skills add https://github.com/charlesjones-dev/claude-code-plugins-dev --skill plugins-scaffolding
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plugins-scaffolding
Source: https://github.com/charlesjones-dev/claude-code-plugins-dev/tree/main/plugins/ai-plugins/skills/plugins-scaffolding
Command: npx skills add https://github.com/charlesjones-dev/claude-code-plugins-dev --skill plugins-scaffolding

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill guides developers through creating Claude Code plugins with proper structure, manifests, and components. It simplifies the extension of Claude's capabilities, enabling custom automation and community sharing without needing to master complex internal APIs.

Core Features & Use Cases

  • Plugin Architecture Guidance: Explains the structure of plugins, commands, agents, skills, hooks, and MCP servers.
  • Manifest Creation: Provides specifications for plugin.json and marketplace.json metadata, ensuring proper configuration.
  • Component Development: Guides the creation of all plugin components with best practices and examples.
  • Distribution & Versioning: Advises on semantic versioning and marketplace distribution for easy sharing and updates.
  • Use Case: Create a new Claude Code plugin from scratch, including its directory structure, plugin.json manifest, and an example command, ensuring it follows best practices for distribution and functionality.

Quick Start

Use the plugins-scaffolding skill to create a new Claude Code plugin named 'my-first-plugin' with a basic command.

Frequently Asked Questions about plugins-scaffolding

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a Claude Code plugin from scratch?

Create a plugin by setting up a root directory with a `.claude-plugin/plugin.json` manifest file. The manifest must include version, description, author, homepage, repository, license, and keywords fields. Follow kebab-case naming conventions and define your plugin's commands, agents, skills, hooks, or MCP servers within the manifest structure.

What structure and metadata does a plugin.json manifest require?

A plugin.json manifest must contain version, description, author, homepage, repository, license, and keywords fields at minimum. It defines your plugin's components—commands, agents, skills, hooks, and MCP servers—and can include optional custom paths for advanced layouts. Proper metadata ensures compatibility with the Claude Code marketplace.

Can I distribute my Claude Code plugin to the marketplace?

Yes, Claude Code plugins can be distributed through the marketplace using semantic versioning. The scaffolding guidance covers marketplace.json metadata specifications and distribution best practices, enabling community sharing and streamlined updates of your custom extensions.

What are the best practices for organizing plugin commands, agents, and skills?

Organize plugin components—commands, agents, skills, hooks, and MCP servers—within your manifest using kebab-case naming. Follow the defined architectural structure with a mandatory root plugin directory and `.claude-plugin/plugin.json` configuration to ensure proper functionality and marketplace compliance.

Do I need prior experience with Claude's internal APIs to build a plugin?

No, the scaffolding guidance simplifies plugin development without requiring mastery of complex internal APIs. It provides all required artifacts, conventions, and component specifications, making it accessible for developers new to Claude Code extension development.

How does semantic versioning apply to plugin updates and releases?

Semantic versioning structures plugin version numbers to communicate release changes and compatibility. The scaffolding guidance advises on applying versioning conventions for marketplace distribution, enabling clear communication of updates and maintaining user trust through predictable release cycles.