What is the difference between a skill and a plugin?

A skill is a specific behavior or guidance file, while a plugin is a packaging format that bundles skills, commands, agents, and hooks for distribution.

What is the most common error in Claude Code plugin design?

The most frequent mistake is placing directories like 'commands/' or 'agents/' inside the '.claude-plugin/' folder. These must remain at the plugin root to be correctly identified.

Does this skill help with MCP server integration?

Yes, it provides specific patterns for both Stdio and HTTP transports, including workarounds for known interpolation bugs and OAuth flow documentation.

How do I handle secrets like API keys in my plugins?

This skill enforces the use of environment variable references (e.g., ${API_KEY}) in manifest files to ensure sensitive credentials are never hardcoded or committed to version control.

Claude Code Plugin Architect

Name: Claude Code Plugin Architect
Author: racurry

byracurry

Developer Tools

Guides the design, architecture, and distribution of Claude Code plugins using official specifications and best practices.

About

Claude Code Plugin Architect is an essential skill for developers looking to package and share custom extensions. It provides interpretive guidance on the official plugin specification, helping you navigate complex requirements for directory structures, manifest files, and MCP server bundling. By following its structured workflows, you can avoid common pitfalls—such as incorrect folder nesting—and implement secure patterns for environment variables and OAuth authentication. This skill ensures your plugins are not only functional but also ready for marketplace distribution with standardized documentation and validation.

Key Features

Validates directory structures to ensure plugin components are discoverable
Outlines secure environment variable patterns for handling sensitive API keys
0 GitHub stars
Provides templates for plugin.json manifests and MCP server configurations
Offers quality checklists for marketplace-ready plugin distribution
Guides OAuth implementation for remote MCP services using native HTTP transport

Use Cases

Integrating third-party APIs via MCP servers with standardized authentication
Converting local scripts and agents into modular, version-controlled extensions
Packaging internal company workflows into distributable team plugins

About

Key Features

Validates directory structures to ensure plugin components are discoverable
Outlines secure environment variable patterns for handling sensitive API keys
0 GitHub stars
Provides templates for plugin.json manifests and MCP server configurations
Offers quality checklists for marketplace-ready plugin distribution
Guides OAuth implementation for remote MCP services using native HTTP transport

Use Cases

Integrating third-party APIs via MCP servers with standardized authentication
Converting local scripts and agents into modular, version-controlled extensions
Packaging internal company workflows into distributable team plugins