experiment-bridge

Convert EXPERIMENT_PLAN.md into executable training and evaluation runs.

2|1|Updated Apr 19, 2026
One-click install
npx skills add https://github.com/raja21068/AutoResearch --skill experiment-bridge-raja21068
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: experiment-bridge
Source: https://github.com/raja21068/AutoResearch/tree/main/skills/aris/experiment-bridge
Command: npx skills add https://github.com/raja21068/AutoResearch --skill experiment-bridge-raja21068

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the gap between an experiment plan and actually running the experiments, so you can generate initial results without wasting GPU hours on incorrect implementations.

Core Features & Use Cases

  • Implements experiments from a plan: Reads EXPERIMENT_PLAN.md (and related logs) to extract run order, hyperparameters, metrics, and success criteria, then generates the corresponding training/evaluation code.
  • Deploys and collects initial results: Optionally clones a base repo, sanity-runs first, then deploys the full experiment suite with parallel routing and result collection.
  • Prevents costly mistakes with review: Performs an optional cross-model code review (e.g., GPT-5.4 xhigh) before deployment to catch logic errors and evaluation-ground-truth mistakes.

Use Case Example: When you already have a claim-driven EXPERIMENT_PLAN.md from earlier workflows, this Skill converts it into runnable scripts, sanity-checks them, deploys the experiments, and updates refine-logs/EXPERIMENT_TRACKER.md with an initial results summary.

Quick Start

Ask to implement and execute the plan by providing the experiment plan path, for example: implement and run experiments from refine-logs/EXPERIMENT_PLAN.md.

Frequently Asked Questions about experiment-bridge

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

FAQPage Schema
How do I convert an experiment plan into executable training code?

Converting an experiment plan into executable training code involves reading EXPERIMENT_PLAN.md to extract run order and hyperparameters, then automatically generating the corresponding runnable scripts for deployment.

How do I automate sanity checks before running full GPU experiments?

Automating sanity checks before full GPU experiments involves running generated scripts locally first to catch logic errors, then deploying the full experiment suite with parallel routing to collect initial results safely.

Can I use cross-model code review to catch evaluation ground-truth mistakes?

Yes, you can use cross-model code review to catch evaluation ground-truth mistakes by optionally performing an automated review pass before deployment to identify logic errors in the generated training scripts.

Do I need a prepared EXPERIMENT_PLAN.md to deploy research automation workflows?

Yes, you need a prepared EXPERIMENT_PLAN.md file to deploy research automation workflows, because the system reads this plan to extract run order, hyperparameters, metrics, and success criteria for generating executable code.

How do I update an experiment tracker with initial GPU deployment results?

To update an experiment tracker with initial GPU deployment results, the system parses the outputs from the full experiment suite and automatically populates refine-logs/EXPERIMENT_TRACKER.md with an initial results summary.

What is the best way to prevent wasting GPU hours on incorrect experiment implementations?

The best way to prevent wasting GPU hours on incorrect experiment implementations is to generate code from a structured plan, perform sanity runs, and conduct cross-model code review before deploying the full suite.