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.
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.
Stronger alternatives
This repository is archived — consider an actively maintained alternative.
Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.
Claude CodeNot declared
CursorNot declared
CodexNot declared
GitHub CopilotNot declared
WindsurfNot declared
Gemini CLINot declared
ClineNot declared
OpenCodeNot declared
Repository health
Stars1
LicenseLICENSE
Default branchmain
Status
Archived
Package contents
Files included with this skill beyond the listing page.
skill mdSKILL.md4,814 B
docsSUMMARY.md334 B
History
First seen on skills.sh
First recorded snapshot · 1 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-endpoints 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
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)
Decide whether the workload really needs cluster-level control.
Choose on-demand vs reserved billing based on run duration and baseline utilization.
Choose Kubernetes vs Slurm based on orchestration requirements and team tooling.
Select region, GPU type, driver version, and shared storage plan.
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 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.
Resource Map
Cluster API reference: [references/api-reference.md](references/api-reference.md)