agentleFS
boeschjboeschj/ml-intern-plugin/skills/trackio/SKILL.md

trackio

Skill0 starsChanged 4 months agoApache-2.0View on GitHub

Configure trackio experiment monitoring for training runs, add alert callbacks, read alerts back between runs, and derive the next run's config from prior alerts. Use for any training job monitoring or when iterating on hyperparameters.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 1 is distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use trackio.alert(title, text, level) at every decision point in training.

    line 19
  2. Distinctive:

    Always include numeric values and an actionable suggestion in the text, for example "loss=12.4 at step 200, lr likely too high, try x0.1".

    line 24
  3. Very specific:

    Read alerts between runs instead of parsing thousands of metric points.

    line 30
  4. Very specific:

    Read the prior config via api.runs(...).config and only mutate keys the alerts justify changing.

    line 51

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Trackio is natively integrated with Transformers Trainer and all TRL trainers; the built-in TrackioCallback handles init, log, and finish. In TrainingArguments, SFTConfig, DPOConfig, or GRPOConfig set:

report_to="trackio"
run_name="sft_qwen3-4b_lr2e-5_bs128"
project="<descriptive-project-name>"
trackio_space_id="<namespace>/ml-intern-a1b2c3d4"

Replace the bracketed values with real ones before the script leaves your hands: the namespace comes from hf-whoami --brief, the project groups related runs for comparison, and the space id suffix is any 8 characters. TRACKIO_PROJECT and TRACKIO_SPACE_ID env vars work too. Always give the user the dashboard URL: https://huggingface.co/spaces/<trackio_space_id>.

Alerts drive iteration

Use trackio.alert(title, text, level) at every decision point in training. Levels:

  • ERROR: stop and change approach (divergence, NaN, OOM)
  • WARN: tweak hyperparameters (overfitting, early stopping, KL spike, reward collapse, slow convergence)
  • INFO: milestones (training complete, target reached, checkpoint saved)

Always include numeric values and an actionable suggestion in the text, for example "loss=12.4 at step 200, lr likely too high, try x0.1". A future run must be able to parse it and act.

Wire alerts through a custom TrainerCallback passed via callbacks=[...]: on_log for training metrics (loss, reward, kl), on_evaluate for eval metrics (only available there). Keep each condition simple: one metric, one threshold.

Reading alerts back

Read alerts between runs instead of parsing thousands of metric points. CLI, always with --json:

trackio get alerts --project <p> --run <r> --json
trackio get alerts --project <p> --since <iso8601> --json
trackio get run    --project <p> --run <r> --json
trackio get metric --project <p> --run <r> --metric <m> --json
trackio list runs  --project <p> --json

Python: api = trackio.Api(); api.alerts(p, run=r, since=ts); api.runs(p) where each run carries .name, .config, .alerts().

The plugin's job monitor watches job states and failure logs for you; read alerts with the CLI between runs and react to ERROR alerts immediately instead of waiting for the job to finish.

Next config from prior alerts

  • diverged: lr x 0.1
  • overfitting: weight_decay x 10 or reduce capacity
  • early stopping: lr x 0.5 or adjust the schedule
  • high accuracy: refine around the current config

Read the prior config via api.runs(...).config and only mutate keys the alerts justify changing.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.