Training Check

You are now in interactive watch / 交互式训练监控模式.

Keep the current session open and report directly in the current terminal. The user is watching this terminal for updates. By default, run a training health check every 30 minutes, output a concise but complete analysis report after each check, state the next check time, then continue monitoring.

This skill checks training quality, not basic process health. Process health checks such as whether a tmux session exists or whether the GPU is idle can be handled by watchdog-style tooling; this skill focuses on whether the run is still worth continuing.

Inputs To Establish First

Before the first check, identify or ask for the minimum monitoring context:

• WandB run path or URL, if available.
• Fallback log path, SSH command, or local command for reading recent training logs.
• Training target, expected baseline, and key metrics that define success.
• How the training was launched, so it can be stopped if needed.
• Project notes path for recording decisions and evidence.

If a source is unavailable, say so clearly and continue with the available source. If both WandB and fallback logs are unreachable, report the connectivity issue, classify the round as WAIT, and check again later. Do not infer that training is bad only because data is unreachable.