exp-status

Checks live status of running experiments and auto-collects completed ones.

Updated Jul 15, 2026
One-click install
npx skills add https://github.com/1549171506/shizhengmubangai1 --skill exp-status-1549171506
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: exp-status
Source: https://github.com/1549171506/shizhengmubangai1/tree/main/Desktop/123/empiricalwiki/i18n/en/skills/exp-status
Command: npx skills add https://github.com/1549171506/shizhengmubangai1 --skill exp-status-1549171506

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Tracking many concurrently running ML experiments across local screen sessions and remote SSH servers is tedious and error-prone; this Skill unifies status checks into a single report and can automatically collect finished experiments and advance the research pipeline. ## Core Features & Use Cases - Unified Status Monitoring: Scans all running experiments, checks local screen sessions or remote servers via SSH, and classifies each as running, anomaly, completed-pending-collect, or collected. - Anomaly Detection: Greps recent logs for NaN, OOM, Traceback, and Inf patterns and surfaces the latest metrics (loss, accuracy, step) in a status table. - Auto-Collect & Pipeline Advance: With --collect-ready it triggers /exp-run --collect for finished experiments; with --pipeline and --auto-advance it advances the research pipeline to Stage 4 once all experiments complete. - Use Case: While running a hyperparameter sweep on a remote GPU server, periodically invoke this Skill (or schedule it via cron) to see which runs are alive, which crashed, and automatically move to the verdict stage when everything finishes. ## Quick Start Ask the assistant to check the status of all running experiments and collect any that have finished.

Frequently Asked Questions about exp-status

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

FAQPage Schema
How do I check the status of running ML experiments?

Run the exp-status skill with no arguments to scan all experiments marked as running in wiki/experiments/. It checks local screen sessions or remote servers via SSH and prints a table classifying each experiment as running, anomaly, completed-pending-collect, or collected.

How to automatically collect completed experiments?

Use the --collect-ready flag, which calls /exp-run --collect for every experiment whose session has ended. Collections run sequentially to avoid concurrent wiki writes, and an updated status report is printed afterward.

Can exp-status monitor experiments on a remote GPU server?

Yes. Experiments with a remote block in their wiki page are checked via python3 tools/remote.py check over SSH, which returns alive status, recent log lines, and detected anomalies. SSH failures mark the experiment as check_failed without stopping other checks.

How does exp-status detect experiment anomalies like NaN loss?

It fetches the last 20 log lines and greps for NaN, OOM, Traceback, and Inf patterns, using the anomalies field from remote.py for remote runs. Detected anomalies are reported in the status table, but fixes require manually running /exp-run --collect.

What happens when all experiments in a pipeline finish?

With --pipeline and --auto-advance, the skill verifies every experiment in stage3a_deployed has status completed, then triggers /research --start-from stage4 to advance the pipeline. If not all are done, it prints progress and waits for the next cron trigger.