run-experiment

Launch AI experiments in tmux with conda activation and GPU checks.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/schmidtkk/skills --skill run-experiment-schmidtkk
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: run-experiment
Source: https://github.com/schmidtkk/skills/tree/main/run-experiment
Command: npx skills add https://github.com/schmidtkk/skills --skill run-experiment-schmidtkk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Skill streamlines the end-to-end process of launching AI experiments in tmux with environment setup, GPU checks, and live monitoring, removing manual overhead and guesswork.

Core Features & Use Cases

  • Automates environment preparation (Conda), GPU readiness checks, and session management in tmux.
  • Supports parallel and distributed multi-GPU runs with safe monitoring and early failure detection.
  • Use Case: A researcher wants to launch multiple experiments across GPUs, track training output in real time, and ensure reproducible activation of the right Conda environment.

Quick Start

Describe your conda environment, launch command, and session name, and I will set up a tmux session, activate the environment, and launch the experiment.

Frequently Asked Questions about run-experiment

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

FAQPage Schema
How do I launch AI experiments in tmux with automatic conda activation and GPU checks?

To launch AI experiments in tmux with conda activation and GPU checks, provide your conda environment name, launch command, and session name. The system dynamically detects conda paths, verifies the environment, orchestrates the tmux session, and starts live monitoring automatically.

Can I run multi-GPU training experiments in parallel across separate tmux sessions?

Yes, you can run multi-GPU training experiments in parallel. The system supports distributed multi-GPU launches across single or multiple tmux sessions, applying GPU availability validation and safe monitoring with early failure detection for each experiment.

What's the best way to monitor training output in real time after launching experiments?

The best way to monitor training output in real time is through iterative log monitoring built into the session orchestration. Once your experiment launches in tmux, the system tracks training output continuously, allowing you to watch progress and catch failures early without manual intervention.

Does this approach work with dynamic conda path detection for reproducible environment setup?

Yes, reproducible environment setup relies on dynamic conda path detection. The system automatically locates your conda installation, verifies the target environment exists, and activates it within the tmux session before launching your experiment, ensuring consistent results across runs.

Why do I need to validate GPU availability before launching distributed training workloads?

Validating GPU availability before launching distributed training workloads prevents resource conflicts and early runtime failures. The system checks GPU readiness as part of the launch sequence, ensuring the required hardware is free and available before committing your experiment to a session.

What are the limitations of launching experiments in tmux for research workloads?

The primary limitation for launching experiments in tmux is that it targets research workloads requiring environment setup and GPU validation. It focuses on local or accessible GPU resources via conda and tmux orchestration, meaning it does not natively manage remote cluster schedulers or cloud job queues.