ml-experimentation

Manage machine learning experiment lifecycles from planning to reporting.

38|5|Updated Dec 20, 2025
One-click install
npx skills add https://github.com/ericmjl/skills --skill ml-experimentation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ml-experimentation
Source: https://github.com/ericmjl/skills/tree/main/skills/ml-experimentation
Command: npx skills add https://github.com/ericmjl/skills --skill ml-experimentation

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Planning, executing, and reporting machine learning experiments can be complex and error-prone; this skill provides a repeatable lifecycle with journaling, diagnostics, and a canonical artifact structure to improve reproducibility and communication.

Core Features & Use Cases

  • Experiment lifecycle management: planning, fast iteration, script execution, logging, journaling, plotting, and scientific report writing.
  • Deterministic runs and artifacts: strict canonical tree with JOURNAL.md, runs/, logs/, plots/ to enable reproducibility and auditability.
  • Scalability and governance: supports rapid de-risked runs (< 60 seconds) and full runs for hypothesis validation, with structured data and plots for reporting.
  • Use Case: a data scientist plans a new experiment, conducts quick iterations, records observations in JOURNAL.md, and publishes a final report with plots and tables.

Quick Start

Plan a new hypothesis, initialize an experiment, and run an initial de-risked iteration using the provided scripts to generate a JOURNAL.md and baseline logs.

Frequently Asked Questions about ml-experimentation

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

FAQPage Schema
How do I manage end-to-end machine learning experiment lifecycle from planning to reporting?

To manage the end-to-end machine learning experiment lifecycle, you can use a structured workflow that supports hypothesis-driven iteration, journaling, plotting, and formal report writing. This ensures reproducibility through a canonical runs structure including JOURNAL.md, logs, and plots.

How do I structure ML experiment runs for reproducibility and auditability?

To structure ML experiment runs for reproducibility and auditability, maintain a strict canonical tree with JOURNAL.md, runs/, logs/, and plots/. This deterministic artifact structure enables fast iteration, scientific reporting, and clear tracking of log-based metrics.

Do I need uv or pixi to execute scripts for hypothesis-driven ML experiments?

Yes, you need a deterministic workflow with uv or pixi for script execution when running hypothesis-driven ML experiments. This requirement ensures that your de-risked runs and full validation iterations execute consistently and reliably across different environments.

What is the best way to run rapid de-risked iterations for machine learning experiments?

The best way to run rapid de-risked iterations for machine learning experiments is to execute scripts under 60 seconds that generate baseline logs and a JOURNAL.md. This approach allows quick hypothesis testing before committing to full validation runs.

How does journaling work during fast ML experiment iterations?

Journaling during fast ML experiment iterations works by recording observations directly in a JOURNAL.md file within a canonical runs structure. This practice captures hypothesis changes, logs metrics, and supports plotting and final scientific report generation.

Can I use this approach for full hypothesis validation runs instead of just quick iterations?

Yes, you can use this approach for full hypothesis validation runs. The workflow supports both rapid de-risked runs under 60 seconds and full runs for comprehensive hypothesis validation, utilizing structured data, logs, and plots for final reporting.