create-plugin

Scaffold a Claude Code and Codex plugin repository with plugin.json and marketplace.json files.

104|19|Updated Apr 14, 2026
One-click install
npx skills add https://github.com/alexsmedile/hormozi-skills --skill create-plugin-alexsmedile
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-plugin
Source: https://github.com/alexsmedile/hormozi-skills/tree/main/skills/create-plugin
Command: npx skills add https://github.com/alexsmedile/hormozi-skills --skill create-plugin-alexsmedile

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Turning a repo of skills into a working Claude Code and Codex plugin is tedious and easy to misconfigure, so this Skill generates a complete, marketplace-ready plugin scaffold for you.

Core Features & Use Cases

  • Plugin scaffolding for both platforms: Creates the required .claude-plugin/ and .codex-plugin/ plugin manifests in one go.
  • Marketplace support: Writes marketplace metadata files so your plugin can be discovered and installed via the marketplace flow.
  • Correct repo structure enforcement: Ensures skills and agents remain at repo root so autodiscovery works properly without schema validation issues.

Use it when you want to publish a GitHub-based plugin, set up marketplace metadata, and package existing skills/ and agents/ into a unified plugin experience for Claude Code and Codex.

Quick Start

Ask the skill to create a plugin scaffold by telling it your repo name, GitHub username, one-sentence description, author name, what the plugin contains, and your license.

Frequently Asked Questions about create-plugin

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

FAQPage Schema
How do I scaffold a Claude Code and Codex plugin repository for GitHub?

Scaffolding a Claude Code and Codex plugin repository requires generating the necessary `.claude-plugin/` and `.codex-plugin/` manifests. This process creates a complete, marketplace-ready GitHub repo structure with correct autodiscovery and schema constraints.

What files are needed to publish a Claude Code plugin to the marketplace?

Publishing a Claude Code plugin to the marketplace requires `plugin.json` and `marketplace.json` files. These metadata files ensure your plugin can be correctly discovered, installed via the marketplace flow, and validated against required schema constraints.

How do I package existing skills and agents into a unified plugin?

Packaging existing skills and agents into a unified plugin requires keeping them at the repository root so autodiscovery works properly. Scaffolding tools enforce this correct repo structure while generating the necessary plugin manifests.

Can I configure MCP servers and hooks when creating a plugin repo?

Configuring MCP servers and hooks is supported when creating a plugin repo. During the scaffolding process, you can select optional skills, agents, hooks, and MCP server configurations to include in your generated plugin manifests.

Why does my Claude Code plugin fail schema validation during marketplace installation?

Claude Code plugin schema validation fails during marketplace installation when repository structure is misconfigured. If skills and agents are not placed at the repo root, autodiscovery breaks, preventing correct operation and marketplace metadata processing.

What information do I need to provide to scaffold a marketplace-ready plugin?

Scaffolding a marketplace-ready plugin requires providing your repo name, GitHub username, a one-sentence description, author name, the plugin contents, and your chosen license. This information populates the generated manifest and marketplace metadata files.