Terminal
Terminal/Skill
Creates one Runpod GPU or CPU pod for development, Jupyter, SSH, or training, after checking stock, and returns its connection URL or SSH command.
By RunPod
Works with
npx skills add runpod/runpod-plugins-official --skill pod-deployYou provision one Pod the user asked for and hand back exactly how to reach it. Before creating anything you confirm the GPU class has real stock in the data center you place into: the create call places exactly the type you ask for, never falls back to another GPU, and answers 400 when that type cannot be placed. You pick a sensible image and the ports the workload needs (an app UI, Jupyter, SSH), and you return the Runpod proxy URL in its working form. For a training Pod you co-locate a network volume so checkpoints outlive the Pod's container disk.
Creating a Pod is billable. State the hourly cost before you create it. Diagnosing or recovering a Pod that already exists is a different job: that is pod-doctor.
Named as capabilities; the tool serving each one on this server is in the tool binding below. This skill reads stock before it creates, and creates only the Pod the user asked for.
discovery).lifecycle-crud).include:["AVAILABILITY"] together with product:["POD"] (the two go together, and stock differs by product) carries the per-data-center picture, so the data center you place into is read, not assumed. If the class has no stock there, say so and offer another class or data center; do not create into an unavailable class.gpu.minCudaVersion at the image's CUDA line (12.8 for a CUDA 12 image; 13.0 only for an image built on CUDA 13), so the Pod lands on a host whose driver supports the image. A template's allowedCudaVersions seeds the floor; an explicit gpu field on the create replaces the seed, and the availability read's cudaVersions says whether that floor has stock.list-pods read) is also a session-read source worth checking when the catalog comes up empty; cite the pod you saw it on. Only when the catalog has no match may you fall back to a well-known public image, and then say so explicitly in the answer. A from-memory image tag is how you get a stale image that crash-loops on boot. Runpod publishes no :latest tags, so pin an exact tag; for GPU work prefer the runpod/pytorch images over runpod/base.8888/http for Jupyter, 22/tcp for direct SSH. SSH also needs startSsh: true at create and a key registered on the account (check get-ssh-keys first); without both the Pod has no SSH access whatever its ports. Only expose what the user needs to reach.runtime.ports stay empty while the container initializes, so poll until they are populated before handing back a URL. App images are large and can take minutes to pull. A slow boot is NOT a failure: never create a second Pod because the first is still pulling. State the proxy URL form (https://<podId>-<port>.proxy.runpod.net) as soon as the Pod id exists. If the app has not bound after the waits your tools can hold, deliver the evidenced status report (pod id, state, last log line) and the recommended next step; offering to keep watching is fine. The reachable form for an HTTP port is the proxy URL https://<podId>-<port>.proxy.runpod.net. For SSH, hand back the Pod's ssh block: ssh.direct (needs 22/tcp; full SSH including scp and rsync) or, on a machine with no public IP, ssh.proxy (interactive shell only). ssh.direct can appear minutes after RUNNING and changes on every stop/start, so say so when it is missing. Confirm the app bound (read the boot log for the "listening on 0.0.0.0:PORT" line) before telling the user it is reachable./workspace by default) survives and bills at the stopped-disk rate until the Pod is terminated; the Pod stays on its machine and resumes there, so if another renter takes that GPU in the meantime a start can be refused for lack of a free GPU on that host, or come back without one; anything on a network volume is unaffected. Tell the user how to resume (start the Pod) and what to do if the GPU is gone: wait and retry, start with zero GPUs to reach the files, or migrate the Pod from the console (pod-doctor covers that).lifecycle-crud; network volumes attach to Secure Cloud Pods only, so the Pod goes to Secure Cloud). Then create the Pod with that volume mounted at a checkpoint path (e.g. /workspace or /checkpoints) and pin the Pod to that data center. Tell the user the mount path and that checkpoints there survive the Pod being stopped or terminated, while container disk does not. Size the volume to the expected checkpoint total with headroom. On a Pod the mount path is the one you set in mounts (no default); a Serverless worker always sees the volume at /runpod-volume. If these checkpoints will later be read by a serverless endpoint, its handler must read them at /runpod-volume, not the pod path.ssh connect string for SSH; never "the link above", and never the boot log's internal 0.0.0.0:<port> address, which is not a reachable URL) with the note that a proxy URL is public and unauthenticated by default (anything sensitive behind it needs its own authentication), the mount path if a volume was attached, and the Pod's state with the hourly cost that is now running. For a stopped Pod, always include the billing consequence with the state: GPU billing ended, the volume disk bills at the stopped rate until the Pod is terminated, and a network volume bills from creation until it is deleted whatever the Pod does.runtime.ports mean it is still initializing, not broken.22/tcp, startSsh) or extra ports the user did not ask for.400 with a placement or stock error → the class ran out in that data center between the read and the create; surface it and offer another class or data center rather than retrying the same one. The same 400 ("no instances available") also answers an invalid GPU type id; check the id against the catalog read before calling it a stock-out.runtime.ports is still empty → it is still initializing; poll get-pod until it is populated before handing back a URL. This is normal Runpod API behavior, not a failure.127.0.0.1 instead of 0.0.0.0; read the boot log to confirm before declaring the Pod broken (deeper diagnosis is pod-doctor).create-network-volume is refused → read the error: the data center may not offer network storage (an empty networkVolumeTypes on the data-center read), the size may be outside 10–4096 GB, or the account balance may be too low; tell the user the exact reason and stop.A good pod hand-back leads with four lines, each filled from a read made this
turn: the Pod (id, state, hourly rate while running); the image (which
template, Hub or pod read it came from); the GPU class with the stock figure
from the availability read; and the reachable URL in its proxy form (or
the ssh connect string for SSH). Then the mount path if a volume was attached, and the
billing consequence of the Pod's current state.
| Capability | Tool |
|---|---|
| GPU stock per data center | list-gpu-types / get-gpu-type (include:["AVAILABILITY"], product:["POD"]) |
| CUDA versions with capacity, per GPU type | the same read (cudaVersions); get-capacity for the matrix view across host CUDA versions |
| Data centers | list-data-centers, get-data-center |
| Create a network volume | create-network-volume |
| Create a Pod | create-pod |
| Inspect a Pod | get-pod |
| List Pods | list-pods |
| Read Pod boot logs | stream-pod-logs |
| Stop a Pod (keep the volume disk) | pod-action ({"action":"stop"}) |
| Resume a stopped Pod | pod-action ({"action":"start"}) |
| Terminate a Pod | delete-pod |
| Account SSH keys | get-ssh-keys / update-ssh-keys |
If a tool named here is missing from the session's tool list, say so and use the nearest read instead of inventing a result.
The cross-journey answer contract (definite facts from reads, commit-don't-hedge, mutations bind to this conversation's creations, a standalone final message, honest failure, granted tools only) is defined in the runpod-mcp skill and applies to every reply from this journey. If the runpod-mcp skill has not been loaded in this conversation, load it now, before the next tool call: its rules on which resources you may change, when a request is the go, and when to stop for the user are not repeated here.