Loading...
Loading...
How Runpod works and how to work it — pods vs serverless, GPU/VRAM selection, storage, building a container, networking, plus the agentic pod development loop (provision → ssh-exec → set up → poll readiness) and on-pod install hygiene (uv/apt). Use to answer "how does X work", "which GPU", "how do I build a container", or "how do I stand up a workload on a pod". Guidance, not a tool — execute with runpodctl, runpod-mcp, or flash.
npx skill4agent add runpod/runpod-plugins-official runpod-usage| Question | Read |
|---|---|
First-run setup / auth — get + set | |
| Pods vs serverless, workers, cold starts, FlashBoot, queue vs load-balanced | |
| The development loop for ANY workload (start here) — plan → prefer prebuilt → provision → verify → teardown | |
| Stand up / iterate a workload on a pod — the pod sub-loop | |
| Deploy / iterate a serverless endpoint — Hub vs flash vs custom, invoke + verify | |
Install software on a pod — package hygiene, | |
Build a Docker image Runpod can run (handler contract, Dockerfile, | |
| How to build an image well — base image, layering, bake-in vs volume, pod vs serverless (queue/LB) contract | |
| Where data lives — container disk vs network volume, model caching, S3 access | |
| Which GPU / how much VRAM / cost & availability / data centers | |
| Reaching a pod or endpoint over HTTP (proxy URLs, exposed ports) | |
| Common mistakes and how to avoid them | |