experiment

Executes and records auditable main experiment runs against an accepted baseline.

Updated Apr 1, 2026
One-click install
npx skills add https://github.com/zniihgnexy/vid_tokenizer --skill experiment-zniihgnexy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: experiment
Source: https://github.com/zniihgnexy/vid_tokenizer/tree/main/.ds/codex-home/skills/deepscientist-experiment
Command: npx skills add https://github.com/zniihgnexy/vid_tokenizer --skill experiment-zniihgnexy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Research quests often stall or produce untrustworthy results because experiments are run ad hoc, without a defined contract, comparable baseline, or durable records. This Skill turns a selected idea into auditable evidence by enforcing a disciplined run contract, controlled execution, and honest result recording. ## Core Features & Use Cases - Run Contract Definition: Locks the research question, hypotheses, baseline, metrics, stop conditions, and budget in PLAN.md and CHECKLIST.md before any code changes. - Disciplined Execution: Requires bounded smoke tests before long runs, durable logging via bash_exec, structured progress markers, and explicit monitoring cadences. - Durable Evidence Recording: Produces run manifests, metrics files, claim-validation records, and a structured evaluation summary routed through artifact.record_main_experiment. - Use Case: After accepting a baseline and selecting an idea in a machine-learning research quest, use this Skill to implement the minimal change, run a pilot, execute the full training run with monitored logs, and record a verdict of supported, refuted, or inconclusive against the baseline. ## Quick Start Ask the agent to run the main experiment for the currently selected idea against the accepted baseline and record the results.

Frequently Asked Questions about experiment

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

FAQPage Schema
How do I run a main experiment against a baseline in a research quest?▼

Confirm the selected idea, baseline reference, dataset split, primary metric, and stop condition, then write PLAN.md and CHECKLIST.md. Run a bounded smoke test first, launch the real run with durable logging, validate outputs, and record the result with artifact.record_main_experiment.

What should an experiment plan include before running code?▼

A plan should state the research question, null and alternative hypotheses, baseline and comparability contract, code touchpoints, smoke and full-run commands, stop and abandonment conditions, and fallback options. The provided plan and checklist templates define the canonical structure.

When should I not use the experiment stage?▼

Skip it when the baseline gate is unresolved, the idea stage still has open tradeoffs, or the real need is writing or follow-up analysis rather than a main run. Resolve missing preconditions through the decision stage first.

How are long-running training runs monitored safely?▼

Launch long runs detached through bash_exec, emit throttled single-line JSON progress markers, and follow a wait-and-check cadence of roughly 60s, 120s, 300s, 600s, then 1800s intervals. Kill and relaunch cleanly if the run is wedged or invalid.

What happens if experiment results look suspiciously good?▼

Treat suspiciously strong or baseline-identical metrics as a diagnosis trigger, not a success. Stop brute-force retrying, run the smallest discriminative test to separate hypotheses, and verify comparability before claiming any delta.

What durable outputs must a main experiment produce?▼

A run directory with artifact_manifest.json, run_manifest.json, metrics.json, metrics.md, summary.md, exported logs, and a claim-validation record mapping each claim to a verdict of supported, refuted, or inconclusive, plus an explicit next-action decision.