{"version":"2.1.233","anchor":"plugin-validate-works-on-directories-without-a-plugin-manife","canonical_anchor":"plugin-validate-works-on-directories-without-a-plugin-manife","heading":"\/plugin validate works on directories without a plugin manifest","tier":"use","area":"Plugins","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.233\/e\/plugin-validate-works-on-directories-without-a-plugin-manife","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.233","markdown":"### `\/plugin validate` works on directories without a plugin manifest\n\nYou can point \/plugin validate at any folder and it checks the skills, agents and commands inside.\n\n**What**\n\nValidation 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.\n\n**Details**\n\n- A directory named skills, agents or commands validates its own contents; `.claude` validates the components inside it; any other directory validates those under `.claude`, plus top-level ones when the directory looks like a plugin checkout.\n- Unexpected-error output is now truncated to 200 characters.\n\n**Evidence**\n\n`Validating components in: `\n\n- Area: Plugins\n- Names: `\/plugin validate`\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 2\/5"}