SkillsAdd

togethercomputer/skills

together-gpu-clusters

On-demand and reserved GPU clusters (H100, H200, B200) on Together AI with Kubernetes or Slurm orchestration, shared storage, credential management, and cluster scaling for ML and HPC jobs.

First seen Mar 31, 2026

Installation

$ npx skills add togethercomputer/skills --skill together-gpu-clusters
View on skills.sh ↗ GitHub repository ↗

Summary

  • On-demand and reserved GPU clusters (H100, H200, B200) on Together AI with Kubernetes or Slurm orchestration, shared storage, credential management, and cluster scaling for ML and HPC jobs.
  • Reach for it when the user needs multi-node compute or infrastructure control rather than a managed model endpoint.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

find-skills Same topic
vercel-labs/skills

Helps users discover and install agent skills when they ask questions like "how do I do X", "fi…

3.3M installs
agent-browser Same topic
vercel-labs/agent-browser

Browser automation CLI for AI agents. Use when the user needs to interact with websites, includ…

810.4K installs
vercel-react-best-practices Same topic
vercel-labs/agent-skills 697.8K installs
web-design-guidelines Same topic
vercel-labs/agent-skills

Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "chec…

617.3K installs
microsoft-foundry Same topic
microsoft/azure-skills

Build, deploy, evaluate, optimize, fine-tune, and manage Microsoft Foundry agents, models, and …

576.5K installs
azure-prepare Same topic
microsoft/azure-skills

Prepare azd-based Azure projects for deployment: generates azure.yaml, infrastructure (Bicep/Te…

568.3K installs

Also in this package

Other skills from togethercomputer/skills · top by installs.

npx skills add togethercomputer/skills
together-chat-completions 93 together-batch-inference 88 together-images 83 together-embeddings 78 together-fine-tuning 77 together-evaluations 76 together-audio 74 together-dedicated-containers 73 together-video 72 together-sandboxes 71

Browse all from togethercomputer/skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 34
License LICENSE
Default branch main
Open issues 0
Status Active

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 6,331 B
  • docs SUMMARY.md 334 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 70 installs

SKILL.md

Together GPU Clusters

Overview

Use Together AI GPU clusters when the user needs infrastructure control instead of a managed inference product.

Typical fits:

  • distributed training
  • multi-node inference
  • HPC or Slurm workloads
  • custom Kubernetes jobs
  • attached shared storage and cluster lifecycle management

When This Skill Wins

  • Provision a cluster and manage it over time
  • Choose between on-demand and reserved capacity
  • Choose Kubernetes or Slurm as the orchestration layer
  • Manage shared volumes and credentials
  • Scale up, scale down, or troubleshoot node health

Hand Off To Another Skill

  • Use together-dedicated-model-inference for managed single-model hosting
  • Use together-dedicated-containers for containerized inference without owning the full cluster
  • Use together-sandboxes for short-lived remote Python execution
  • Use together-fine-tuning for managed training jobs instead of raw cluster operations

Quick Routing

  • Current regions, instance types, pricing, or a non-creating command plan

- Read [references/pricing-and-discovery.md](references/pricing-and-discovery.md) - Query the live regions endpoint, then compare only the matching numeric rates on the official pricing table

  • Cluster creation, scaling, credentials, deletion

- Start with [scripts/managecluster.py](scripts/managecluster.py) or [scripts/managecluster.ts](scripts/managecluster.ts) - Read [references/api-reference.md](references/api-reference.md)

  • Shared storage lifecycle

- Use [scripts/managestorage.py](scripts/managestorage.py) - Read [references/api-reference.md](references/api-reference.md)

  • Kubernetes vs Slurm operations

- Read [references/cluster-management.md](references/cluster-management.md)

  • Troubleshooting node health, PVCs, or scheduling

- Read [references/cluster-management.md](references/cluster-management.md)

  • Together CLI workflows

- Read [references/cli.md](references/cli.md)

Workflow

  1. Decide whether the workload really needs cluster-level control.
  2. Choose on-demand vs reserved billing based on run duration and baseline utilization.
  3. Choose Kubernetes vs Slurm based on orchestration requirements and team tooling.
  4. Select region, GPU type, driver version, and shared storage plan.
  5. Provision first, then layer in access credentials, workload deployment, scaling, and health checks.

High-Signal Rules

  • Python scripts require the Together v2 SDK (together>=2.0.0). If the user is on an older version, they must upgrade first: uv pip install --upgrade "together>=2.0.0".
  • Prefer managed products unless the user explicitly needs raw infrastructure control.
  • Treat storage lifecycle separately from cluster lifecycle; volumes can outlive clusters.
  • When creating a cluster with new shared storage, prefer inline sharedvolume over creating a volume separately and attaching via volumeid. Separately created volumes may land in a different datacenter partition than the cluster, causing a "does not exist in the datacenter" error even when the volume shows as available.
  • GPU stock-outs (409 "Out of stock") are common. Always call list_regions() first and be prepared to try multiple regions.
  • The regions response reports supported configurations, not prices or

guaranteed stock. Never infer the cheapest GPU from response order or hardware generation; open the GPU Cluster pricing table and compare its numeric on-demand rates.

  • GPU clusters have an 8-GPU minimum. For an hourly estimate, multiply the displayed per-GPU-hour rate by at least 8.
  • ON_DEMAND has no one-hour duration flag. For a one-hour plan, omit

--duration-days, create the cluster only when authorized, then delete it after the intended runtime. If the user requests a command without provisioning, print it but do not run it.

  • The API requires cudaversion and nvidiadriverversion as separate fields in addition to the combined driverversion string. Pass them via extra_body in the Python SDK.
  • Credentials retrieval is part of provisioning. Do not stop at cluster creation if the user needs to run workloads immediately.
  • Slurm and Kubernetes operational patterns differ materially; read the cluster-management reference before improvising.
  • For repeated cluster operations, start from the scripts instead of rebuilding request shapes.
  • Slurm startup scripts (worker/login init, worker/controller prolog and epilog, extra slurm.conf) are Slinky v1.0 only. A non-zero exit from a worker prolog or epilog drains the node, and calling Slurm commands (squeue, scontrol, sacctmgr) inside any prolog/epilog can deadlock the scheduler.

Resource Map

  • Cluster API reference: [references/api-reference.md](references/api-reference.md)
  • Operational guide: [references/cluster-management.md](references/cluster-management.md)
  • Operational troubleshooting: [references/cluster-management.md](references/cluster-management.md)
  • CLI guide: [references/cli.md](references/cli.md)
  • Live inventory, pricing, and non-creating plans:

[references/pricing-and-discovery.md](references/pricing-and-discovery.md)

  • Python cluster management: [scripts/managecluster.py](scripts/managecluster.py)
  • TypeScript cluster management: [scripts/managecluster.ts](scripts/managecluster.ts)
  • Python storage management: [scripts/managestorage.py](scripts/managestorage.py)

Official Docs