experiment

Runs a change-measure-decide experiment loop to validate prompt and agent tuning changes.

Updated Aug 5, 2026
One-click install
npx skills add https://github.com/harivansh-afk/loom-index-e2e --skill experiment-harivansh-afk
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: experiment
Source: https://github.com/harivansh-afk/loom-index-e2e/tree/main/skills/experiment
Command: npx skills add https://github.com/harivansh-afk/loom-index-e2e --skill experiment-harivansh-afk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Most prompt, config, and agent tuning changes are unverified guesses, and stochastic LLM outputs make "it looks better" almost always noise. This Skill enforces a disciplined loop: state a hypothesis and observable, measure a baseline, change exactly one thing, run multiple rollouts, and keep or revert based on evidence. ## Core Features & Use Cases - Structured experiment loop: Hypothesis plus concrete observable, baseline measurement, one isolated change, N rollouts, and an explicit keep/revert/inconclusive verdict with a recorded result. - Real-agent A/B testing: Drives the actual Claude or Codex TUI through the index Python harness (tui.harness.Claude) in a PTY, so runs are live-visible on the web dashboard and rollouts are a simple asyncio gather loop. - Confound control: Enforces same-model baselines, neutral non-leading tasks, fresh agents per rollout, and rate-based comparison instead of single samples. - Use Case: You tweak a global skill prompt and want to know if it actually helps. Apply the change, run 5 baseline and 5 candidate rollouts of a representative task through the TUI harness, compare success rates, and keep the change only if it measurably wins. ## Quick Start Ask the agent to A/B test your prompt change by running five baseline and five post-change rollouts of a representative task through the TUI harness and reporting the keep-or-revert verdict with rates.

Frequently Asked Questions about experiment

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

FAQPage Schema
How do I test whether a prompt change actually improves agent performance?▼

Define a concrete observable, measure a baseline with N rollouts before the change, apply exactly one change, then run the same number of rollouts after. Compare success rates and keep the change only if it reliably wins; revert otherwise.

How to A/B test Claude agent behavior with the TUI harness?▼

Use tui.harness.Claude to launch a fresh real agent per rollout, run a neutral task with agent.run(), score each reply against your observable, and gather results concurrently with asyncio. Compare the baseline rate against the post-change rate.

Why not evaluate agent changes with claude -p or tmux?▼

Headless claude -p runs do not match real interactive sessions, and tmux scripting is fragile. The TUI harness spawns the real agent in a PTY, making sessions live-visible on the dashboard with clean programmatic prompt, await, and assertion APIs.

How many rollouts are needed for a reliable experiment result?▼

One run is noise for stochastic LLM outputs; use 3-5 rollouts minimum and more for subtle effects. A shift from 2/5 to 3/5 is inconclusive, so raise N before declaring a small delta a win.

What is the difference between prompt-eval and experiment?▼

prompt-eval confirms a new behavior took effect at all by loading the prompt in a fresh agent. experiment answers the follow-up question of whether the change is actually better than the baseline, using measured rollout rates.

When is a change not testable with this experiment loop?▼

A change is not testable when it produces no concrete observable difference, such as a pass/fail criterion, count, latency, or token total. Subjective impressions like "feels smarter" do not qualify, and the loop says to stop and state that.