experiment-run

Collects experiment results and routes screening or confirmation outcomes through the research pipeline.

Updated Aug 18, 2026
One-click install
npx skills add https://github.com/Nitrogen216/awesome-dsh-mods --skill experiment-run-nitrogen216
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: experiment-run
Source: https://github.com/Nitrogen216/awesome-dsh-mods/tree/main/modes/dsh-autoresearch/skills/experiment-run
Command: npx skills add https://github.com/Nitrogen216/awesome-dsh-mods --skill experiment-run-nitrogen216

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It turns completed background experiment jobs into disciplined, auditable pipeline decisions, preventing premature promotion, post-hoc threshold changes, and uncontrolled reruns in autonomous research workflows. ## Core Features & Use Cases - Result Collection: Verifies the plan, baseline, reserved scientific run id, and DSH job completion, then recomputes the declared metric and appends a factual record to research/RESULTS.jsonl. - Screening Routing: Routes passing runs to confirmation and failing runs back to mapping or literature with explicit outcomes like screen_pass or screen_fail. - Confirmation Routing: Promotes only frozen candidates that pass the full promotion rule, and rejects unstable or guardrail-violating results as not_confirmed. - Use Case: After experiment-bridge launches a screening run, use this skill to collect the finished job, record the metric delta, and decide whether the candidate advances to confirmation or returns to candidate mapping. ## Quick Start Collect the completed experiment run reserved by experiment-bridge and route the screening result to the next pipeline stage.

Frequently Asked Questions about experiment-run

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

FAQPage Schema
How do I route a screening experiment result in an autonomous research pipeline?▼

Compare the recomputed metric against the precommitted threshold and guardrails. Passing runs move from screening to confirmation with outcome screen_pass, while no-gain runs return to mapping or literature with outcome screen_fail.

How do I collect results from a background experiment job?▼

Verify the plan, baseline, reserved run id, and job completion, then persist the job id, command, config, commit, seed, and raw-result path. Recompute the declared metric from raw outputs and append one factual record to research/RESULTS.jsonl.

When can a screening result be promoted directly?▼

Never. Screening-only results cannot be promoted; a candidate must pass the full promotion rule during the confirmation phase with a frozen implementation before moving to promotion.

What happens when an experiment run fails due to a bug?▼

Invalid runs caused by bugs or infrastructure failures can be fixed and rerun only if the scientific comparison was never observed. When leaving the candidate, record the outcome as invalid rather than screen_fail.

Can I adjust the decision threshold after seeing experiment results?▼

No. The candidate and decision threshold are precommitted and must not be modified after observing a result, which prevents post-hoc bias in the research pipeline.