plugin-json-schema

Validate Claude Code plugin.json manifests for required fields and auto-discovery.

8|2|Updated Feb 9, 2026
One-click install
npx skills add https://github.com/mikeparcewski/wicked-garden --skill plugin-json-schema
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plugin-json-schema
Source: https://github.com/mikeparcewski/wicked-garden/tree/main/.claude/skills/plugin-json-schema
Command: npx skills add https://github.com/mikeparcewski/wicked-garden --skill plugin-json-schema

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This guide provides a reference and validation framework for Claude Code plugin manifests, helping developers create and troubleshoot plugin.json entries with confidence.

Core Features & Use Cases

  • Comprehensive field reference: name, version, description, author, homepage, repository, license, keywords, commands, agents, skills, hooks, mcpServers, lspServers, and more.
  • Auto-discovery guidance: explains how Claude Code automatically loads standard components and how to structure non-standard components.
  • Validation & best practices: outlines common validation errors, path formats, and recommended project layout for plugins.

Quick Start

Create a plugin.json manifest that follows the standard fields and auto-discovery rules.

Frequently Asked Questions about plugin-json-schema

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is a plugin.json manifest and what fields does it require?

A plugin.json manifest defines Claude Code plugin configurations, requiring name, version, and description fields. It also supports optional metadata like author, homepage, repository, license, and keywords for comprehensive plugin documentation.

How do I validate a plugin.json manifest for Claude Code?

Validate a plugin.json manifest by checking required fields (name, version, description), verifying path formats for standard directories (commands, agents, skills, hooks), and resolving common validation errors outlined in the schema reference.

How does auto-discovery work for Claude Code plugin components?

Auto-discovery automatically loads standard plugin components from designated directories (commands, agents, skills, hooks). Non-standard configurations require explicit declarations in the plugin.json manifest to ensure proper loading.

Can I define custom paths for non-standard plugin configurations in plugin.json?

Yes, non-standard plugin configurations can be defined in plugin.json by explicitly declaring custom paths and components outside the standard auto-discovery directories, ensuring Claude Code loads them correctly.

Why is my plugin.json manifest failing validation?

Plugin.json validation fails when required fields (name, version, description) are missing, path formats are incorrect, or standard directory structures are misconfigured. Review validation errors and ensure fields match the schema reference.

What optional metadata can I include in a plugin.json manifest?

Optional plugin.json metadata includes author, homepage, repository, license, and keywords. These fields enhance plugin discoverability and documentation without affecting core auto-discovery or validation behavior.