training-check

Monitors WandB training metrics periodically to detect NaN, divergence, and idle GPUs.

Updated Jul 9, 2026
One-click install
npx skills add https://github.com/Lingjie-wang/autoRL --skill training-check-lingjie-wang
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: training-check
Source: https://github.com/Lingjie-wang/autoRL/tree/main/Auto-claude-code-research-in-sleep/skills/training-check
Command: npx skills add https://github.com/Lingjie-wang/autoRL --skill training-check-lingjie-wang

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires wandb.

What problem does it solve? Long training runs can silently waste GPU hours when loss diverges, NaN values appear, or metrics plateau, and these problems are often only discovered after training finishes. This Skill performs periodic automated health checks on running training jobs so failures are caught early. ## Core Features & Use Cases - WandB Metric Polling: Reads loss trends, eval metrics, gradient norms, and learning rate schedules from the WandB API, with SSH log-file fallback when WandB is unreachable. - Tiered Judgment: Acts directly on clearly good or clearly bad signals, and escalates only ambiguous cases to a Codex model for a STOP/CONTINUE/WAIT verdict. - Adaptive Check Intervals: Runs via CronCreate starting at 10 minutes, increasing to 20, 30, then 60 minutes when consistently healthy, and resetting after anomalies. - Use Case: After launching a multi-day fine-tuning run, schedule this Skill to poll the WandB run every 10 minutes; it kills the job and logs evidence if loss diverges, saving the remaining GPU budget. ## Quick Start Set up a recurring check for my WandB run entity/project/run_id to monitor training health every 10 minutes.

Frequently Asked Questions about training-check

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

FAQPage Schema
How do I monitor WandB training metrics automatically?

Use the WandB API to fetch run history and check loss trends, eval metrics, NaN values, and gradient norms on a recurring schedule. This Skill polls every 10 minutes initially and increases the interval up to 60 minutes when training stays healthy.

How to detect NaN or loss divergence during model training?

Check the loss history from WandB for NaN or Inf values and whether loss increases over multiple consecutive checkpoints. Clearly bad signals trigger an immediate training stop, while ambiguous trends are escalated to a model judgment call.

What is the difference between training quality checks and process health checks?

Process health checks like watchdog.py verify the session is alive and GPUs are active every 60 seconds. Training quality checks examine whether loss is decreasing and metrics are improving, running every 10 to 60 minutes.

What happens if WandB is unreachable during a training check?

The check falls back to reading the training log directly over SSH by tailing the log file on the server. If both WandB and logs are unreachable, it reports the connectivity issue and retries at the next interval rather than assuming training is broken.

When should I not stop a training run based on metrics?

Do not stop training on a single loss spike, since some spikes are normal. Judge based on trends over multiple checkpoints, and only stop when signals are clearly bad such as persistent NaN or sustained divergence.