train-stack-health

Inspect remote training stack health for conda environments, verl or veomni versions, and one-step smoke tests.

Updated Jun 6, 2026
One-click install
npx skills add https://github.com/Kirrito-k423/AutoResearch --skill train-stack-health-kirrito-k423
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: train-stack-health
Source: https://github.com/Kirrito-k423/AutoResearch/tree/main/.agents/skills/06-train-stack-health
Command: npx skills add https://github.com/Kirrito-k423/AutoResearch --skill train-stack-health-kirrito-k423

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Before running real training jobs on a remote server, you need to know whether the training stack is actually ready: which conda environments exist, which verl or veomni versions are installed, and whether a minimal one-step training run can pass with a decreasing loss. This Skill automates that readiness probe so you avoid wasting time on misconfigured environments. ## Core Features & Use Cases - Environment Inspection: Parses conda env list and pip list output to inventory available training environments and installed packages. - Version Detection: Detects verl or veomni framework versions on the remote server. - One-Step Smoke Test: Runs a minimal 1-step training case and verifies that the step completes and the loss decreases. - Health Table Output: Produces a train stack health summary for readiness review before data collection. - Use Case: Before launching a distributed RLHF experiment on server nvidia-01, run the stack probe to confirm the conda env, verl version, and minimal runner behavior are all healthy. ## Quick Start Run the stack probe against my remote server nvidia-01 using the config at ./config/config.yaml and tell me whether the training stack is healthy.

Frequently Asked Questions about train-stack-health

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

FAQPage Schema
How do I check if a remote training server is ready for verl training?▼

Run the stack probe script with your config file and target server name. It inspects conda environments, detects the installed verl version, and runs a minimal one-step training smoke test to confirm the stack works before real jobs.

How to run a minimal one-step training smoke test for veomni?▼

The probe executes a minimal 1-step training case on the remote server and checks that the step completes and the loss decreases. This validates the runner behavior without launching a full training job.

Does this skill check remote hardware or network speed?▼

No. Hardware inspection belongs to a separate skill (03) and network speed testing to another (04). This skill only covers conda environments, verl or veomni versions, and minimal training smoke tests.

What inputs does the training stack probe require?▼

It requires a YAML config file path and a target server name, passed as arguments to scripts/stack_probe.py. The server must be reachable and have conda plus the training frameworks installed.

Why does the one-step smoke test fail even though conda envs exist?▼

An existing conda environment does not guarantee a working stack. The smoke test can fail due to missing or mismatched verl or veomni versions, broken dependencies, or runner misconfiguration, which the health table helps isolate.