Manages the lifecycle, validation, and execution of HPC and AutoDL research experiments.
Install
mkdir -p .claude/skills/autodl-hpc && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/11059" && unzip -o skill.zip -d .claude/skills/autodl-hpc && rm skill.zipInstalls to .claude/skills/autodl-hpc
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Prepare, validate, and gate AutoDL/HPC research experiments with GitHub deploy-key bootstrap, offline data policy, preflight and smoke gates, FileZilla/SFTP result transfer, and formal-run approval boundaries. Defaults to command preparation over autonomous SSH execution. Use when Codex needs AutoDL, /root/autodl-tmp, remote GPU/HPC smoke tests, preflight_autodl.py, run_autodl_smoke.sh, deploy keys, formal suite gating, or safe download/audit workflows.Key capabilities
- →Bootstrap GitHub deploy keys
- →Validate environments with preflight checks
- →Execute smoke tests
- →Gate formal experiment suites
- →Transfer results via SFTP
How it works
It coordinates research pipelines by validating environments with preflight and smoke gates before allowing formal execution.
Inputs & outputs
When to use autodl-hpc
- →Preparing HPC experiment environments
- →Running smoke tests
- →Gating formal experiment suites
- →Transferring research results
About this skill
SSH GPU/HPC Execution
Capability Routing
This is a first-layer entry skill. Keep it loaded as the user-facing route; when a request needs a specialized capability below, resolve the debuffer repo root from .debuffer_skills/installed-skills-codex.txt (repo_root) when available, read the referenced library SKILL.md, then follow that skill. Do not copy the whole library skill into this file.
/system-profile: read../../skills-codex-library/experiments/system-profile/SKILL.md./training-check: read../../skills-codex-library/experiments/training-check/SKILL.md./run-experiment: read../../skills-codex-library/experiments/run-experiment/SKILL.md./analyze-results: read../../skills-codex-library/experiments/analyze-results/SKILL.md./hpc-formal-run-gate: read../../skills-codex-library/experiments/hpc-formal-run-gate/SKILL.md.
Use this skill for AutoDL or other SSH GPU/HPC machines. Determine the machine type first: AutoDL-managed, shared HPC with a scheduler, or a standalone shared server. Use provider defaults only for the matching type; otherwise use the project contract or SSH alias supplied by the owner.
For an AutoDL-managed instance, read references/autodl-hpc.md. For a
non-AutoDL, shared, non-Slurm, or advisor-provided machine, read
references/shared-hpc-project-contract.md and instantiate
assets/HPC_PROJECT_CONTRACT.template.md in the project. Do not load the AutoDL
provider guide merely because the skill name starts with autodl.
A user- or organization-supplied machine policy overrides provider defaults in
this skill; if two safety rules conflict, apply the stricter rule. For any
nontrivial remote environment setup or rebuild, also read
../shared-references/compute-env-contract.md and use an environment
specification, hash ledger, and smoke witness before declaring the machine ready.
Direct SSH Contract
- AutoDL console commands apply only to AutoDL-managed instances. For another machine, use only the alias, key path, host, port, and user supplied by the owner; never infer them.
- In AutoDL mode only, start from the exact SSH command shown in the console, for example:
ssh -p <PORT> root@connect.<REGION>.seetacloud.com. - All connection and repository examples in this skill are templates. Replace
<PORT>,<REGION>,<project_slug>,<owner>,<private_repo>,<repo_name>, and<branch>only with values supplied for the current machine and repository. Never reuse values from an earlier project or infer missing values. - Treat the host, port, username, and password as session-specific secrets. Never commit them, place the password in a command block, or put the password in a runbook. The user enters a password interactively, or configures an AutoDL public key through the provider console.
- Store the connection as placeholders or an SSH config alias only after the user has created it locally. Do not invent a region, port, host, or alias.
- Use the same approved alias/endpoint for
ssh,scp, and monitoring. Do not silently fall back to an old server alias. Shutdown verification applies only where shutdown is allowed by the machine contract. - The backslash sometimes shown before
@is escaping from a display layer; the shell command isroot@host. - In AutoDL mode, distinguish login credentials from the machine-generated GitHub Deploy Key. Neither should be regenerated merely because an SSH session ended. Reuse the existing key after a normal restart of the same instance and rotate only after destruction, loss, revocation, or an explicit request.
- In AutoDL mode only, route private GitHub setup through the reference's six-step machine-key workflow. For another machine, follow the project contract's server-generated Deploy Key procedure.
Customized Pack Defaults
- Prefer command preparation over direct SSH execution. If the user has not explicitly approved remote execution, output the exact command block using the configured alias or provider endpoint and wait for pasted results.
- Read-only inspection may proceed without a second approval only when the active machine contract explicitly allows it. Environment setup, writes, downloads, smoke runs, and formal execution still require scoped approval.
- Keep local work lightweight: repo edits, tests, lint, config validation, manifest updates, and result audit. Heavy training belongs on AutoDL/HPC.
- Do not implement fully autonomous SSH workflows. SSH remains a manual or explicitly approved boundary. Shutdown is always a separate action.
- Keep runbooks concise. Merge repeated operational notes into the project's
HPC_PROJECT_CONTRACT.mdor one provider runbook instead of generating a new long Markdown file for every attempt. - Read
../shared-references/autosci-lite-patterns.mdfor the pilot gate and negative-memory rules. Formal suites require a passed pilot or an explicit waiver recorded in the runbook.
Workflow
- Classify the current phase: bootstrap, data staging, setup, preflight, smoke, pilot gate, formal approval, formal execution, result download, or local audit.
- Confirm the repo has the expected contracts before remote execution:
docs/runbooks/HPC_PROJECT_CONTRACT.mdor an equivalent machine contract- a project setup command or
scripts/hpc/setup.sh - a machine preflight command or
scripts/hpc/preflight.py - a smoke wrapper or
scripts/hpc/run_smoke.sh scripts/run_experiment_suite.pyscripts/analysis/audit_run_bundles.pyexperiments/suites/smoke.yamldata/DATA_MANIFEST.mdwhen large uploaded data exists- a concise machine runbook or project contract
- Treat target-machine smoke as engineering validation only. Do not present smoke metrics as paper evidence or formal results.
- Prepare a clean local package before touching the remote machine: syntax checks, suite dry-run, manifest generation, job-count inspection, then
git commitandgit push. Do not use the server as a development workspace. - Keep code sync Git-based when possible: commit and push locally, then use the project alias/endpoint to run
git pull --ff-onlyon the server. If GitHub access from the server is unavailable, use narrowly scopedscp/rsynctransfers; never copy a local private key to the server. - Always use the Python/environment path specified by the project contract. Use a placeholder plus the contract path in generic command blocks. The
/root/miniconda3example belongs only to an AutoDL instance that actually has that environment. - Network policy comes from the machine contract.
/etc/network_turboand AutoDL mirrors apply only in AutoDL mode; on another machine use only verified reachable endpoints and approved mirrors. - Run setup, preflight, dry-run, smoke, formal dry-run, and formal manifest generation before any formal execution. If setup changes Python/CUDA/packages/weights, update the compute environment ledger first and rerun the smoke witness.
- Run or review a bounded pilot gate before formal suites. Pilot output stays under
experiments/runs/pilot/...or another raw run path and is not paper evidence. - Require explicit user approval before enabling or running any formal suite. Dry-run formal suites first.
- Launch long formal work only in a detached
screen/tmuxsession, or the contract's process manager, with logs and PID metadata. AutoDL shutdown protocol applies only to an owned AutoDL instance; shared HPC is never shut down unless its owner explicitly requests it. - Download raw run folders back under
experiments/runs/...; do not copy them intoexperiments/results/until local audit and result-to-claim scripts have passed.
Key Rules
- Do not hand-edit server code for formal experiments. Change locally, commit, push, then pull fast-forward on the target machine.
- Do not use AutoDL paths, package environments, network accelerators, or shutdown commands on another machine. Use the active project contract.
- Do not reboot or power off a shared HPC machine unless its owner explicitly requests that exact action.
- Do not use
pkill,killall, broad process-name matching, or terminate a PID whose project, command, and ownership have not been verified. - Do not exceed the machine's account-wide GPU, CPU, RAM, storage, or concurrency budget. Record the selected GPU UUIDs and resource envelope before launch.
- Do not start a long formal run directly from the SSH foreground shell.
- Do not auto-shutdown on failure. AutoDL success-only shutdown applies only in AutoDL mode.
- Do not treat a normal stop/restart of the same instance as key loss.
- In AutoDL mode, do not replace an existing working GitHub Deploy Key without
first checking
/root/.ssh/and the effective SSH configuration. - Do not call shutdown successful because the remote command returned; success requires a subsequent SSH connection attempt to fail.
- Do not automate shutdown verification with a plaintext password or
sshpass. Batch verification requires a preconfigured key or agent. - Do not upload the whole local repository with FileZilla/SFTP, and never sync
.git/. - Do not rely on unapproved runtime downloads. Use the network endpoints and mirrors named in the project contract, and verify revision, size, and hashes.
- Do not write smoke output into
experiments/results/. - Do not treat pilot output as paper evidence; use it only to decide whether formal runs are safe to launch.
- Do not edit a frozen protocol after seeing smoke or formal outputs unless making an explicit protocol revision.
- Stop at a failed gate and report the failed command, artifact path, and required fix.
- If pilot or smoke fails, update
experiments/NEGATIVE_RESULTS.mdwith the run id, artifact path, failure reason, and decision.
Coordination
If the repo needs structural changes before HPC work, use the research-repo architecture conventions first: reusable cod
Content truncated.
When not to use it
- →When the task is local development only
- →When formal approval is not required
Prerequisites
Limitations
- →Requires specific script contracts
- →Not for development workspaces
How it compares
It mandates formal approval gates and smoke testing before running experiments, unlike ad-hoc execution.
Compared to similar skills
autodl-hpc side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| autodl-hpc (this skill) | 0 | 4mo | No flags | Advanced |
| senior-devops | 7 | 11mo | Review | Advanced |
| gitops-workflow | 5 | 5mo | Review | Advanced |
| devops-engineer | 1 | 6mo | Review | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
senior-devops
davila7
Comprehensive DevOps skill for CI/CD, infrastructure automation, containerization, and cloud platforms (AWS, GCP, Azure). Includes pipeline setup, infrastructure as code, deployment automation, and monitoring. Use when setting up pipelines, deploying applications, managing infrastructure, implementing monitoring, or optimizing deployment processes.
gitops-workflow
sickn33
Implement GitOps workflows with ArgoCD and Flux for automated, declarative Kubernetes deployments with continuous reconciliation. Use when implementing GitOps practices, automating Kubernetes deployments, or setting up declarative infrastructure management.
devops-engineer
Jeffallan
Use when setting up CI/CD pipelines, containerizing applications, or managing infrastructure as code. Invoke for pipelines, Docker, Kubernetes, cloud platforms, GitOps.
terraform-specialist
sickn33
Expert Terraform/OpenTofu specialist mastering advanced IaC automation, state management, and enterprise infrastructure patterns. Handles complex module design, multi-cloud deployments, GitOps workflows, policy as code, and CI/CD integration. Covers migration strategies, security best practices, and modern IaC ecosystems. Use PROACTIVELY for advanced IaC, state management, or infrastructure automation.
devops-engineer
I-Synergy
DevOps and CI/CD specialist. Use for building pipelines, containerization, infrastructure as code, or deployment automation. User-invocable only for production deployments.
bazel-build-optimization
wshobson
Optimize Bazel builds for large-scale monorepos. Use when configuring Bazel, implementing remote execution, or optimizing build performance for enterprise codebases.