plugin-tester

Plugin validation checks your plugin's directory structure, plugin.json integrity, and knowledge content for marketplace readiness. Run the validation process to ensure your plugin meets all structural and content requirements before deployment.

A valid plugin requires a directory named plugins/{category}-{name}, a .claude-plugin/plugin.json file, and at least one knowledge/*.md file. The plugin.json must include name, version, description, author, and knowledge path fields matching your directory structure.

Yes. Load your plugin in a test Claude project by editing .claude/settings.json to enable it, then run load tests and verify that Claude can access your knowledge files and respond appropriately.

Validation will fail if required fields are missing, the version isn't valid semver, or the plugin name doesn't match your directory name. Fix these structural issues before proceeding to knowledge content validation.

Yes. The validator ensures knowledge files exist and meet content requirements based on plugin type—agent, workflow, skill, domain, platform, or stack—each with mandatory sections that must be present.

Run validation during development to catch structural issues early, again before release as a pre-release gate, and finally during deployment readiness checks to confirm all requirements are met before marketplace publication.