create-claude-plugin

Create bundled Claude Code plugins with marketplace.json and SKILL.md files.

Updated Mar 1, 2026
One-click install
npx skills add https://github.com/andy-austin/quipu --skill create-claude-plugin-andy-austin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-claude-plugin
Source: https://github.com/andy-austin/quipu/tree/main/.claude/skills/create-claude-plugin
Command: npx skills add https://github.com/andy-austin/quipu --skill create-claude-plugin-andy-austin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This guide reduces the friction of packaging multiple Claude Code extensions by standardizing plugin structure, marketplace metadata, and installation steps so teams can share and publish cohesive capabilities without broken paths or missing frontmatter.

Core Features & Use Cases

  • Plugin scaffolding: canonical directory layouts, required .claude-plugin/marketplace.json, and SKILL.md conventions for each skill.
  • Component integration: instructions for bundling skills, agents, commands, hooks, and MCP servers and referencing them correctly in marketplace.json.
  • Testing, versioning, and distribution: local testing, semantic versioning, Git/GitHub release workflows, and private or public marketplace publication.
  • Use Case: package a document-processing suite with multiple SKILL.md skills, testing scripts, and MCP server configs into a single plugin for team distribution and marketplace releases.

Quick Start

Create a plugin directory with a .claude-plugin/marketplace.json and properly structured skills, then install the marketplace locally to verify the plugin loads.

Frequently Asked Questions about create-claude-plugin

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

FAQPage Schema
How do I bundle Claude Code skills and MCP servers into a single distributable plugin?

To bundle Claude Code extensions, create a plugin directory with a .claude-plugin/marketplace.json file, add SKILL.md frontmatter for each skill, and reference all agents, commands, hooks, and MCP server configs using accurate relative paths.

What is the required directory structure for publishing a Claude Code plugin to a marketplace?

A Claude Code plugin requires a canonical directory layout featuring a .claude-plugin/marketplace.json file for metadata, individual SKILL.md files with proper frontmatter for each skill, and optional scripts or MCP configuration files referenced via relative paths.

How do I test a Claude Code plugin locally before publishing it to a marketplace?

You can test a Claude Code plugin locally by installing the marketplace from your local directory to verify that the plugin loads correctly, ensuring all component paths resolve and SKILL.md frontmatter is valid before release.

Can I distribute Claude Code plugins privately to my team without a public marketplace listing?

Yes, Claude Code plugins can be distributed privately for team sharing. You package the skills, agents, and MCP servers together, then share the plugin directory or use a private marketplace publication workflow.

How do versioned releases work for Claude Code plugins distributed via GitHub?

Versioned releases for Claude Code plugins use semantic versioning combined with Git and GitHub release workflows. You update the version in your marketplace.json and tag releases to manage plugin updates.

Why are my Claude Code plugin components not loading after installation?

Claude Code plugin components fail to load when the .claude-plugin/marketplace.json contains inaccurate relative paths or when individual SKILL.md files are missing required frontmatter fields.