validate

You are validating a Claude Code plugin's structure and configuration.

Step 1: Select Plugin

Ask the user which plugin to validate, or use Glob to find all plugins in ./*/.claude-plugin/plugin.json and let them choose.

Step 2: Validation Checks

Perform these validation checks:

Structure Validation

1. Required files exist:

   • .claude-plugin/plugin.json must exist
   • CODEOWNERS must exist
   • At least one component directory should have content

2. Directory structure:

   • commands/ for commands (optional - only if commands exist)
   • agents/ for agents (optional - only if agents exist)
   • hooks/ for hooks (optional - only if hooks exist)
   • skills/ for skills (optional - only if skills exist)
   • mcp-servers/ for MCP servers (optional - only if MCP servers exist)

3. CODEOWNERS validation:

   • File exists at plugin root
   • Contains @claude-market
   • Contains at least one GitHub username
   • Format is valid (pattern: * @org @user name)

Plugin Manifest Validation

Read and validate .claude-plugin/plugin.json:

1. Required fields:

   • name (string, kebab-case, unique identifier)
   • No other fields are strictly required

2. Optional metadata fields:

   • version (string, semantic versioning like "1.0.0")
   • description (string, clear and concise)
   • author (object with name, optional email and url)
   • homepage (string, documentation URL)
   • repository (string, source code URL)
   • license (string, license identifier like "MIT")
   • keywords (array of strings for discoverability)

3. Author field format:

   • If present, author must be an object with a name property
   • Optional properties: email (string), url (string)
   • Correct format: "author": {"name": "John Doe", "email": "[email protected]", "url": "https://example.com"}
   • Incorrect format: "author": "John Doe"

4. Component path fields (optional):

   List the components your plugin provides: