Skip to content
BENIBIX Learn

claude plugin validate Command

Also known as claude plugin validate, Validate a plugin

It checks a plugin you are making for mistakes.

Think of it like

It is like a friend reads your work first. They find what is wrong before you hand it in.

Example

Jack's plugin repo runs claude plugin validate on each pull request. One day plugin.json is missing a field. The check fails before anyone installs it.

Why it matters

A plugin with a broken manifest fails for everyone who installs it. This catches it first.

Definition

claude plugin validate checks a plugin you are making. It reads the plugin's manifest, a marketplace's manifest, or the skills, agents and commands in a folder. Then it lists what is wrong. It ends with code 0 when all is well and 1 when it finds a problem. So a CI job can stop a broken plugin from being shared.

Example code

bash
claude plugin validate ./my-plugin
Check a plugin folder.
validate and eval come before you share it, on the maker's side.

Common mistake

Thinking a pass means the plugin works well. It checks the shape of the files, not whether its skills do a good job. claude plugin eval tests that.

Key takeaways

  1. 1
    Checks the files. Manifests and parts.
  2. 2
    Exit 0 or 1. CI can stop it.
  3. 3
    Shape, not quality. eval tests that.

Compare

Learn it properly