cpv-create-plugin

name	cpv-create-plugin
description	Create Claude Code plugin or marketplace repos with full CI/CD. Use when scaffolding. Used via cpv-the-skills-menu.
user-invocable	false

Create Plugin / Marketplace

Overview

Scaffolds complete Claude Code plugin or marketplace repositories with standard files, CI/CD workflows, git hooks, and release pipeline.

Marketplace layout

CPV supports three layouts: A (hub-and-spoke), B (nested), C (marketplace-in-plugin, self-referential). Default to A for multi-plugin sets; suggest C when one repo should be both plugin and marketplace. See marketplace-layouts.md.

Prerequisites

• git, uv, gh CLI on PATH
• CPV plugin installed
• GitHub account (for publishing)

Instructions

1. Create a Plugin Repository:

   uv run "${CLAUDE_PLUGIN_ROOT}/scripts/generate_plugin_repo.py" <target-dir> \
     --name <plugin-name> --description "<description>" \
     --author "<author>" --author-email "<email>" \
     --github-owner <github-username> [--marketplace <name>]
   

2. Create a Marketplace Hub (HUBS ONLY — no plugin code inside):

   uv run "${CLAUDE_PLUGIN_ROOT}/scripts/generate_marketplace_repo.py" <target-dir> \
     --name <marketplace-name> --owner-name "<display-name>" \
     --description "<description>" --github-owner <github-username>
   

3. After generation:

   • Validate via launcher (alias plugin) — see references/launcher-invocation.md. Direct invocation refused.

     The one-liner · Why the launcher is mandatory · Direct invocation (development only)

   • Fix ALL issues (CRITICAL, MAJOR, MINOR, NIT) — only WARNINGs may remain
   • Init git: cd <target-dir> && git init && git add -A && git commit -m "Initial scaffold"
   • Create repo: gh repo create <owner>/<name> --public --source . --push
   • Configure hooks: git config core.hooksPath git-hooks

Copy this checklist and track your progress:

• Repository generated
• Validation passed
• All issues fixed
• Git initialized and committed
• GitHub repo created
• Hooks configured

4. Standardize existing repos:

   uv run "${CLAUDE_PLUGIN_ROOT}/scripts/standardize_plugin.py" <path> [--fix]
   uv run "${CLAUDE_PLUGIN_ROOT}/scripts/standardize_marketplace.py" <path> [--fix]
   

Output

• Complete plugin/marketplace directory with all standard files
• CI/CD workflows, pre-push hook, publish.py, cliff.toml
• README with badge markers and component tables

Error Handling

Error	Resolution
Target directory exists	Choose a different name or remove the existing directory
Missing required arguments	Provide all mandatory flags (--name, --github-owner)
Validation fails after generation	Run standardize --fix, then fix remaining issues manually
ModuleNotFoundError: yaml	Use uv run --with pyyaml python when outside CPV venv

Resources

• Examples

  Create plugin · Create marketplace

• Pipeline Rules

  Pre-Push Hook: The Quality Gate · Fix-All Mandate · Running CPV Scripts · Processing Validation Output · GitHub Secrets · CI Workflow Dependencies · Marketplace Notification · All Scripts Are Python · Binary Plugins · README Requirements · Pre-Publish Local Dry-Run · Post-Push CI Verification · Mega-Linter Configuration

• v2.1.80+ Plugin Features

  Monitor tool · userConfig (plugin.json) · channels (plugin.json) · CLAUDE_PLUGIN_OPTION_ env vars · Inline marketplace (settings.json) · managed-settings.d/ drop-in directory · Plugin skill name field (v2.1.98)

• Marketplace Layouts

  Overview · Layout A — Hub-and-Spoke (separate repos) · Layout B — Nested single-repo (monorepo) · Layout C — Marketplace-in-plugin (self-referential single repo) · How Claude Code updates plugins in each layout · When to choose which · Rich metadata fields (author, homepage, license, category) · Why CPV does not use git-subdir · Encountering a non-CPV marketplace · Refactoring between layouts · Agent behavior summary

• Dev-stripping

  Why this exists · When NOT to use · Testing approach

• Parallel scanning (v2.103.0+) — newly-scaffolded plugins inherit the ~11.6× CPV speedup for free via uvx --from git+... remote-mode in their ci.yml / release.yml / publish.py (no template re-scaffold needed when CPV ships a new parallelism win)

  Table of contents · Performance summary · Environment knobs (disable selectively for debugging) · Scaffolded plugins (created via cpv-create-plugin / cpv-setup-plugin-repo) · Batch commands (cpv-batch-*) · Remote validation (cpv remote-mode + scaffolded publish.py) · When to disable parallelism · See also

MCP Server Bundling

Place bundled MCP executables in servers/, reference as ${CLAUDE_PLUGIN_ROOT}/servers/<name>. Unique names per server. See skills/cpv-fix-validation/references/empirical-loading-bugs.md for footguns.

Token Optimization

Use mcp__plugin_llm-externalizer_llm-externalizer__* for bounded work.

Examples

See examples.md.

Create plugin · Create marketplace

Dev-stripping (TRDD-793ac32a)

generate_plugin_repo.py --strip-dev (default) emits a cpv.strip block. See dev-stripping.md.

Why this exists · When NOT to use · Testing approach