creating-a-plugin

Scaffold Claude Code plugin blueprints with standard directory layouts and SKILL.md frontmatter.

5|1|Updated Jan 26, 2026
One-click install
npx skills add https://github.com/ed3dai/ed3d-plugins-testing --skill creating-a-plugin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: creating-a-plugin
Source: https://github.com/ed3dai/ed3d-plugins-testing/tree/main/plugins/ed3d-extending-claude/skills/creating-a-plugin
Command: npx skills add https://github.com/ed3dai/ed3d-plugins-testing --skill creating-a-plugin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill scaffolds a complete Claude Code plugin blueprint, ensuring consistent project structure, a SKILL.md entry point for each skill, and ready-to-publish component organization.

Core Features & Use Cases

  • Provides a standard directory layout including commands/, agents/, skills/, hooks/, and MCP servers.
  • Ensures SKILL.md frontmatter exists with a name and description, enabling auto-discovery and validation.
  • Helps teams bootstrap new plugins quickly across projects to maintain consistency.

Quick Start

Create a new plugin folder, add a .claude-plugin/plugin.json manifest, and place a SKILL.md under each skill directory following the template. Then populate optional directories (scripts/, references/, assets/) as needed.

Frequently Asked Questions about creating-a-plugin

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

FAQPage Schema
How do I scaffold a complete Claude Code plugin structure for new projects?▼

Scaffolding a Claude Code plugin requires generating a standard directory layout including commands/, agents/, skills/, hooks/, and a .claude-plugin/plugin.json manifest to ensure ready-to-publish component organization and consistent project structure.

What is the required directory layout for developing Claude Code agents and commands?▼

The standard directory layout for Claude Code plugins includes separate directories for commands/, agents/, skills/, hooks/, and MCP servers, alongside optional folders like scripts/, references/, and assets/ to organize components.

How does SKILL.md frontmatter enable auto-discovery for Claude Code plugins?▼

SKILL.md frontmatter enables auto-discovery by requiring a name and description field for each skill, allowing the Claude Code plugin structure to be validated and integrated consistently across multiple projects.

Can I use this scaffolding approach to enforce uniform plugin structures across multiple projects?▼

Yes, this scaffolding approach enforces uniform plugin structures across multiple projects by standardizing the directory layout and requiring a SKILL.md entry point with frontmatter for each skill, ensuring teams bootstrap consistently.

Do I need a plugin manifest to bootstrap a new Claude Code plugin?▼

Yes, you need a .claude-plugin/plugin.json manifest to bootstrap a new Claude Code plugin, which serves as the central configuration file alongside the standard directory layout and SKILL.md files.