plugin-validation-skill

Claude Code plugin validation verifies manifests, directory structure, and component placement by enforcing frontmatter presence and cross-checking against marketplace definitions. This structured quality gate ensures reliable plugin deployment.

Yes, you can validate MCP server configurations and hooks before marketplace deployment. The validation process checks path portability and component structure, integrating into CI workflows to enforce standards before publishing.

To validate a single Claude Code skill, run `uv run python scripts/validate_skill.py /path/to/skill`. This checks the skill's frontmatter and structure to ensure it meets required quality standards.

Marketplace validation fails when plugins lack required frontmatter, have incorrect component placement, or violate path portability rules. The validation process cross-checks these elements against marketplace definitions to identify structural issues.

Yes, pyyaml is a required dependency for running Claude Code plugin validation. You need to install dependencies in the validation repository before executing the Python scripts to validate plugins, skills, or MCP configurations.

The best way to enforce quality gates for Claude Code plugin releases is integrating structured validation into CI workflows. This verifies plugin manifests, hooks, skills, and MCP configurations before publishing to ensure reliable deployment.