run-experiment

Deploy and launch ML training experiments on local or remote GPU servers.

Updated Apr 1, 2026
One-click install
npx skills add https://github.com/zniihgnexy/vid_tokenizer --skill run-experiment-zniihgnexy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: run-experiment
Source: https://github.com/zniihgnexy/vid_tokenizer/tree/main/.claude/skills/run-experiment
Command: npx skills add https://github.com/zniihgnexy/vid_tokenizer --skill run-experiment-zniihgnexy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Launching ML experiments on GPU machines involves repetitive manual steps: checking GPU availability, syncing code, setting up screen sessions, and verifying processes started correctly. This Skill automates that deployment workflow so experiments launch consistently on the right GPU with logs captured. ## Core Features & Use Cases - Environment Detection: Reads the project's CLAUDE.md to determine whether to run locally (CUDA/MPS) or on a remote server via SSH, including conda environment and code directory settings. - GPU Pre-flight Checks: Queries nvidia-smi (or PyTorch MPS on Mac) to find free GPUs before assigning any job, preventing memory conflicts. - Code Sync & Deployment: Syncs code via rsync or git push/pull, then launches each experiment in a dedicated screen session (remote) or background process (local) with CUDA_VISIBLE_DEVICES binding and tee-based logging. - Use Case: You have three training runs to launch on a remote 4x A100 server. The Skill checks which GPUs are free, rsyncs your Python files, starts three screen sessions each pinned to a different GPU, and reports back the GPU assignments and log file locations. ## Quick Start Ask the AI to run your training experiment on the GPU server, for example by saying run experiment: train the NVRC codec model on the remote server.

Frequently Asked Questions about run-experiment

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

FAQPage Schema
How do I run ML training experiments on a remote GPU server?▼

Configure your server's SSH alias, conda environment, and code directory in the project's CLAUDE.md, then describe the experiment to launch. The Skill checks GPU availability, syncs code via rsync or git, and starts the job in a screen session with GPU binding.

How to check GPU availability before launching a training job?▼

Run nvidia-smi with a CSV query for memory.used and memory.total on the target machine, locally or over SSH. A GPU is considered free when memory.used is below 500 MiB, and the Skill always performs this check before assigning devices.

Can I run experiments locally on a Mac with Apple Silicon?▼

Yes, local execution supports Mac MPS in addition to Linux CUDA. PyTorch uses MPS automatically, and long-running local jobs are launched as background processes so the conversation stays responsive.

Should I use rsync or git to sync code to a remote server?▼

rsync is the default and syncs only Python files, excluding data and checkpoints. Set code_sync to git in CLAUDE.md to push commits locally and pull on the server, which gives version tracking and easier multi-server synchronization.

Why does my remote experiment fail to start after deployment?▼

Common causes include a missing conda activation hook, an occupied GPU, or unsynced code changes. Verify the launch by listing screen sessions over SSH and inspecting the log file created by the tee command.