run-experiment

Deploy and run ML experiments on local or remote GPU servers.

Updated Apr 18, 2026
One-click install
npx skills add https://github.com/THUFanZd/Sewed_pipeline --skill run-experiment-thufanzd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: run-experiment
Source: https://github.com/THUFanZd/Sewed_pipeline/tree/main/.agents/skills/run-experiment
Command: npx skills add https://github.com/THUFanZd/Sewed_pipeline --skill run-experiment-thufanzd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Deploy and run ML experiments on local or remote GPU environments, unifying setup, execution, and verification to reduce manual orchestration and downtime.

Core Features & Use Cases

  • Environment-driven deployment: Detects whether the target is a local machine or remote server using project metadata (AGENTS.md) to determine the correct workflow.
  • GPU readiness and pre-flight checks: Validates available GPUs, CUDA/driver readiness, and compatibility before launching training.
  • Code synchronization: Syncs code changes (rsync by default or git-based) while avoiding large data transfers.
  • Optional experiment tracking: Supports Weights & Biases integration when enabled in AGENTS.md for metrics logging and experiment reproducibility.
  • Remote deployments with proper isolation: Launches training in dedicated screen sessions with GPU binding and conda environments; supports local execution as well.
  • Post-launch verification and notifications: Verifies the launch and optionally notifies via configured channels (e.g., Feishu) when experiments complete.

Quick Start

Run an ML experiment on the target GPU server using the provided script and arguments.

Frequently Asked Questions about run-experiment

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

FAQPage Schema
How do I deploy and run ML experiments on a remote GPU server?

To run ML experiments on a remote GPU server, this solution orchestrates the deployment by syncing code changes, validating CUDA driver readiness, and launching training jobs in isolated screen sessions with specific GPU binding. It relies on AGENTS.md configuration to determine server paths and conda environments.

Can I use W&B integration for experiment tracking when launching training jobs remotely?

Yes, you can use W&B integration for experiment tracking when launching training jobs remotely. By enabling Weights & Biases in the AGENTS.md configuration, the execution workflow automatically logs metrics and supports experiment reproducibility throughout the remote training process.

Do I need to manually sync code changes to the GPU server before launching training?

You do not need to manually sync code changes to the GPU server before launching training. The deployment workflow automatically synchronizes code changes using rsync by default or git-based methods, specifically avoiding large data transfers to optimize the remote setup process.

How does the system validate GPU readiness before starting ML training execution?

The system validates GPU readiness by performing pre-flight checks that confirm available GPUs, verify CUDA and driver readiness, and ensure compatibility before launching training. This validation prevents execution errors and downtime on the target remote or local server.

What is the best way to run ML experiments on a local machine versus a remote GPU server?

The best way to run ML experiments on either environment is through environment-driven deployment. The system detects whether the target is a local machine or remote server using project metadata in AGENTS.md, automatically applying the correct workflow, GPU binding, and conda environment isolation for each scenario.