check-experiments

Parse tmux session outputs and CSV logs to report ML experiment progress and errors.

2|Updated Apr 12, 2026
One-click install
npx skills add https://github.com/Clay-HHK/claude-config --skill check-experiments
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: check-experiments
Source: https://github.com/Clay-HHK/claude-config/tree/main/skills/check-experiments
Command: npx skills add https://github.com/Clay-HHK/claude-config --skill check-experiments

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Rapidly discover the status, progress, and failures of ML experiments running inside tmux sessions so you can understand resource usage and experiment health without attaching or altering processes.

Core Features & Use Cases

  • Session discovery: Enumerates tmux sessions and reports name, creation time, and attach/detach status.
  • Progress parsing: Extracts epoch/step counts, percentages, loss and metric values, and ETA from recent terminal output.
  • Log inspection & error detection: Reads recent CSV/log rows and scans for common failure patterns like CUDA OOM and Python Tracebacks; ideal for multi-GPU training sweeps, ablation studies, and resumptions.
  • Status reporting: Produces a concise table summarizing status, progress, key metric, and ETA for easy sharing or documentation.

Quick Start

Run a tmux session scan, parse the last outputs and recent CSV logs, and return a concise status report of all experiments.

Frequently Asked Questions about check-experiments

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

FAQPage Schema
How do I monitor ML experiment progress in tmux sessions without attaching?

You can monitor ML experiment progress by collecting tmux session outputs and parsing terminal text for epoch, step, and metric values. This generates a concise status report without attaching to or altering the active sessions.

How do I check for CUDA OOM and Traceback errors across multiple training sweeps?

To check for CUDA OOM and Traceback errors across multiple sweeps, scan recent terminal outputs and log files for specific failure patterns. This detects crashes across multi-GPU training runs and flags them in a status table.

Can I read recent CSV log rows to extract loss and metric values from running experiments?

Yes, you can read recent CSV log rows to extract loss and metric values from running experiments. Parsing the latest CSV entries captures current training metrics and integrates them into a concise status summary.

Does tmux experiment monitoring work for multi-GPU training and ablation studies?

Yes, tmux experiment monitoring works for multi-GPU training and ablation studies by enumerating active sessions and parsing their outputs. It reports progress and detects failures across multiple concurrent runs without interrupting them.

What is the best way to summarize experiment status and ETAs for documentation?

The best way to summarize experiment status and ETAs for documentation is to parse terminal outputs and CSV logs into a structured table. This formatted report includes progress, key metrics, and failure states for easy sharing.