Use it now
Useful4 Signal2
You can point /plugin validate at any folder and it checks the skills, agents and commands inside.
What's wrong with this entry?
Anonymous. No account, no email.
/plugin validate
What
Validation no longer requires a plugin manifest. Point it at a path with no plugin.json or marketplace.json and it validates the skills, agents and commands underneath instead, printing a Validating components in: header rather than the manifest header.
Details
- A directory named skills, agents or commands validates its own contents;
.claudevalidates the components inside it; any other directory validates those under.claude, plus top-level ones when the directory looks like a plugin checkout. - Unexpected-error output is now truncated to 200 characters.
Evidence
Validating components in:
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