skills/autodl-instance-pro/SKILL.md
Use when managing AutoDL public cloud container instance Pro resources, including creating instances, listing instances, checking status/details, power on/off, release, save images, and list private images through AutoDL Pro API.
npx skillsauth add cyicz123/autodl-elastic-deploy autodl-instance-proInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Use this skill for AutoDL public cloud container instance Pro resources.
https://api.autodl.comAUTODL_PRO_HOSTAUTODL_PRO_TOKEN, then fallback AUTODL_TOKEN, read only from this skill's local .envnode <SKILL_DIR>/autodl-pro.mjs ...Do not reuse Elastic private-cloud host/token variables. AUTODL_ELASTIC_HOST and AUTODL_ELASTIC_TOKEN belong to the sibling elastic deployment skill only.
When the user asks to show commands, review a payload, dry-run, or not execute, do not call AutoDL. The answer must say not executed and no live API call, then include:
node <SKILL_DIR>/autodl-pro.mjs create --json <config.json>https://api.autodl.com, unless AUTODL_PRO_HOST overrides itAUTODL_PRO_TOKEN, fallback AUTODL_TOKENPOST /api/v1/dev/instance/pro/create, POST /api/v1/dev/instance/pro/power_on, or POST /api/v1/dev/instance/pro/image/savenode <SKILL_DIR>/autodl-pro.mjs create --json <config.json>
node <SKILL_DIR>/autodl-pro.mjs snapshot <instance_uuid>
node <SKILL_DIR>/autodl-pro.mjs status <instance_uuid>
node <SKILL_DIR>/autodl-pro.mjs list [--page-index 1] [--page-size 10]
node <SKILL_DIR>/autodl-pro.mjs power-on <instance_uuid> [--start-command "..."]
node <SKILL_DIR>/autodl-pro.mjs power-off <instance_uuid>
node <SKILL_DIR>/autodl-pro.mjs release <instance_uuid>
node <SKILL_DIR>/autodl-pro.mjs save-image <instance_uuid> --name <image_name>
node <SKILL_DIR>/autodl-pro.mjs list-images [--page-index 1] [--page-size 10]
Release is destructive and the CLI does not silently power off first.
node <SKILL_DIR>/autodl-pro.mjs status pro-xxxxxxxx
node <SKILL_DIR>/autodl-pro.mjs power-off pro-xxxxxxxx
node <SKILL_DIR>/autodl-pro.mjs release pro-xxxxxxxx
Power-on calls POST /api/v1/dev/instance/pro/power_on with:
{
"instance_uuid": "pro-xxxxxxxx",
"payload": "gpu",
"start_command": "bash /root/start.sh"
}
payload is always "gpu". Omit start_command only when the user did not provide one.
Save-image calls POST /api/v1/dev/instance/pro/image/save with:
{
"instance_uuid": "pro-xxxxxxxx",
"image_name": "my-saved-image"
}
Required fields:
| Field | Requirement |
|---|---|
| req_gpu_amount | Integer 1 through 4 |
| expand_system_disk_by_gb | Integer 0 through 500 |
| gpu_spec_uuid | GPU spec UUID |
| image_uuid | Base/private image UUID |
| cuda_v_from | Minimum CUDA version value, such as 118 |
Example:
{
"req_gpu_amount": 1,
"expand_system_disk_by_gb": 50,
"gpu_spec_uuid": "GPU-RTX4090",
"image_uuid": "image-xxxxxxxxxx",
"cuda_v_from": 118
}
GPU spec IDs vary by region and account availability. Confirm current IDs with AutoDL before creating paid resources.
| Example GPU | Example spec ID |
|---|---|
| RTX 4090 | GPU-RTX4090 |
| RTX 3090 | GPU-RTX3090 |
| A100 | GPU-A100 |
| H100 | GPU-H100 |
Public base image UUID examples are illustrative; prefer listing private images or using the official console for exact current values.
| Example image | Example UUID |
|---|---|
| PyTorch CUDA 11.8 | image-pytorch-118-example |
| Ubuntu 22.04 CUDA 12.2 | image-ubuntu-122-example |
The CLI prints structured JSON to stdout. On error:
{
"status": "error",
"error_type": "validation_error",
"message": "Pro 创建参数有误",
"details": {
"errors": ["req_gpu_amount(5) 必须是 1 到 4"]
}
}
For token_missing, write AUTODL_PRO_TOKEN in this skill's .env. For validation_error, fix the config used by node <SKILL_DIR>/autodl-pro.mjs create --json <config.json> before retrying; do not submit an invalid paid create request. For release, ask the user to confirm the target instance and power-off state before calling release.
development
Manage AutoDL GPU resources across both clouds and sync local data to containers over SSH. Covers private-cloud elastic deployment (ReplicaSet/Job/Container, scaling, lifecycle, images, GPU stock, events, blacklist), public-cloud container instance Pro (create/snapshot/status/list/power/release/save-image), and rclone-based incremental SSH/SFTP sync of code, weights, and logs. 通过 AutoDL 私有云弹性部署与公有云容器实例 Pro 管理 GPU 容器,并用 rclone 通过 SSH 增量同步代码/权重/日志。当用户提到 AutoDL、弹性部署、公有云实例、GPU 容器调度、私有云部署、增量同步、sync、rclone 时使用。
development
通过 AutoDL 私有云弹性部署 API 批量调度和管理 GPU 容器。支持创建部署(ReplicaSet/Job/Container)、查询容器状态、设置副本数、停止/删除部署等操作。当用户提到 AutoDL、弹性部署、GPU 容器调度、批量创建容器、私有云部署时使用。
development
Maintainer-only workflow for handling GitHub Secret Scanning alerts on OpenClaw. Use when Codex needs to triage, redact, clean up, and resolve secret leakage found in issue comments, issue bodies, PR comments, or other GitHub content.
development
Maintainer workflow for OpenClaw releases, prereleases, changelog release notes, and publish validation. Use when Codex needs to prepare or verify stable or beta release steps, align version naming, assemble release notes, check release auth requirements, or validate publish-time commands and artifacts.