Skip to content
Development
Skill

/experiment-tracking-review

Use when reviewing ML training code to confirm a run could be reconstructed later -- hyperparameters, metrics, data references, and artifacts logged, not just printed to stdout.

From plugin
agent-powerups
8114 skills46 agents54 commands

Claude Code

$ npx -y skills add yeaight7/agent-powerups --skill experiment-tracking-review --agent claude-code

SKILL.md

experiment-tracking-review.SKILL.md
name: experiment-tracking-review
description: Use when reviewing ML training code to confirm a run could be reconstructed later -- hyperparameters, metrics, data references, and artifacts logged, not just printed to stdout.

Purpose

An ML experiment is useless if you cannot reconstruct exactly how it was run and what data it used. This review checks that everything needed for reconstruction is logged.

When to Use

  • Reviewing a training script before serious experiment cycles begin
  • Results exist but nobody can say which configuration produced them
  • Metrics are printed to stdout only

Inputs

  • The training script(s) and any tracking/config setup (MLflow, wandb, config files)

Workflow

1. **Hyperparameter logging**: the script logs *every* hyperparameter (learning rate, batch size, architecture details). Hardcoded magic numbers must be extracted to a config and logged. 2. **Metric logging**: training and validation metrics are logged at each epoch or step, not just at the end. 3. **Artifact saving**: final model weights, preprocessing scalers/encoders, and the exact configuration file are saved together in a versioned directory or tracking system. 4. **Data reference**: the run records which data it used (path, version, or hash). 5. **Enforce structured logging** (JSON, MLflow, wandb) — stdout-only metric reporting is a blocking finding.

Output

  • A finding list of what is not logged or saved, with the specific fix for each gap

Verification

  • [ ] Every hyperparameter logged (no unlogged magic numbers remain)
  • [ ] Per-epoch/step train and validation metrics logged
  • [ ] Weights + preprocessors + config saved together, versioned
  • [ ] Data reference (path/version/hash) recorded with the run
  • [ ] No stdout-only metric reporting remains

Failure Modes

  • **End-only metrics** — a final score without curves hides divergence and the onset of overfitting.
  • **Orphaned artifacts** — weights saved without the matching scaler/encoder and config cannot be served correctly later.
  • **Config drift** — the logged config differs from what the script actually used; log the resolved config at runtime.
Read more
@yeaight7
Ships withagent-powerups

Curated power-ups for coding agents: skills, slash commands, MCP configs, hooks, AGENTS.md templates, and workflows for serious software engineering. Claude Code, Codex, Antigravity CLI, Cursor and more

8114 skills46 agents
Get the whole plugin

Stars on GitHub

Momentum

stars in total
8
Star history of yeaight7/agent-powerups on GitHub, a chart by star-history.com

Other skills on agent-powerups.

More skills from other plugins.

brainstorming
Auto-invoked

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…

@obra@obraInstall Skill
ask-matt

ask-matt

Ask which skill or flow fits your situation. A router over the skills in this repo.

skills11d309k
@mattpocock@mattpocockInstall Skill
accessibility
Auto-invoked

accessibility

Design, implement, and audit accessible UI to WCAG 2.2 Level AA across Web, iOS, and Android — semantic ARIA roles and labels,…

ecc13d293k
@affaan-m@affaan-mInstall Skill
compiler-commit

compiler-commit

Use when you want to verify compiler changes and commit with the correct convention. Runs tests, lint, and format, then commits…

react2d252k
@facebook@facebookInstall Skill

Questions about experiment-tracking-review.

Which coding agents can use experiment-tracking-review?
experiment-tracking-review installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.