benchmark

Combines floor results and capability-ceiling delta to emit a verdict.

28|3|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/mifunedev/openharness --skill benchmark-mifunedev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: benchmark
Source: https://github.com/mifunedev/openharness/tree/main/.claude/skills/benchmark
Command: npx skills add https://github.com/mifunedev/openharness --skill benchmark-mifunedev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Benchmark skill provides a structured gate to decide whether a landed change actually improves the harness by combining the regression floor status with the capability-ceiling delta and emitting a single verdict that informs subsequent routing.

Core Features & Use Cases

  • Combines /eval floor results with the capability-ceiling delta to determine BENEFICIAL or NOT-BENEFICIAL.
  • Enforces a deterministic decision path: the first failing signal ends NOT-BENEFICIAL, and both signals clear yields BENEFICIAL.
  • Integrates with the executable loop to drive decisions such as revert or continue and proper routing to repeat.

Quick Start

Run the benchmark step after a change to obtain a decisive verdict and route the loop accordingly.

Frequently Asked Questions about benchmark

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

FAQPage Schema
How do I decide if a code change actually improves an automation harness?

To decide if a code change improves an automation harness, evaluate regression-floor results alongside capability-ceiling deltas to emit a single BENEFICIAL or NOT-BENEFICIAL verdict that informs subsequent routing.

What is a capability-ceiling delta in benchmark evaluation?

A capability-ceiling delta in benchmark evaluation measures the improvement in maximum performance capabilities, which is combined with regression-floor status to determine if a landed change is beneficial.

How do I automate revert decisions in a continuous evaluation loop?

Automate revert decisions in a continuous evaluation loop by running a benchmark step after a change to obtain a decisive verdict, which then guides the control flow to trigger a revert or repeat action.

When does an automation benchmark return a NOT-BENEFICIAL verdict?

An automation benchmark returns a NOT-BENEFICIAL verdict through a deterministic decision path where the first failing signal from either the regression floor or capability ceiling immediately ends the evaluation.

Can I gate deployment routing based on benchmark evaluation results?

You can gate deployment routing based on benchmark evaluation results by integrating the final STATUS line verdict into an executable loop to satisfy gating constraints and direct control flow.

Are there limitations to using deterministic decision paths for harness evaluation?

Deterministic decision paths for harness evaluation are limited by strict sequential logic, meaning the first failing signal ends the evaluation as NOT-BENEFICIAL without evaluating remaining signals.