Plugin Builder

Plugin Builder

Create a new Claude Code plugin in ~/my-claude-marketplace.

Step 1 — Ensure marketplace exists

Check if ~/my-claude-marketplace exists:

ls ~/my-claude-marketplace

If not found, clone it:

git clone https://github.com/lynconEBB/my-claude-marketplace ~/my-claude-marketplace

Step 2 — Gather requirements

Ask the user for:

• Plugin name (kebab-case, e.g. my-plugin) — if not in $ARGUMENTS
• Description — brief sentence of what it does
• Components needed — which of the following apply:
  • Skills (slash commands)
  • Agents (subagents)
  • Hooks (event handlers)
  • MCP servers
  • LSP servers

Only create files for selected components. Skip the rest.

Step 3 — Create plugin directory

Use the template at ${CLAUDE_SKILL_DIR}/template/ as reference.

Create ~/my-claude-marketplace/plugins/<plugin-name>/ with this minimal structure (always required):

<plugin-name>/
└── .claude-plugin/
    └── plugin.json

Populate .claude-plugin/plugin.json:

{
  "name": "<plugin-name>",
  "description": "<description>",
  "version": "1.0.0",
  "author": {
    "name": "Lyncon Baez",
    "email": "lynconlyn@gmail.com"
  }
}

Step 4 — Add selected components

Skills

Create skills/<skill-name>/SKILL.md for each skill. Use this structure:

---
name: <skill-name>
description: <what it does and when Claude should use it>
disable-model-invocation: true
---

# Skill instructions here

Set disable-model-invocation: true for task-oriented skills (deploy, commit, etc.). Omit it for knowledge/reference skills Claude should apply automatically.

Add the skills path to plugin.json only if using a non-default location.

Agents

Create agents/<agent-name>.md:

---
name: <agent-name>
description: <what this agent specializes in and when to invoke it>
---

Agent system prompt here.

Hooks

Create hooks/hooks.json:

{
  "hooks": {
    "PostToolUse": [
      {
        "matcher": "Write|Edit",
        "hooks": [
          {
            "type": "command",
            "command": "${CLAUDE_PLUGIN_ROOT}/scripts/your-script.sh"
          }
        ]
      }
    ]
  }
}

Make hook scripts executable: chmod +x scripts/your-script.sh

Always use ${CLAUDE_PLUGIN_ROOT} for paths in hooks and MCP configs.

MCP servers

Create .mcp.json:

{
  "mcpServers": {
    "<server-name>": {
      "command": "${CLAUDE_PLUGIN_ROOT}/servers/<binary>",
      "args": []
    }
  }
}

LSP servers

Create .lsp.json:

{
  "<language>": {
    "command": "<lsp-binary>",
    "args": [],
    "extensionToLanguage": {
      ".<ext>": "<language>"
    }
  }
}

Step 5 — Register in marketplace

Read ~/my-claude-marketplace/.claude-plugin/marketplace.json and add the plugin to the plugins array:

{
  "name": "<plugin-name>",
  "source": "./plugins/<plugin-name>",
  "description": "<description>"
}

Step 6 — Confirm

Show the user the created structure and remind them to install:

claude plugin install <plugin-name>@blynck-tools

Rules

• Always use ${CLAUDE_PLUGIN_ROOT} (not absolute paths) inside hooks/MCP configs
• All component directories (skills/, agents/, hooks/) go at plugin root, never inside .claude-plugin/
• Only create files for components the user actually needs
• Refer to ${CLAUDE_SKILL_DIR}/template/ for concrete file examples
• For full schema details, CLI commands, and troubleshooting, consult ${CLAUDE_SKILL_DIR}/plugin-reference.md