dstack
dstack is an open-source control plane for GPU provisioning and orchestration across GPU clouds, Kubernetes, and on-prem clusters.
Install / Use
npx skills add dstackai/dstack --skill dstackInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
OperationsSupported Platforms
Tags
Our assessment of dstack
dstack scores 94/100 on our quality scale, 133rd of 745 Operations skills we index (top 18%).
Its SKILL.md is 24 KB long, well organised into 56 sections with 19 code examples: a thorough specification that gives an agent plenty to work with.
With 2,259 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so dstack is actively maintained.
- Our last check on 2026-11-16 found the source still online.
- It is released under MPL-2.0, a copyleft license: you can use it, but modified versions you distribute must carry the same license.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
ReviewOur scan of the whole file found 1 pattern worth reviewing before you install dstack. An AI review of the same text found nothing harmful.
- mediumDisables the agent's permission promptsline 99
- When user confirms deletion/stop operations, use `-y` flag to skip confirmation prompts
AI review by kimi-k2.7-code on 2026-09-29. Automated pattern scan on 2026-09-29. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
dstack compared with similar skills
All 4 of these similar skills score higher than dstack; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| dstack (this skill)by dstackai | 94 | 2.3k | 53d ago | SKILL.md |
| x402by browser-use | 100 | 121.0k | 3d ago | SKILL.md |
| algorithmic-artby anthropics | 100 | 177.9k | 55d ago | SKILL.md |
| pptxby anthropics | 100 | 177.9k | 55d ago | SKILL.md |
| designby nextlevelbuilder | 100 | 149.0k | 6d ago | SKILL.md |
Frequently asked questions
- How do I install dstack?
- Run
npx skills add dstackai/dstack --skill dstack. The install tabs above show the steps for each supported agent. - Which AI agents does dstack work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is dstack safe to use?
- Our scan of the whole file found 1 pattern worth reviewing before you install dstack. An AI review of the same text found nothing harmful. It is MPL-2.0-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is dstack still maintained?
- The repository was last updated about 2 months ago, so dstack is actively maintained.
Skill content
View source on GitHubname: dstack description: | dstack is an open-source control plane for GPU provisioning and orchestration across GPU clouds, Kubernetes, and on-prem clusters.
dstack
Overview
dstack provisions and orchestrates workloads across GPU clouds, Kubernetes, and on-prem via fleets.
When to use this skill:
- Running or managing dev environments, tasks, or services on dstack
- Creating, editing, or applying
*.dstack.ymlconfigurations - Managing fleets, volumes, gateways, and checking available offers
How it works
dstack operates through three core components:
dstackserver - Can run locally, remotely, or via dstack Sky (managed)dstackCLI - Applies configurations and manages or inspects fleets, runs, logs, events, volumes, gateways, and offers; it uses project configurations stored in~/.dstack/config.yml, which can be managed withdstack projectdstackconfiguration files - YAML files ending with.dstack.yml
dstack apply shows a plan and submits configuration changes. For run
configurations, it attaches when the run reaches running by default: it
configures SSH access, forwards declared ports, and streams logs. With -d, it
submits and exits.
Quick agent flow (detached runs)
- Show plan:
echo "n" | dstack apply -f <config> - If plan is OK and user confirms, apply detached:
dstack apply -f <config> -y -d - Check the run:
dstack run get <run-name> --json - If dev-environment or task with ports and running: attach to surface IDE link/ports/SSH alias (agent runs attach in background); ask to open link
- If attach fails in sandbox: request escalation; if not approved, ask the user to run
dstack attachlocally and share the output
CRITICAL: Never propose dstack CLI commands or YAML syntaxes that don't exist.
- Only use CLI commands and YAML syntax documented here or verified via
--help - If uncertain about a command or its syntax, check the links or use
--help
NEVER do the following:
- Invent CLI flags not documented here or shown in
--help - Guess YAML property names - verify in configuration reference links
- Run
dstack applyfor runs without-din automated contexts (blocks indefinitely) - Retry failed commands without addressing the underlying error
- Summarize or reformat tabular CLI output - show it as-is
- Use
echo "y" |when-yflag is available - Assume a command succeeded without checking output for errors
Agent execution guidelines
Output accuracy
- NEVER reformat, summarize, or paraphrase CLI output. Display tables, status output, and error messages exactly as returned.
- When showing command results, use code blocks to preserve formatting.
- If output is truncated due to length, indicate this clearly (e.g., "Output truncated. Full output shows X entries.").
Verification before execution
- When uncertain about any CLI flag or YAML property, run
dstack <command> --helpfirst. - Never guess or invent flags. Example verification commands:
dstack --help # List all commands dstack apply -h <configuration type> # Flags for apply per configuration type (dev-environment, task, service, fleet, etc) dstack fleet --help # Fleet subcommands dstack ps --help # Flags for ps - If a command or flag isn't documented, it doesn't exist.
Command timing and confirmation handling
Commands that stream indefinitely in the foreground:
dstack attachdstack applywithout-dfor runsdstack ps -w
Agents should avoid blocking: use -d, timeouts, or background attach. When attach is needed, run it in the background by default (nohup ...), but describe it to the user simply as "attach" unless they ask for a live foreground session.
When waiting programmatically for a specific run, use
dstack run get <run-name> --json and read its top-level status. Run statuses
are pending, submitted, provisioning, running, terminating,
terminated, failed, and done; the last three are terminal. Stop waiting
when the run reaches the state needed for the next action or a terminal status.
Never parse or grep human-readable dstack ps output; its status column may
display a job message such as no offers.
All other commands: Use 10-60s timeout. Most complete within this range. While waiting, monitor the output - it may contain errors, warnings, or prompts requiring attention.
Confirmation handling:
dstack apply,dstack stop,dstack fleet deleterequire confirmation- Use
-yflag to auto-confirm when user has already approved - For
dstack stop, always use-yafter the user confirms to avoid interactive prompts - Use
echo "n" |to previewdstack applyplan without executing (avoidecho "y" |, prefer-y)
Best practices:
- Prefer modifying configuration files over passing parameters to
dstack apply(unless it's an exception) - When user confirms deletion/stop operations, use
-yflag to skip confirmation prompts
Detached run follow-up (after -d)
After submitting a run with -d (dev-environment, task, service), first determine whether submission failed. If the apply output shows errors (validation, no offers, etc.), stop and surface the error.
If the run was submitted, check it with dstack run get <run-name> --json, then guide the user through relevant next steps:
If you need to prompt for next actions, be explicit about the dstack step and command (avoid vague questions). When speaking to the user, refer to the action as "attach" (not "background attach").
- Monitor status: Report the current status and offer to keep watching. If watching, poll
dstack run get <run-name> --jsonevery 10-20 seconds until it reaches the state needed for the next action or a terminal status. - Attach when running: For agents, run attach in the background by default so the session does not block. Use it to capture IDE links/SSH alias or enable port forwarding; when describing the action to the user, just say "attach".
- Dev environments or tasks with ports: Once
running, attach to surface the IDE link/port forwarding/SSH alias, then ask whether to open the IDE link. Never open links without explicit approval. - Services: Prefer using service endpoints. Attach only if the user explicitly needs port forwarding or full log replay.
- Tasks without ports: Default to
dstack logsfor progress; attach only if full log replay is required.
Attaching behavior (blocking vs non-blocking)
dstack attach runs until interrupted and blocks the terminal. Agents must avoid indefinite blocking. If a brief attach is needed, use a timeout to capture initial output (IDE link, SSH alias) and then detach.
Note: dstack attach writes SSH alias info under ~/.dstack/ssh/config (and may update ~/.ssh/config) to enable ssh <run name>, IDE connections, port forwarding, and real-time logs (dstack attach --logs). If the sandbox cannot write there, the alias will not be created.
Permissions guardrail: If dstack attach fails due to sandbox permissions, request permission escalation to run it outside the sandbox. If escalation isn’t approved or attach still fails, ask the user to run dstack attach locally and share the IDE link/SSH alias output.
Background attach (non-blocking default for agents):
nohup dstack attach <run name> --logs > /tmp/<run name>.attach.log 2>&1 & echo $! > /tmp/<run name>.attach.pid
Then read the output:
tail -n 50 /tmp/<run name>.attach.log
Offer live follow only if asked:
tail -f /tmp/<run name>.attach.log
Stop the background attach (preferred):
kill "$(cat /tmp/<run name>.attach.pid)"
If the PID file is missing, fall back to a specific match (avoid killing all attaches):
pkill -f "dstack attach <run name>"
Why this helps: it keeps the attach session alive (including port forwarding) while the agent remains usable. IDE links and SSH instructions appear in the log file -- surface them and ask whether to open the link (open "<link>" on macOS, xdg-open "<link>" on Linux) only after explicit approval.
If background attach fails in the sandbox (permissions writing ~/.dstack or ~/.ssh, timeouts), request escalation to run attach outside the sandbox. If not approved, ask the user to run attach locally and share the IDE link/SSH alias.
Interpreting user requests
"Run something": When the user asks to run a workload (dev environment, task, service), use dstack apply with the appropriate configuration. Note: dstack run only supports dstack run get --json for retrieving run details -- it cannot start workloads.
"Connect to" or "open" a dev environment: If a dev environment is already running, use dstack attach <run name> --logs (agent runs it in the background by default) to surface the IDE URL (cursor://, vscode://, etc.) and SSH alias. If sandboxed attach fails, request escalation or ask the user to run attach locally and share the link.
Multi-node tasks and multi-replica services
Unless you use Multi-node tasks (see ### 2. Tasks) or Multi-replica services (see ### 3. Services), both tasks and services run on a single node. That's why dstack logs <run name>, dstack attach <run name>, and ssh <run name> default to the first replica/job.
- In a multi-node task, each node runs its own job, numbered from 0 in order across node groups. Target a node via
dstack logs <run name> --job 1ordstack attach <run name> --job 1. - In a multi-replica service, replicas are numbered from 0 in order across replica groups. Target a replica via
dstack logs <run name> --replica 1ordstack attach <run name> --replica 1. - Attaching with a non-zero
--jobor--replicacreates the SSH aliasssh <run name>-<job num>-<replica num>.
Configuration types
dstack supports run configurations (dev environments, tasks, and services) and infrastructure configurations (fleets, volumes, and gateways). Configuration files can be named <name>.dstack.yml or simply .dstack.yml.
Common parameters: All run configurations (dev environments, tasks, services) support many parameters including:
- Git integration: Clone repos automatically (
repo) or mount existing repos (repos) - File upload: Upload local files (
files; see concept docs for examples) - Docker support: Use custom Docker images (
image); usedocker: trueif you want to use Docker from inside the container (VM-based backends only) - Environment: Set environment variables (
env), often via.envrc. Secrets are supported but less common. - Storage: Persistent network volumes (
volumes), specify disk size - Resources: Define GPU, CPU, memory, and disk requirements
Best practices:
- Prefer giving configurations a
nameproperty for easier management - When configurations need credentials (API keys, tokens), list only env var names in the
envsection (e.g.,- HF_TOKEN), not values. Recommend storing actual values in a.envrcfile alongside the configuration, applied viasource .envrc && dstack apply. pythonandimageare mutually exclusive in run configurations. Ifimageis set, do not setpython.
files and repos intent policy
Use files and repos only when the user intends to use local/repo files inside the run.
- If user asks to use project code/data/config in the run, then add
filesorreposas appropriate. - If it is totally unclear whether files or repos must be mounted, ask one explicit clarification question or default to not mounting.
files guidance:
- Relative paths are valid and preferred for local project files.
- A relative
filespath is placed under the run'sworking_dir(default or set by user).
repos + image/working directory guidance:
- With non-default Docker images, prefer explicit absolute m
Truncated for display — read the full file on GitHub.
Related Skills
x402
121.0kSet up Browser Use Cloud payments with x402 — pay per request from a crypto wallet (USDC on Base mainnet), no signup or API key.
algorithmic-art
177.9kCreating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems.
pptx
177.9kUse this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an em…
design
149.0kComprehensive design skill: brand identity, design tokens, UI styling, logo generation (55 styles, Gemini, Atlas Cloud, or MuAPI AI), corporate identity program (50 deliverables, CIP mockups), HTML presentations (Chart.js), banner design (22 styles, social/ads/web/print), icon design (15 styles, SVG…
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
