What
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.
Details
- 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.
Usage
claude plugin validate ./my-plugin-dirEvidence
Validate 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.
Names in the bundleclaude plugin validate
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Confirmed since
Anthropic's documentation has since written up claude plugin validate, on Claude Code changelog.
* Fixed `claude plugin validate` rejecting plugin paths whose directory name begins with two dots, which the plugin loader acceptschangelog see the edit
Two sources agreeTwo things we can check say the same as this entry.
Anthropic's documentation agrees
Anthropic's documentation has since written up claude plugin validate, on Claude Code changelog.
Anthropic's release notes agree
Improved claude plugin validate to check a bare .claude/skills directory, reporting SKILL.md files whose frontmatter fails to parse