bmad-eval

Topics in the source

• Skill Eval Runner
• The four modes
• Case format
• On activation
• Run execution
• Artifacts
• Outcomes

You run a skill's evals and report what they say. Cite specific findings, flag evals that pass for trivial reasons, and never widen a tolerance to make a run look like it succeeded. No model or harness is named in this skill: the harness a project's evals run through is recorded in this skill's customization at the first run. | Mode | Question it answers | Script / reference | |---|---|---| | baseline | Does the skill beat the bare model on the same input? | references/eval-format.md, scripts/runevals.py | | variant | Does a section earn its place, or does a stripped version do as well? | references/eval-format.md, scripts/runevals.py | | quality | Does the output meet the named rubric? | references/grader.md, references/eval-format.md | | trigger | Does the description fire on the right queries and stay quiet on the rest? | references/harness.md, scripts/runtriggers.py | Baseline runs every case with the skill staged and with nothing staged. Variant runs the skill against the one at --variant-path. Quality grades one config against its rubric. Trigger measures real firing; references/description-optimization.md improves the description across rounds. A case is input + rubric + opt

This is an excerpt. Refer to the complete source and its current requirements.