experiment_manager

Manages experiment branches, run reports, artifacts, and promotion workflows for research directions.

5|1|Updated Jul 17, 2026
One-click install
npx skills add https://github.com/WissingChen/my_code_config --skill experiment-manager-wissingchen
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: experiment_manager
Source: https://github.com/WissingChen/my_code_config/tree/main/my_skills/experiment_manager
Command: npx skills add https://github.com/WissingChen/my_code_config --skill experiment-manager-wissingchen

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Research experiments often sprawl across untracked branches, unrecorded expectations, and unverifiable results. This Skill enforces disciplined experiment lifecycle management: every run targets a registered hypothesis, every artifact is accounted for, and every conclusion is traceable to evidence. ## Core Features & Use Cases - Branch and Worktree Lifecycle: Creates and manages exp/NN-slug branches and isolated worktrees with explicit user authorization, keeping exploratory code separate from the base branch. - Run Reports with Frozen Expectations: Each run produces an ENN-experiment-report.md with pre-registered baselines, expected ranges, mechanism predictions, and convergence records written before results are seen. - Artifact Hygiene and Git Policy: Maintains a whitelist of what enters Git (small tables, configs, final figures) versus external storage with checksums, preventing repository bloat. - Closure and Promotion: Synthesizes falsified or validated directions into an illustrated REPORT.md, merging only validated content through a reviewed promote/NN-slug branch. - Use Case: A researcher running a series of model ablation experiments uses this Skill to register hypotheses before each run, track which results narrowed the hypothesis space, and produce a final evidence-linked report when the direction closes. ## Quick Start Ask the assistant to open a new experiment branch for the approved proposal, register the expected results, and produce a run report after execution.

Frequently Asked Questions about experiment_manager

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

FAQPage Schema
How do I manage machine learning experiment branches in Git?▼

Create one `exp/NN-slug` branch per research direction inside an isolated Git worktree, confirmed with the user before creation. Keep exploratory code on the experiment branch and merge only validated content back through a separate promotion branch.

How to write a reproducible experiment run report?▼

Register the research question, baseline, expected result ranges, and mechanism predictions before running. After execution, record actual results with uncertainty, deviation analysis, a convergence record, and a retain/discard manifest for figures and artifacts.

What files should go into Git for ML experiments?▼

Commit only small decision tables, minimal configs, analysis scripts, and final figures. Exclude model weights, caches, dataset copies, full logs, and regenerable outputs; store large valuable files externally with URI, checksum, and producing commit recorded.

When should an experiment direction be stopped or pivoted?▼

Stop and return the direction for rescoping when two consecutive runs fail to shrink any decision-relevant uncertainty. Pivot by archiving the old core hypothesis as superseded and opening a new proposal rather than rewriting project history.

Can experiment branches be merged directly into the main branch?▼

No. Exploratory experiment branches are never merged directly. Only the final report package and validated implementations are merged, through a separately reviewed `promote/NN-slug` branch where every line of the diff is justified.