How do I install the Runpod Usage skill?

Run npx skillmds@latest add ariffazil/runpod-usage in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Runpod Usage safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Runpod Usage?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Runpod Usage free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under Apache-2.

Who published Runpod Usage?

ariffazil (@ariffazil) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Runpod Usage by ariffazil — Agent Skill

Name: Runpod Usage
Author: ariffazil

Runpod Usage

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.

ariffazil Updated Sep 21, 2026

File contents

Runpod usage (concepts)

Governance: Irreversible infra ops (deploy/destroy/spend/credential changes) route via arifos-governance; irreversible actions require 888_HOLD release. (F1 AMANAH / F13 SOVEREIGN)

Background knowledge for making the right choice before you act. This skill runs nothing — once you know what to do, execute with runpod-mcp/runpodctl (infra), flash (your own code), or companion-clis (models/images/data).

Read the one reference file that matches the question:

Question	Read
First-run setup / auth — get + set `RUNPOD_API_KEY`, SSH, companion creds	`reference/getting-started.md`
Pods vs serverless, workers, cold starts, FlashBoot, queue vs load-balanced	`reference/concepts.md`
The development loop for ANY workload (start here) — plan → prefer prebuilt → provision → verify → teardown	`reference/development-loop.md`
Stand up / iterate a workload on a pod — the pod sub-loop	`reference/pod-workflows.md`
Deploy / iterate a serverless endpoint — Hub vs flash vs custom, invoke + verify	`reference/endpoint-workflows.md`
Install software on a pod — package hygiene, `uv`, non-interactive, caching	`reference/on-pod-setup.md`
Build a Docker image Runpod can run (handler contract, Dockerfile, `--platform=linux/amd64`)	`reference/docker.md`
How to build an image well — base image, layering, bake-in vs volume, pod vs serverless (queue/LB) contract	`reference/building-images.md`
Where data lives — container disk vs network volume, model caching, S3 access	`reference/storage.md`
Which GPU / how much VRAM / cost & availability / data centers	`reference/gpu-selection.md`
Reaching a pod or endpoint over HTTP (proxy URLs, exposed ports)	`reference/networking.md`
Common mistakes and how to avoid them	`reference/gotchas.md`

---name: runpod-usagedescription: 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.license: Apache-2.0---# Runpod usage (concepts)> **Governance:** Irreversible infra ops (deploy/destroy/spend/credential changes) route via arifos-governance; irreversible actions require 888_HOLD release. (F1 AMANAH / F13 SOVEREIGN)Background knowledge for making the right choice before you act. This skill runsnothing — once you know what to do, execute with **runpod-mcp**/**runpodctl**(infra), **flash** (your own code), or **companion-clis** (models/images/data).Read the one reference file that matches the question:| Question | Read || --- | --- || First-run setup / auth — get + set `RUNPOD_API_KEY`, SSH, companion creds | `reference/getting-started.md` || Pods vs serverless, workers, cold starts, FlashBoot, queue vs load-balanced | `reference/concepts.md` || **The development loop for ANY workload (start here)** — plan → prefer prebuilt → provision → verify → teardown | `reference/development-loop.md` || **Stand up / iterate a workload on a pod** — the pod sub-loop | `reference/pod-workflows.md` || **Deploy / iterate a serverless endpoint** — Hub vs flash vs custom, invoke + verify | `reference/endpoint-workflows.md` || **Install software on a pod** — package hygiene, `uv`, non-interactive, caching | `reference/on-pod-setup.md` || Build a Docker image Runpod can run (handler contract, Dockerfile, `--platform=linux/amd64`) | `reference/docker.md` || **How to build an image well** — base image, layering, bake-in vs volume, pod vs serverless (queue/LB) contract | `reference/building-images.md` || Where data lives — container disk vs network volume, model caching, S3 access | `reference/storage.md` || Which GPU / how much VRAM / cost & availability / data centers | `reference/gpu-selection.md` || Reaching a pod or endpoint over HTTP (proxy URLs, exposed ports) | `reference/networking.md` || Common mistakes and how to avoid them | `reference/gotchas.md` |

Frequently asked questions