bmad-eval-runner

Run skill evals across baseline, variant, quality, and trigger modes and report graded results.

Updated Sep 3, 2026
One-click install
npx skills add https://github.com/watchthelight/shatterfish --skill bmad-eval-runner-watchthelight
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-eval-runner
Source: https://github.com/watchthelight/shatterfish/tree/main/.claude/skills/bmad-eval-runner
Command: npx skills add https://github.com/watchthelight/shatterfish --skill bmad-eval-runner-watchthelight

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve? It answers whether a skill actually earns its place by measuring it against the bare model, a stripped variant, a rubric, and real trigger queries, instead of relying on intuition about whether the skill helps. ## Core Features & Use Cases - Four eval modes: baseline (skill vs bare model), variant (full vs stripped version), quality (output vs rubric via a read-only grader), and trigger (does the description fire on near-miss queries). - Isolated, reproducible runs: each case executes in a clean working directory with a from-scratch environment, permanent run folders, and timing/token capture written to disk immediately. - Description optimization loop: stratified train/test query splits with the test set blinded from the improver, so trigger descriptions are tuned without overfitting. - Use Case: After editing a skill's description, run trigger mode to measure false positives and false negatives on near-miss queries, then iterate the description across bounded rounds and pick the winner by held-out test score. ## Quick Start Ask the AI to run the evals for the skill at a given path in baseline and quality mode and report where the run folder was written.

Frequently Asked Questions about bmad-eval-runner

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I evaluate whether a skill is better than the bare model?

Run baseline mode, which executes each case twice in identical clean environments: once with the skill staged and once with nothing staged. Comparing the two configs shows whether the skill produces something the bare model cannot.

How do I test if a skill description triggers on the right queries?

Use trigger mode with a queries file of near-miss should-trigger and should-not-trigger pairs. The runner stages a synthetic skill, sends each query through the adapter multiple times, and reports the trigger rate per query against a threshold.

What eval modes does the skill eval runner support?

Four modes: baseline (skill versus bare model), variant (full skill versus a stripped version), quality (output graded against a rubric), and trigger (description firing measured through the platform adapter). Each mode answers a different question about the skill.

Does the eval runner work with runtimes other than Claude Code?

Yes, everything runtime-specific lives behind a platform adapter JSON file defining the invocation command, auth env var, transcript format, and skill directory. A Claude Code adapter ships in assets, and other runtimes can be added by writing a new adapter config.

Why does trigger detection reject substring matching on transcripts?

The runtime's init event lists every discovered skill by name, so a substring match would report a 100% trigger rate regardless of the description. Only tool_use events, such as a Skill call or a Read of the skill's SKILL.md, count as a genuine load.

What happens when no platform adapter is configured?

The runner degrades gracefully instead of crashing: it stages every case with the skill, fixtures, and composed prompt, writes a manifest, and records each result as skipped until an adapter is configured.