experiment

Plans and executes research experiment runs with numbered run folders and launch commands.

Updated Aug 26, 2026
One-click install
npx skills add https://github.com/coollx/stable-harness --skill experiment-coollx
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: experiment
Source: https://github.com/coollx/stable-harness/tree/main/.claude/skills/experiment
Command: npx skills add https://github.com/coollx/stable-harness --skill experiment-coollx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Running research experiments involves repetitive ceremony: allocating run numbers, writing configuration overrides, drafting plan documents, and monitoring long-running jobs. This Skill standardizes the full run lifecycle so every experiment follows the same folder structure and commit discipline. ## Core Features & Use Cases - Plan mode: Interviews the researcher in batches of questions, allocates a global run number, writes run.yaml overrides, and produces a structured plan document ending with the exact launch command. - Execute mode: Runs a smoke pass for long jobs, hands off launch commands, monitors run.log for failure signatures, recovers transient failures, and commits summary.json on completion. - Use Case: A researcher sketching a new training run says "plan a run" — the Skill interviews them about configuration, diffs the overrides against a sibling run, writes the plan file, and prepares the launch command without ever auto-launching long jobs. ## Quick Start Ask the assistant to plan a new experiment run for your current hypothesis using the experiment skill.

Frequently Asked Questions about experiment

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

FAQPage Schema
How do I plan a new experiment run?

Invoke the plan mode, which interviews you in batches of three questions with recommended answers, allocates the next global run number, writes run.yaml with overrides only, and produces a plan document ending with the exact launch command.

How do I run a long experiment safely?

For runs expected to exceed about one hour, execute mode runs a smoke pass first — the full workflow on fewer than three instances into outputs/smoke/. A failed smoke means fix the pipeline before launching the real run.

Does the experiment skill launch long jobs automatically?

No. The skill hands the researcher the launch command and never auto-launches long jobs. Short runs may be run directly, and once the researcher launches, the skill has standing authorization to recover transient failures.

How are experiment failures detected and recovered?

The skill monitors outputs/run.log with failure-signature searches, since silence is not success. Transient failures are recovered, each incident is recorded as a dated paragraph in the run log, and long pipelines resume via their volume argument.

What happens when an experiment run completes?

On completion the skill confirms summary.json landed and commits it with the run's spine line. A discarded run commits nothing, keeping the git history clean of abandoned experiments.