research-run

Designs pre-registered ML experiments and interprets run results with statistical verdicts.

Updated Jul 3, 2026
One-click install
npx skills add https://github.com/mnazaal/dotfiles --skill research-run-mnazaal
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: research-run
Source: https://github.com/mnazaal/dotfiles/tree/main/.agents/skills/research-run
Command: npx skills add https://github.com/mnazaal/dotfiles --skill research-run-mnazaal

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? ML experiments often produce uninterpretable results because hypotheses, predictions, and analysis plans are decided after seeing the numbers. This Skill enforces pre-registration before launching runs and structured verdicts after, so comparisons actually answer the question they were designed to test. ## Core Features & Use Cases - Pre-Registration: Records the prediction, decision rule, falsifier, analysis path, and search bounds before any training, split into design-phase and method-phase commitments. - Experiment Design: Sizes comparisons from pilot variance (n ≈ 16σ²/Δ²), pairs arms on seeds, checks oracle ceilings, and verifies the regime is not saturated. - Result Verdicts: Classifies outcomes as improve, degrade, noise, broken, or unknown, with explicit exit paths for each, and writes a predicted-versus-observed block to LOG.md. - Use Case: Before launching an ablation sweep, use this Skill to write the hypothesis as a mechanism, size the seed count from pilot variance, and pre-register the decision rule; after the run, get a verdict on whether the effect exceeds noise. ## Quick Start Use the research-run skill to pre-register my ablation comparing the new attention variant against the baseline before I launch the sweep.

Frequently Asked Questions about research-run

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

FAQPage Schema
How do I pre-register an ML experiment before running it?▼

Pre-registration records five commitments before any numbers exist: the prediction with direction and size, the decision rule linking results to actions, the falsifier, the analysis path, and the search bounds. Split it into design quantities fixed before training and method hyperparameters fixed before touching test data.

How many seeds do I need for an ML comparison?▼

For a two-arm comparison at conventional power, use roughly n ≈ 16σ²/Δ² per arm, where σ is pilot per-seed variance and Δ is the minimum difference worth acting on. Pairing arms on the same seeds usually requires far fewer runs than unpaired arms.

Why is my non-significant ML result not evidence of no effect?▼

A non-significant result from an underpowered design is inconclusive, not evidence of absence. Check whether the design was ever powered for the minimum effect worth acting on; below that sample size the run cannot distinguish no effect from insufficient data.

What does it mean when paired seeds still show large per-seed differences?▼

Large per-seed differences despite shared seeds indicate the arms consume the RNG stream differently, so pairing only held nominally. Diagnose this by reading the arms' RNG consumption in code, not the numbers, since it looks identical to a heavy-tailed effect.

When should I not trust an ablation sweep result?▼

Distrust results when the best cell was selected from many unnamed comparisons, when arms are saturated at a floor or ceiling, when a searched hyperparameter landed at the grid edge, or when the baseline was reimplemented rather than the authors' reference code.