How can I verify if my plugin paths are correct?

You can use the validate-plugin-paths.nu script provided by this skill to check if all skill directories, command files, and agents exist and are accessible.

Why shouldn't I include dependencies in my plugin.json?

The 'dependencies' field is reserved for marketplace.json entries; including it in a local plugin.json manifest is considered invalid and may cause validation errors.

Can I configure MCP servers directly in the plugin manifest?

Yes, MCP servers can be configured either as an inline object directly in plugin.json or as a path reference to a separate mcp-config.json file.

Where should the Claude Code plugin manifest be located?

All plugin manifests must be stored at the relative path .claude-plugin/plugin.json within your plugin's root directory.

What is the correct naming convention for a Claude plugin?

Plugins must use kebab-case naming (lowercase letters, numbers, and hyphens only). For example, 'my-custom-plugin' is valid, but 'MyPlugin' is not.

Claude Plugin Architect

Name: Claude Plugin Architect
Author: vinnie357

byvinnie357

배포 및 DevOps

Streamlines the creation, validation, and management of plugin.json manifests for Claude Code extensions.

소개

The Claude Plugin Architect skill is a specialized guide and toolset designed to simplify the development lifecycle of Claude Code plugins. It provides comprehensive schema validation, enforces naming conventions, and ensures that all internal paths for skills, commands, and agents are correctly mapped. By using this skill, developers can automate the validation of manifest files, avoid common configuration errors like using marketplace-only fields, and maintain semantic versioning standards, ultimately ensuring their plugins load reliably within the Claude environment.

주요 기능

Relative path verification for skills, commands, agents, and MCP servers
Detection of invalid marketplace-level metadata in local manifests
0 GitHub stars
Enforcement of kebab-case naming conventions and semantic versioning
Support for inline or referenced hooks and MCP server configurations
Automated plugin.json schema validation for syntax and field requirements

사용 사례

Validating complex plugin configurations before submission to a repository
Troubleshooting plugin loading issues by validating manifest compliance
Scaffolding new plugin directory structures and manifest templates

소개

주요 기능

Relative path verification for skills, commands, agents, and MCP servers
Detection of invalid marketplace-level metadata in local manifests
0 GitHub stars
Enforcement of kebab-case naming conventions and semantic versioning
Support for inline or referenced hooks and MCP server configurations
Automated plugin.json schema validation for syntax and field requirements

사용 사례

Validating complex plugin configurations before submission to a repository
Troubleshooting plugin loading issues by validating manifest compliance
Scaffolding new plugin directory structures and manifest templates