run-experiment

Deploy and run GPU-based ML experiments across local, SSH, Vast.ai, and Modal environments.

Updated Apr 21, 2026
One-click install
npx skills add https://github.com/Shallow-W/llm-wiki --skill run-experiment-shallow-w
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: run-experiment
Source: https://github.com/Shallow-W/llm-wiki/tree/main/.claude/skills/run-experiment
Command: npx skills add https://github.com/Shallow-W/llm-wiki --skill run-experiment-shallow-w

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the friction of launching ML experiments by handling GPU environment detection, code synchronization, dependency setup, job execution, and results/log management across local machines, remote SSH servers, Vast.ai, and Modal.

Core Features & Use Cases

  • Environment-aware deployment: Detects Local/Remote/Vast.ai/Modal from CLAUDE.md, with Vast.ai instance reuse and Modal delegation.
  • GPU pre-flight validation: Checks GPU availability (via nvidia-smi or MPS availability) before launching to avoid wasting cycles.
  • Operational launch workflow: Starts experiments using screen for remote/Vast.ai and background execution for local, while capturing logs with tee.
  • Optional W&B instrumentation: When enabled in CLAUDE.md, it ensures scripts log metrics to Weights & Biases.
  • Optional Vast.ai lifecycle management: Automatically downloads results/logs and destroys the instance when auto_destroy: true to prevent idle billing.

Quick Start

Ask the assistant to run an ML experiment with: run experiment to train my model with the dataset and hyperparameters described above.

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 jobs across local hardware and remote SSH servers?▼

Running ML training jobs across local hardware and remote SSH servers requires coordinating environment detection, code synchronization, GPU pre-flight validation, and job launching via screen for background execution with log capture. This workflow automates that deployment process end-to-end.

How do I deploy GPU experiments to Vast.ai and automatically stop idle billing?▼

Deploying GPU experiments to Vast.ai and stopping idle billing involves launching training jobs with auto_destroy enabled, which automatically downloads results and logs before destroying the instance upon completion to prevent ongoing charges.

Can I run ML experiments on Modal serverless without managing infrastructure?▼

Running ML experiments on Modal serverless without managing infrastructure is supported through direct delegation via the /serverless-modal entry point, handling environment selection and job execution automatically.

How does GPU availability validation work before launching remote training jobs?▼

GPU availability validation before launching remote training jobs works by checking nvidia-smi or MPS availability to ensure GPU resources are present, preventing wasted cycles on environments lacking hardware.

Does this deployment workflow support Weights & Biases logging for ML experiments?▼

Weights & Biases logging for ML experiments is supported optionally, ensuring scripts automatically log metrics to W&B when enabled in the environment configuration for tracking experiment runs.

What is the best way to synchronize code and dependencies before running remote ML experiments?▼

Synchronizing code and dependencies before running remote ML experiments requires detecting the target environment from configuration files, then coordinating code sync, dependency setup, and GPU checks prior to job execution.