create-claude-plugin
codyhxyz/create-claude-plugin
Automatiza a publicação de plugins Claude do rascunho ao marketplace
Ver no GitHubSkill que automatiza todo o ciclo de vida de publicação de plugins Claude, desde validação local até submissão no marketplace official. Valida o plugin, executa testes, faz check de portabilidade Cowork, cria repositório GitHub e preenche formulário de submissão automaticamente.
Instalação
npx convez-ai codyhxyz/create-claude-plugin1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.
Métricas
Casos de uso
- Publicar skills e plugins no marketplace oficial Claude
- Validar plugins antes de submissão com duas camadas de checagem
- Testar portabilidade automática via Cowork desktop app
- Gerar repositório GitHub configurado com templates e tópicos
Veredito

Ferramenta robusta que resolve um problema real: democratizar a publicação de plugins Claude. A automação em duas camadas (saúde genérica + validação marketplace) e o teste Cowork via Computer Use a diferenciam de scripts simples. Essencial para quem quer escalar a adoção de plugins no ecossistema.
README
A tradução para o português deste README ainda está na fila.
create-claude-plugin
A Claude plugin that ships Claude plugins. Yes, it's recursive. Someone had to do it.
Other plugin guides explain what plugins are. This one walks you from "I have an idea" to "it's live in claude-plugins-official" without leaving Claude Code. It validates, runs the local test loop, does the Cowork portability check, pushes to GitHub, and fills out the submission form. You handle the judgment (naming, scoping, what it should actually say). The skill handles the plumbing.
Before and after
Before: "I have a skill in ~/.claude/ and no idea how to share it."
After: plugin passes claude plugin validate, repo is live on GitHub, /plugin marketplace add owner/repo works in a fresh session, and the submission form is open in your browser with every field already on your clipboard. About 20 minutes.
What you get
- A validated plugin that passes
claude plugin validateand works in-session viaclaude --plugin-dir. - A live GitHub repo with topics, a verified install flow, and
gh repo createalready done. - A filled-in submission. Clipboard pre-loaded with every field the form asks for, browser opened to
claude.ai/settings/plugins/submit, fields grouped by form page so you can paste and tab through. - An automated Cowork smoke test. Most toolkits stop at
claude plugin validate. This one drives the Cowork desktop app for you: Claude Code's Computer Use installs your plugin, runs your test prompt, and screenshots errors. No manual clicking. (macOS plus Pro/Max only; there's a manual fallback otherwise.) - A generic repo-health check (linting, type checking, tests, pre-commit, security, docs) via
scripts/readiness.sh— runs as a Phase 4.5 advisory scoring 20 criteria across 6 categories, withscripts/readiness-fix.shavailable to scaffold missing configs (prettier/eslint/ruff/pre-commit/jest/pytest/.env.example/issue templates).
Two-layer validation
This plugin ships two orthogonal checks. Layer 1 — generic repo health (scripts/readiness.sh) scores any codebase on hygiene basics: linter config, formatter, type checking, tests, coverage, pre-commit hooks, .gitignore, CODEOWNERS, issue/PR templates. Non-blocking; advisory. Layer 2 — marketplace-specific (scripts/check-submission.sh) validates the 17 rules Anthropic's submission form enforces: manifest schema, naming, marketplace.json integrity, Cowork portability, marketing artifacts. Blocking. Run them together: readiness catches hygiene gaps; check-submission catches submission blockers. check-submission.sh also reports the readiness score as an informational line.
Examples
Example 1. "I have a code-review agent in .claude/agents/ and I want to share it." The skill converts the agent file into a plugin layout, scaffolds .claude-plugin/plugin.json and marketplace.json, writes the README with install instructions, runs claude plugin validate, pushes to GitHub, and prints every submission field ready to paste.
Example 2. "Build me a plugin from scratch that bundles a skill and a PostToolUse hook." The skill picks the layout (skill at skills/<name>/SKILL.md, hook at hooks/hooks.json), inserts ${CLAUDE_PLUGIN_ROOT} substitutions so the hook survives install, runs the local claude --plugin-dir test loop, then walks you through hosting and submission.
Install
Claude Code (recommended)
/plugin marketplace add codyhxyz/codyhxyz-plugins && /plugin install create-claude-plugin@codyhxyz-plugins
The plugin@marketplace format is <plugin-name>@<marketplace-name>. codyhxyz-plugins is my meta-marketplace — one add, every plugin I ship.
See the full codyhxyz-plugins marketplace for my other plugins.
Manual install
mkdir -p ~/.claude/skills/create-claude-plugin
git clone https://github.com/codyhxyz/create-claude-plugin /tmp/ccp
cp -r /tmp/ccp/skills/create-claude-plugin/* ~/.claude/skills/create-claude-plugin/
Usage
Ask Claude Code to make a plugin:
"Help me make a Claude Code plugin out of this skill I have in my
.claude/dir."
"I want to publish my code-review agent to the official Claude marketplace."
"Scaffold a new Claude plugin with a skill and a hook."
The skill activates on its own and walks through seven phases: decide, scaffold, build, test, document, host, submit.
Pre-flighting an existing plugin
If you already have a plugin and want to check whether it's submission-ready:
./scripts/check-submission.sh /path/to/your/plugin
What it does:
- Validates
plugin.jsonhas every field the submission form wants. - Checks the name is kebab-case, not reserved, not impersonating something else, and not already taken in
claude-plugins-official. - Confirms your README has an
## Examplessection. - Runs
claude plugin validateif you have it installed. - Copies every paste-ready field to your clipboard and opens the submission URL.
Why this exists
Making a Claude plugin is maybe 20% mechanics and 80% judgment plus distribution. The CLI handles the mechanics. The existing docs explain what plugins are. Nothing closed the gap between "I have an idea" and "it's listed at claude-plugins-official, installable by anyone running /plugin install."
So: scripts where determinism matters, model where judgment matters. The script catches missing fields. The skill helps you figure out what those fields should say. Same shape as create-chrome-extension.
Related
- create-chrome-extension — same idea, Chrome Web Store instead of the Claude marketplace.
- create-claude-plugin (you're here) —
~/.claude/skill toclaude-plugins-official.
Repository layout
create-claude-plugin/
├── .claude-plugin/
│ ├── plugin.json
│ └── marketplace.json
├── skills/
│ └── create-claude-plugin/
│ ├── SKILL.md # main orchestration skill
│ ├── reference/ # load on demand
│ │ ├── plugin-manifest.md
│ │ ├── marketplace-manifest.md
│ │ ├── component-types.md
│ │ ├── hosting-options.md
│ │ └── submission-form.md
│ ├── templates/ # copy + fill in
│ │ ├── plugin/ # plugin.json, marketplace.json, README, LICENSE, CHANGELOG, .gitignore
│ │ ├── skill/SKILL.md
│ │ ├── agent/agent.md
│ │ └── hook/hooks.json
│ └── checklists/
│ ├── pre-publish.md
│ └── submission-ready.md
├── scripts/
│ └── check-submission.sh
├── ARCHITECTURE.md
├── README.md
├── LICENSE
├── CHANGELOG.md
└── .gitignore
Contributing
Issues and PRs welcome. Stale doc links in the skill count as bugs.
License
MIT © 2026 Cody Hergenroeder
Part of codyhxyz-plugins 🍋 — my registry of Claude Code plugins.