claude-code-plugins: Command for Claude Code

You are tasked with converting a Gemini extension to Claude Code plugin format. Follow these steps precisely:

Input

The user will provide a path to a Gemini extension directory containing gemini-extension.json.

Path to convert: $ARGUMENTS

Conversion Steps

1. Validate Input

• Check if the provided path exists and contains gemini-extension.json
• If not found, ask the user for the correct path

2. Read Gemini Extension Configuration

• Read the gemini-extension.json file
• Extract: name, description, version, mcpServers configuration

3. Create Plugin Directory Structure

• Create .claude-plugin directory in the extension path
• Create commands directory if it doesn't exist (it should already exist for extensions with commands)

4. Generate plugin.json

Create .claude-plugin/plugin.json with the following structure:

{
  "name": "<name from gemini-extension.json>",
  "version": "<version from gemini-extension.json>",
  "description": "<description from gemini-extension.json>",
  "commands": ["./commands"],
  "mcpServers": <copy mcpServers object from gemini-extension.json>
}

5. Convert Command Files (TOML to Markdown)

For each .toml file in the commands/ directory:

• Read the TOML file
• Extract description and prompt fields
• Create a new .md file with the same base name
• Format as:

  ---
  description: <description from TOML>
  ---
  
  <prompt from TOML with {{args}} replaced by $ARGUMENTS>
  

• IMPORTANT: Replace all instances of {{args}} with $ARGUMENTS in the prompt
• Keep the original TOML file (don't delete it) for reference

6. Update Marketplace Configuration

• Read .claude-plugin/marketplace.json at the repository root
• Add a new entry to the plugins array if not already present:

  {
    "name": "<plugin name>",
    "description": "<plugin description>",
    "source": {
      "source": "github",
      "repo": "pleaseai/<plugin-name>"
    }
  }
  

• If the plugin already exists in marketplace.json, update its description