plugin-creator

name	plugin-creator
description	Scaffold, validate, test, and ship a production-grade Claude Code plugin + marketplace — especially the pattern where the plugin's ONLY component is an MCP server that surfaces a registry of skills and agents on demand (so they never clog the / menu or the always-on context). Use this WHENEVER the user wants to create, build, scaffold, package, or distribute a Claude Code plugin, plugin marketplace, or MCP-server plugin; expose project-specific skills/agents/tools to a coding agent; turn skills or agents into an installable package; or "make a plugin for this project" — even if they don't say "MCP" or "marketplace" explicitly. Ships a scaffolder, a smoke-tester, a validator, reference docs, and Node + Python server templates so any agent can do this repeatably and correctly.
license	MIT
compatibility	Requires Python 3.8+ for the bundled scripts (standard library only). Generated Node servers need Node.js; generated Python servers need Python 3.8+. The `claude` CLI is optional — used for official `claude plugin validate` and install round-trips. Linux, macOS, and WSL.
metadata	{"author":"github.com/kryptobaseddev","version":"1.0.0","last_updated":"2026-06-08 12:20:29","category":"skill-development"}
allowed-tools	Bash Read Write Edit Glob Grep

plugin-creator

Create a robust, installable Claude Code plugin + marketplace for the project you're invoked in — and do it the right way: a plugin whose only component is an MCP server that exposes a registry of skills/agents on demand, so the catalog can be huge while the always-on context cost stays ~0 and nothing lands in the user's / menu.

This skill bundles everything needed to do it repeatably: a scaffolder, a smoke-tester, a validator, Node + Python server templates, and four reference docs. Use the scripts — don't hand-write boilerplate or reinvent an MCP client; that's what the bundled tooling is for.

${CLAUDE_SKILL_DIR} below means this skill's own directory (where this SKILL.md lives). Run the scripts from there.

Not the right fit? Redirect, don't force it

This skill scaffolds a distributable Claude Code plugin. If the real request is something adjacent, say so plainly and point the user the right way instead of scaffolding a plugin they didn't ask for:

• One standalone skill, not a package ("turn this into a Claude Code skill", no distribution) → that's skill-creator, not this. Don't create a marketplace.
• A general MCP client / application (a CLI or app that connects out to MCP servers) → that's ordinary application code; help them build it directly. This skill builds the server side packaged as a plugin, not clients.
• Just a slash command or a hook, no catalog → a plain plugin command/hook is simpler; see references/recipes.md "Pick a shape".

When it is a plugin, continue below.

The idea in one table

A plugin can ship commands, skills, agents, hooks, and MCP servers. Native skills and agents inject their name+description into every session's system prompt (cost scales with count) and add / menu entries. MCP tools are deferred (name only) and MCP resources load their body only when read. So:

Ship capabilities as…	Always-on cost	/ menu noise	Scales with count
Native skills / agents	name+desc each	yes	badly