bmad-eval-runner

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

1|Updated Sep 18, 2026
One-click install
npx skills add https://github.com/PastaSus/egg-defender --skill bmad-eval-runner-pastasus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-eval-runner
Source: https://github.com/PastaSus/egg-defender/tree/main/.agents/skills/bmad-eval-runner
Command: npx skills add https://github.com/PastaSus/egg-defender --skill bmad-eval-runner-pastasus

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 LLM grader), and trigger (does the description fire on near-miss queries). - Isolated, platform-agnostic runs: each case executes in a clean working directory with a from-scratch environment, with all runtime specifics behind a JSON adapter seam. - Variance benchmarking and description optimization: repeat runs are aggregated into mean/stddev/delta statistics, and a blinded train/test loop rewrites trigger descriptions without overfitting. - Use Case: Before shipping a new skill, run baseline mode to confirm it beats the bare model, quality mode to grade its outputs against a rubric, and trigger mode to verify its description fires on the right queries. ## Quick Start Run the evals for the skill at path/to/my-skill in baseline and quality mode and tell me where the run folder landed.

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 beats the bare model?

Run baseline mode, which executes every case twice in identical clean working directories: 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 should-trigger and should-not-trigger near-miss queries. The runner stages a synthetic skill, sends each query through the adapter multiple times, and measures the trigger rate against a threshold.

What is the eval case format for skill testing?

A case is a JSON object with an id, input, rubric list, optional state_prefix, and optional fixture files. The state_prefix is a bracketed prime prepended to the input that places the skill mid-workflow in a single shot.

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

Yes, all runtime specifics live behind a JSON adapter config 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 file.

Why does trigger detection reject substring matching?

The runtime's init event lists every discovered skill by name, so a whole-transcript substring match would report a 100% trigger rate regardless of the description. Only tool_use events naming the synthetic skill or reading its SKILL.md count as a load.

What happens when no adapter is configured for an eval run?

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