plugin-checker

Plugin validation checks manifest files, directory layout, agent files, skills, commands, and hooks for correct formation. Run the validate-plugin.sh script to verify existence, syntax, naming conventions, field presence, JSON validity, and security hygiene across all plugin components to catch structural issues early.

Plugin structure expectations include properly organized manifests, agent files, skills, commands, and hooks following naming conventions and file hierarchy standards. The validation checklist confirms your layout matches best practices and Claude plugin ecosystem requirements before deployment.

Best practices enforce comprehensive validation: check JSON syntax in manifests, verify field presence and types, validate frontmatter formatting, apply security hygiene checks, and follow naming conventions. Adhering to these guidelines prevents misconfigurations and ensures plugin conformance with Claude Code standards.

Validation failures typically stem from malformed manifests, missing required fields, incorrect syntax, naming convention violations, or security issues. Error diagnosis identifies which components—manifests, agent files, skills, commands, or hooks—contain problems so you can remediate them systematically.

Yes, validation guidelines apply to both new and existing plugins. Run the validation checklist against your current plugin structure to identify misconfigurations, conformance violations, and best practice gaps, then remediate discovered issues to align with Claude plugin ecosystem standards.