{"version":"2.1.233","anchor":"claude-plugin-validate-works-on-directories-without-a-plugin","canonical_anchor":"claude-plugin-validate-works-on-directories-without-a-plugin","heading":"claude 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\/claude-plugin-validate-works-on-directories-without-a-plugin","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.233","markdown":"### `claude plugin validate` works on directories without a plugin manifest\n\nclaude plugin validate now falls back to checking skills, agents and commands when there is no manifest.\n\n**What**\n\nPointing `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.\n\n**Details**\n\n- The manifest lookup returns an error tagged `NO_MANIFEST`, which is what triggers the fallback rather than aborting.\n- A dedicated message covers the case where the target path or its enclosing `.claude` directory is a symlink.\n- The command's help text was updated to describe both behaviours.\n\n**Usage**\n\n`claude plugin validate .\/my-plugin-dir` **Evidence** `Validate a plugin or marketplace manifest, or the skills, agents, and commands in a directory`\n\n- Area: Plugins\n- Names: `claude plugin validate`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 1\/5"}