claude-code-plugin-specificationlisted

Use when the user asks about "Claude Code plugin", "plugin.json schema", "plugin manifest", "SKILL.md format", "agent frontmatter", "hook events", "plugin marketplace", "marketplace.json", "plugin structure", "LSP plugin", "plugin hooks", "plugin distribution", or needs to verify plugin conformance, understand plugin component schemas, check hook event behavior, or look up Claude Code plugin specification details. Also applies when building or debugging Claude Code plugins and needing authoritative spec details.
amarbel-llc/purse-first · ★ 1 · AI & Automation · score 70

Install: claude install-skill amarbel-llc/purse-first

# Claude Code Plugin Specification A plugin is a self-contained directory that extends Claude Code with skills, agents, hooks, MCP servers, LSP servers, and settings. This skill is the authoritative reference for the plugin format. For the MCP protocol itself, see **bob:mcp**. ## Plugin Components | Component | Location | Purpose | |:------------|:-----------------------------|:-------------------------------------| | Manifest | `.claude-plugin/plugin.json` | Plugin metadata and configuration | | Skills | `skills/<name>/SKILL.md` | Agent skills (slash commands) | | Agents | `agents/<name>.md` | Specialized subagent definitions | | Hooks | `hooks/hooks.json` | Lifecycle event handlers | | MCP servers | `.mcp.json` | MCP server configurations | | LSP servers | `.lsp.json` | Language server configurations | | Settings | `settings.json` | Default settings (currently `agent`) | Components live at the plugin root. Only `plugin.json` goes inside `.claude-plugin/`. The manifest is optional — Claude Code auto-discovers components in default locations. ## Plugin Manifest (`plugin.json`) | Field | Required | Type | Description | |:---------------|:---------|:--------------|:----------------------------------| | `name` | Yes | string | Uni