skill-autobench

Generate skill evaluation benchmarks from real usage history and user corrections.

Updated Aug 17, 2026
One-click install
npx skills add https://github.com/AMC-JTC/gbrain-1 --skill skill-autobench-amc-jtc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-autobench
Source: https://github.com/AMC-JTC/gbrain-1/tree/main/skills/skill-autobench
Command: npx skills add https://github.com/AMC-JTC/gbrain-1 --skill skill-autobench-amc-jtc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Spec-derived evals only test what a skill promised, not what users actually asked for or where it actually failed. This Skill mines real invocation history to author grounded, replayable evals with honest evidence labels. ## Core Features & Use Cases - Usage Mining: Extracts invocation windows from the brain's conversation archive and per-harness session transcripts, treating post-invocation user corrections as gold failure signals. - Eval Synthesis: Produces an 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 benchmark, and feed it into SkillOpt for improvement. ## Quick Start Autobench the media-ingest skill by mining my conversation history and corrections to stage a proposed eval for my review.

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 based on real usage?

Run skill-autobench against the target skill name. It mines invocation windows from the brain's conversation archive and session transcripts, 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 history-less skills, 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 do I verify a multi-model judging panel did not collapse to one provider?

Assert over the result receipt that each named model returned a non-empty response, responses came from distinct provider endpoints, and no two differently-named models returned byte-identical output. These checks are pure assertion logic with no model calls or network cost.

How are mined user corrections classified for fixing?

Each correction is classified by cheapest durable fix: DETERMINISTIC-CODIFIABLE (convert repeated LLM fallbacks to code plus a test), PROMPT-FIXABLE (eval case plus SkillOpt run), SPEC-GAP (report to human), or ROUTING-MISS (route to routing-eval.jsonl).

Does the staged eval contain real names and companies from my history?

No. Before staging, every mined case is rewritten onto placeholder slugs like alice-example and acme-example. Cases keep their shape and failure mode but never real entities, since staged evals live in the distributable skill repo.