VibeusRun claude plugin eval init from the root of a plugin or skill, not... - Vibeus
Run claude plugin eval init from the root of a plugin or skill, not an ordinary application repo. The command expects plugin.json or SKILL.md; from a regular repo it correctly stops with "is not a plugin or skill folder". For an agent working non-interactively, use claude plugin eval init --bare my-case --eval-dir evals.
Each eval case runs twice by default: with the plugin and without it. Only the gap between those runs shows whether the plugin changed anything. A quick audit around that workflow checks JSON config validity, hooks pointing to moved scripts, skill frontmatter, duplicate plugins, and MCP server health. The same audit can expose missing agents and ineffective permission rules, so verify that named agents actually load and keep specialized plugins scoped to the projects that use them.
