experiment-design

Designs falsifiable experiments and validation benchmarks for agent systems with pre-registered kill criteria.

Updated Aug 2, 2026
One-click install
npx skills add https://github.com/dperussina/function2agent --skill experiment-design-dperussina
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: experiment-design
Source: https://github.com/dperussina/function2agent/tree/main/.cursor/skills/experiment-design
Command: npx skills add https://github.com/dperussina/function2agent --skill experiment-design-dperussina

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Agent-system claims are easy to assert and hard to falsify: LLM judges are anti-correlated with truth on false-success detection, benchmark scores swing 10-20 points on harness alone, and multi-agent wins are often just bigger token budgets. This Skill designs experiments that can actually kill a wrong thesis cheaply, and rejects designs that cannot. ## Core Features & Use Cases - Falsification-first design: Orders experiments so the cheapest test that can kill the thesis runs first, with kill criteria pre-registered before any data exists and never moved afterward. - Deterministic oracles and ceiling tests: Replaces LLM judges in the primary success path with SQL assertions, recording proxies, and reference implementations, and uses a hand-written ideal-tool arm (A8) to separate the value of the idea from the quality of the synthesizer. - Contamination and denominator audits: Detects evaluation sets scored against post-fix states, denominators padded with records the instrument declined, and ablations whose positive result is indistinguishable from a broken instrument. - Use Case: Before building a tool-synthesis pipeline, run the ceiling test comparing hand-written ideal tools against a shell-only baseline; if they score the same, the thesis is dead and it cost a week instead of a quarter. ## Quick Start Use the experiment-design skill to review my planned benchmark comparing a single agent against a multi-agent setup and tell me which controls and kill criteria are missing.

Frequently Asked Questions about experiment-design

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

FAQPage Schema
How do I design an experiment that can falsify an agent system claim?▼

Design backwards from the result that would make you stop, and run the cheapest experiment capable of producing it first. Write kill criteria as pre-registered stop conditions before any data exists, and nominate the person empowered to call the kill.

How to evaluate agent benchmarks without an LLM judge?▼

Use deterministic oracles: SQL assertions over privately-seeded fixtures, HTTP records from a recording proxy, or exact match against hand-written reference queries. Run the LLM judge only as an object of study to measure its AUROC against the oracle, never as a gate.

What is a ceiling test in agent tool evaluation?▼

A ceiling test hand-writes roughly 20 ideal tools (arm A8) and compares them against a shell-only baseline (A0). If A8 approximately equals A0, domain tools do not help and the thesis is dead; the gap A8 minus A2 later measures synthesizer quality.

Why do multi-agent benchmark wins need a budget-matched control?▼

Token spend alone explains most variance in agent benchmarks, so a multi-agent win is uninterpretable without a control. Arm A5 gives a single agent the measured mean budget of the best multi-agent arm; if A5 matches it, the topology contributed nothing.

When is an evaluation set contaminated by fixed defects?▼

An evaluation set is contaminated when defects it scores against have since been repaired, because the score then measures the repair rather than detection. Diff every artifact the score reads between the revision where the defect was live and now; artifacts changed as part of the repair invalidate the result.

Why does a false-alarm rate need a compared-count denominator?▼

Detectors that can decline records produce a third outcome that cannot enter a false-alarm numerator, so counting declines in the denominator pads the rate without adding evidence. Report the rate over records actually compared, and report the refusal rate as its own number.