# Build Claude Code Plugin Structures

Plugin authors need a reliable structure before adding commands, agents, skills, hooks, or MCP servers. This skill explains the expected layout, manifest fields, naming rules, and portable path patterns.

## Install

```bash
npx skillstore add anthropics/plugin-structure
```

## Metadata

- Status: approved
- Slug: plugin-structure
- Version: 0.1.0
- Author version: 0.1.0
- Skillstore revision: r1
- Version status: valid
- Tree hash: 231fcbfe446be2298c009729d2799a2d84acb6bd1bca30a46a8a43bb4aa3acb3
- Author: anthropics
- GitHub username: anthropics
- License: MIT
- Repository: https://github.com/anthropics/claude-code/tree/main/plugins/plugin-dev/skills/plugin-structure
- Ref: dbe0e719813583400773166a0621f8a9b8185c72
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands, network, filesystem, env\_access
- Quality score: 80
- Quality tier: silver
- Public page: https://skillstore.pages.dev/skills/plugin-structure
- Manifest: https://skillstore.pages.dev/api/skills/plugin-structure/manifest

## Capabilities

- Explains the required .claude-plugin/plugin.json manifest location.
- Describes default directories for commands, agents, skills, hooks, and MCP servers.
- Shows how custom component paths supplement default discovery paths.
- Defines naming conventions for plugin files, directories, and components.
- Documents portable path usage with the CLAUDE\_PLUGIN\_ROOT variable.
- Provides minimal, standard, and advanced plugin organization examples.

## Use Cases

- Scaffold a New Plugin: Create a clean plugin directory with a manifest and only the component folders needed for the first release.
- Review Plugin Organization: Check whether commands, agents, skills, hooks, and MCP server files follow expected discovery and naming rules.
- Document Team Plugin Standards: Convert plugin architecture rules into simple guidance for teams that maintain shared developer automation.

## Prompt Templates

### Plan a Simple Plugin

```
Design a minimal Claude Code plugin named <plugin-name> with one command. Include the required folders and explain each file.
```

### Add Components

```
Extend my plugin plan with commands, agents, and skills. Keep default discovery paths unless a custom path is necessary.
```

### Review Manifest Paths

```
Review this plugin manifest plan for path issues, naming issues, and missing metadata. Suggest corrections without adding extra features.
```

### Design Advanced Layout

```
Create an advanced Claude Code plugin architecture for <workflow>. Include component boundaries, safe path conventions, and review notes.
```

## Limitations

- It provides structure guidance but does not install or publish plugins.
- It does not validate plugin manifests against a live Claude Code runtime.
- It does not generate production-ready hook scripts or MCP servers.
- Examples require review before use in security-sensitive environments.

## Best Practices

- Start with default discovery directories before adding custom manifest paths.
- Use kebab-case names that describe each component purpose clearly.
- Use CLAUDE\_PLUGIN\_ROOT for plugin-owned files instead of hardcoded local paths.

## Anti Patterns

- Putting commands, agents, skills, or hooks inside the .claude-plugin directory.
- Using parent directory traversal or absolute paths in manifest component fields.
- Adding hooks or MCP servers before documenting their runtime dependencies and permissions.

## Security Audit

- Audited at: 2026-07-20T03:38:56.874\+00:00
- Summary: All 218 static findings are false positives caused by Markdown syntax, code fences, documentation examples, and configuration placeholders. The skill provides structural guidance only; no evidence of prompt injection, credential exfiltration, hidden execution, or malicious intent was found.

## Stats

- Views: 679
- Downloads: 10
- Favorites: 1
- Popularity score: 0