plugin-creator

name	plugin-creator
description	Create automatically creates new AI assistant code plugins with proper structure, validation, and marketplace integration when user mentions creating a plugin, new plugin, or plugin from template. specific to AI assistant-code-plugins repository workflow. Use when generating or creating new content. Trigger with phrases like 'generate', 'create', or 'scaffold'.
allowed-tools	Write, Read, Grep, Bash(cmd:*)
version	2.19.0
author	Jeremy Longshore <[e-mail]>
license	MIT
tags	["example","workflow","plugin-creator"]
compatibility	Designed for Claude Code, also compatible with Codex and OpenClaw

Plugin Creator

Overview

Scaffolds new Claude Code plugins with proper directory structure, required files, marketplace catalog integration, and full validation. Supports all plugin types: command plugins, agent plugins, skill plugins, MCP server plugins, and hybrid combinations.

Prerequisites

• Write access to the plugins/ directory and .claude-plugin/marketplace.extended.json
• jq installed for JSON generation and validation
• pnpm run sync-marketplace available at the repository root
• ./scripts/validate-all-plugins.sh available for post-creation validation

Instructions

1. Gather requirements from the user request: plugin name (kebab-case), category (productivity, security, devops, testing, etc.), plugin type (commands, agents, skills, MCP, or combination), description, and keywords. Default author to the repository owner if unspecified (see ${CLAUDE_SKILL_DIR}/references/plugin-creation-process.md).

2. Create the plugin directory structure under plugins/[category]/[plugin-name]/:

   plugins/[category]/[plugin-name]/
   ├── .claude-plugin/
   │   └── plugin.json
   ├── README.md
   ├── LICENSE
   └── [commands/ | agents/ | skills/ | hooks/ | mcp/]
   

3. Generate .claude-plugin/plugin.json using the template from ${CLAUDE_SKILL_DIR}/references/file-templates.md. Populate all required fields: name, version (default 1.0.0), description, author (name and email), repository, license (default MIT), and keywords (minimum 2).

4. Generate README.md with installation instructions, usage examples, a description section, and contributor information.

5. Create a LICENSE file with MIT license text (or the specified license).

6. Generate component files based on the plugin type:

   • Commands: create commands/[command-name].md with proper YAML frontmatter (name, description, ).