ml-experiment-tracking

Enforce ML experiment reproducibility by logging code, data, and configuration versions.

7|Updated Feb 14, 2026
One-click install
npx skills add https://github.com/KentoShimizu/sw-agent-skills --skill ml-experiment-tracking-kentoshimizu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ml-experiment-tracking
Source: https://github.com/KentoShimizu/sw-agent-skills/tree/main/skills/ml-experiment-tracking
Command: npx skills add https://github.com/KentoShimizu/sw-agent-skills --skill ml-experiment-tracking-kentoshimizu

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) and references (resource) components.

What problem does it solve?

ML experiments often suffer from poor reproducibility and opaque provenance, making comparisons and audits difficult.

Core Features & Use Cases

  • Enforces a shared experiment-tracking schema with mandatory fields (Run ID, code version, data version, feature version, hyperparameters) and artifact lineage rules.
  • Supports templates and references for reproducibility metadata, allowing teams to standardize run tracking and reporting.
  • Useful for research, model development, and production tuning where multiple runs must be compared or reproduced.

Quick Start

Create a new experiment entry by logging code, data, and configuration versions and then generate a reproducibility report.

Frequently Asked Questions about ml-experiment-tracking

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

FAQPage Schema
How do I make ML experiments reproducible for auditing?

Tracking ML experiment metadata requires logging mandatory fields like Run ID, code version, data version, and hyperparameters. This Skill enforces a shared schema to capture these variables, ensuring artifact lineage and reliable reproduction across multiple runs.

What is the best way to compare multiple model training runs?

Comparing multiple model training runs requires standardizing experiment tracking with a shared schema. This Skill enforces mandatory metadata fields and artifact lineage rules, allowing teams to reliably compare, audit, and reproduce different model development pipelines.

How do I track artifact lineage across different ML pipelines?

You can track artifact lineage by enforcing reproducibility rules that capture code, data, and configuration versions. This Skill provides templates and a shared tracking schema to ensure artifact lineage is maintained across experiments and deployments.

Do I need specific dependencies to enforce reproducibility checks?

No specific dependencies are required to enforce reproducibility checks. This Skill provides templates and references for metadata tracking, allowing you to verify runs and generate reproducibility reports without external tool restrictions.

When do I need a shared experiment tracking schema?

You need a shared experiment tracking schema during model development, research, or production tuning where multiple runs must be compared or audited. It ensures reliable reproduction by enforcing mandatory fields like code, data, and feature versions.