mcpbeat

Autolab Reporter

huggingface/autolab-reporter

Operate the local Trackio reporter for Autolab HF Jobs. Use when a reporter or planner needs to inspect scores, active jobs, worker anomalies, duplicate launches, or the overall experiment board.

405 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
78
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/huggingface/context-course --skill autolab-reporter

The instruction itself

3 sections, as written by the author

Use this for the control-plane view of the experiment fleet.

Workflow

  • Load the local operator env:
  • . ~/.autolab/credentials
  • Sync the latest HF Jobs into Trackio:
  • uv run scripts/trackio_reporter.py sync --project autolab
  • Review the human-readable summary:
  • uv run scripts/trackio_reporter.py summary --max-jobs 25
  • Keep the live dashboard open when monitoring parallel runs:
  • uv run scripts/trackio_reporter.py dashboard --project autolab --mcp-server --no-footer
  • For continuous reporting:
  • uv run scripts/trackio_reporter.py sync --project autolab --watch --interval 300

What To Watch

  • active experiment jobs versus non-experiment jobs
  • duplicate active jobs for the same experiment or hypothesis
  • prepare jobs that still carry experiment labels, which usually indicate

wasted bootstrap work

  • leaderboard entries that actually beat the current local promoted master

Guardrails

  • Treat the reporter as the source of truth for fleet status, not stale shell

output from one worker.

  • If the reporter shows anomalies, fix those before launching more work into

the same queue.

  • Use the reporter to decide whether parallel capacity is real. A slot occupied

by a duplicate or bootstrap job is not useful parallelism.

How to use it

Copy the folder

Take huggingface/autolab-reporter from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.