claude plugin validate now falls back to checking skills, agents and commands when there is no manifest.
What's wrong with this entry?
Pointing claude plugin validate at a directory that has no .claude-plugin/plugin.json or .claude-plugin/marketplace.json no longer just fails. It now falls back to validating the skills, agents and commands subdirectories.
- The manifest lookup returns an error tagged
NO_MANIFEST, which is what triggers the fallback rather than aborting. - A dedicated message covers the case where the target path or its enclosing
.claudedirectory is a symlink. - The command's help text was updated to describe both behaviours.
claude plugin validate ./my-plugin-dirValidate a plugin or marketplace manifest, or the skills, agents, and commands in a directory
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.242
/plugin validateinspects hooks modules instead of a declared capabilities listBoth mention validate