bmad-eval-runner

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

6|Updated Aug 29, 2026
One-click install
npx skills add https://github.com/HordRicJr/Akomagni --skill bmad-eval-runner-hordricjr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-eval-runner
Source: https://github.com/HordRicJr/Akomagni/tree/main/bmad-core/.agents/skills/bmad-eval-runner
Command: npx skills add https://github.com/HordRicJr/Akomagni --skill bmad-eval-runner-hordricjr

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve? Evaluating whether a skill actually improves on the bare model, whether a section earns its place, or whether a description triggers correctly is usually guesswork. This Skill runs structured evals against a skill's cases and reports evidence-backed results instead of impressions. ## 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 (description firing measured through a platform adapter). - Isolated, reproducible runs: each case executes in a clean working directory with a from-scratch environment, staged fixtures, and immediate timing/token capture to timing.json. - Description optimization loop: near-miss query generation, stratified train/test split, and blinded iterative rewriting to improve trigger accuracy. - Use Case: After editing a skill's description, run trigger mode to measure whether it fires on the right queries and stays quiet on near misses, then pick the winning description by held-out test score. ## Quick Start Run the evals for the skill at path/to/my-skill in baseline mode and tell me whether it beats the bare model.

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 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 should-trigger and should-not-trigger near-miss queries. The runner stages a synthetic skill, sends each query through the platform adapter multiple times, and reports the trigger rate per query.

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 adapter). Modes can be repeated in one invocation.

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

Yes, all runtime-specific behavior lives behind a JSON platform adapter 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.

What happens when no platform adapter is configured?

The runner degrades gracefully instead of crashing: it stages every case with fixtures and composed prompts, writes a manifest, and records each result as skipped. A configured runtime can complete the run later.

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.