plugin-creator

Generate structured Claude plugin scaffolds with templates and packaging scripts.

10|5|Updated Jan 2, 2026
One-click install
npx skills add https://github.com/ddunnock/claude-plugins --skill plugin-creator-ddunnock
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plugin-creator
Source: https://github.com/ddunnock/claude-plugins/tree/main/skills/plugin-creator
Command: npx skills add https://github.com/ddunnock/claude-plugins --skill plugin-creator-ddunnock

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pyyaml, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill guides users through creating Claude plugins by providing templates, best-practice patterns, and tooling to streamline the authoring process for Skills and MCPs.

Core Features & Use Cases

  • Template-driven scaffolds for Skills (SKILL.md) and MCPs, including resources directories (scripts/, references/, assets/)
  • Ready-to-run scripts for initializing new plugins, packaging into distributable files, and validating structure
  • Clear guidance on naming, frontmatter standards, packaging workflows, and deployment preparations
  • Use Case: A developer wants to bootstrap a new Skill named "my-skill" in skills/ with proper metadata and packaging steps

Quick Start

Example: Create a new Skill

  • python scripts/init_skill.py my-new-skill --path skills/
  • Then package or validate as needed:
  • python scripts/package_skill.py skills/my-new-skill
  • python scripts/quick_validate.py skills/my-new-skill

Frequently Asked Questions about plugin-creator

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

FAQPage Schema
How do I create and package a Claude plugin or Skill from a prompt?

To create and package a Claude plugin, you can use template-driven scaffolds that generate structured directories like scripts/ and references/ alongside ready-to-run scripts for initializing, validating, and packaging your Skills.

What is the standard structure for a Claude Skill or MCP plugin?

The standard structure for a Claude plugin includes a SKILL.md file with frontmatter metadata, alongside organized resource directories such as scripts/, references/, and assets/ to maintain clear separation of code and supporting files.

Do I need Python and pyyaml to generate Claude plugin templates?

Yes, Python and the pyyaml dependency are required to run the initialization, validation, and packaging scripts that generate the Claude plugin scaffold and process frontmatter metadata.

How do I validate a Claude Skill structure before deployment?

You validate a Claude Skill structure by running a quick validation script against your plugin directory to ensure frontmatter standards, naming conventions, and required bundled resources are correctly integrated before deployment.

What's the best way to bootstrap a new Claude Skill with proper metadata?

The best way to bootstrap a new Claude Skill is using an initialization script that automatically applies frontmatter standards, creates the necessary resource directories, and prepares the packaging workflow.

Are there limitations to template-driven scaffolding for MCPs?

Template-driven scaffolding for MCPs focuses on structural generation, naming, and packaging validation, meaning it provides the foundational scaffold and metadata but does not write the custom server logic required for your specific MCP implementation.