skill-autobench

Generate skill evals from mined conversation history and user corrections.

29.4k|4.4k|Updated Apr 5, 2026
One-click install
npx skills add https://github.com/garrytan/gbrain --skill skill-autobench
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-autobench
Source: https://github.com/garrytan/gbrain/tree/main/skills/skill-autobench
Command: npx skills add https://github.com/garrytan/gbrain --skill skill-autobench

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Spec-derived benchmarks only test what a skill promised, not what users actually asked for or where it actually failed. This Skill authors evals from real usage history — mining conversation archives and session transcripts for invocations and corrections — so benchmarks reflect lived behavior instead of imagination.

Core Features & Use Cases

  • History Mining: Searches the brain's conversation archive and per-harness session transcripts for real invocation windows, treating user corrections after an invocation as the gold failure signal.
  • Eval Synthesis: Produces a proposed eval_contract plus 4-8 replayable cases, each labeled HISTORY-IMPLIED or SPEC-DERIVED, staged as PENDING-HUMAN-APPROVAL without ever rewriting SKILL.md.
  • Panel Integrity & Fail-Improve Taxonomy: Verifies multi-model judging panels actually returned distinct provider responses, and classifies mined failures into deterministic-codifiable, prompt-fixable, spec-gap, or routing-miss fixes.
  • Use Case: After repeatedly correcting a media-ingest skill's date formatting, run autobench to mine those corrections, stage a grounded eval, and feed approved cases into skillopt-benchmark.jsonl for optimization.

Quick Start

Ask the agent to autobench a named skill, for example: autobench the media-ingest skill and write the eval from my usage history.

Frequently Asked Questions about skill-autobench

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

FAQPage Schema
How do I write an eval for a skill from its usage history?

Run skill-autobench with the target skill name. It mines the brain's conversation archive and session transcripts for real invocations and corrections, then stages a proposed eval_contract with 4-8 replayable cases at skills/<name>/eval/autobench-<date>.md for human approval.

What happens if a skill has no usage history to mine?

The skill fails closed: it emits an honest no-history report listing substrates checked and queries run, and never fabricates typical invocations. For skills with no history, use gbrain skillopt <name> --bootstrap-from-skill for a spec-derived benchmark instead.

Does skill-autobench modify SKILL.md automatically?

No. It never rewrites SKILL.md, triggers, or any routing surface. The synthesized eval is staged with status PENDING-HUMAN-APPROVAL, and merging the approved eval_contract into frontmatter is an explicit human decision.

How does it verify a multi-model judging panel is real?

It asserts over the judging result object that each named model returned a non-empty response, that responses came from distinct provider endpoints, and that no two differently-named models returned byte-identical output. The check is pure assertion logic with no model calls.

How are mined cases with real names and companies handled?

All mined cases are privacy-scrubbed before staging: real people, companies, and deals are rewritten onto placeholder slugs like alice-example and acme-example. Cases keep their shape and failure mode but never their real entities.

When should I use skill-autobench versus skill-optimizer?

skill-optimizer improves a skill's body against an existing benchmark, while skill-autobench authors the benchmark itself from lived usage and feeds it into skillopt-benchmark.jsonl. Use autobench when real invocation history exists; use skillopt --bootstrap-from-skill when it does not.