Plugin Eval

Guided practice around `claude plugin eval`, which scores a plugin's eval suite: preflight, no-spend validation, a cost estimate, the run, its validity verdict, and the with-versus-without delta. Use when: planning how a headless `claude -p` session launches eval runs, an eval run's delta, arm scores or validity verdict is in question, including whether it can be shared (load this before answering), 'run my plugin evals', 'plugin eval', 'evaluate this plugin', 'eval my skill', 'does my skill actually fire', 'compare two eval runs', 'did my change make the skill better', 'is this gain real', 'aggregate-result.json', 'eval CI gate', 'can this machine run evals', missing socat or bubblewrap, 'how much will this eval cost', 'Bash refuses claude plugin eval', argument order around `--allow-tools`, 'plugin eval blocked in a worktree', 'plugin eval refuses: too many worktrees', 'can plugin eval measure CLAUDE.md or rules'. Not for designing success criteria (/evals:design) or the skill-creator JSON eval format.

melodic-software Updated 30 repo stars

File contents

melodic-software/claude-code-plugins commit c08e432b1c

Frequently asked questions

npx get-skill add melodic-software/plugin-eval