runpod/runpod-plugins-official

runpod-usage

Explain Runpod architecture and design choices: Pods versus Serverless, GPU/VRAM, image construction, storage, networking, and workload development.

Voir la source

Mode d’emploi

  1. Copiez la commande et examinez le paquet avant de l’installer dans votre environnement agent.
  2. Consultez le document original pour les outils, identifiants et environnements requis.
  3. Décrivez les entrées et le livrable souhaité ; comparez la sortie aux sources.
npx skills add https://github.com/runpod/runpod-plugins-official --skill runpod-usage

Avant de commencer

  • L’installation n’inclut ni abonnement au modèle, ni quota API, ni accès aux fichiers.
  • Étoiles et installations reflètent l’activité, pas un test indépendant de qualité ou de sécurité.
Document Skill original

Rendu depuis le dépôt source en conservant titres, exemples, code, tableaux, liens et images.

Runpod usage (concepts)

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), runpod-flash (your own code), or runpod-companion-clis (models/images/data).

This skill explains; the golden paths demonstrate. When the question is really "how do I do X" rather than "how does X work", the verified end-to-end example is the faster answer — runpod/golden-paths/README.md. Read the concept here, then follow the path.

To author files for a custom template, use runpod-build-template; this lane supplies the shared concepts, not a competing packaging workflow.

Read the one reference file that matches the question:

QuestionRead
First-run setup / auth — get + set RUNPOD_API_KEY, SSH, companion credsreference/getting-started.md
Pods vs serverless, workers, cold starts, FlashBoot, queue vs load-balancedreference/concepts.md
The development loop for ANY workload (start here) — plan → prefer prebuilt → provision → verify → teardownreference/development-loop.md
Stand up / iterate a workload on a pod — the pod sub-loopreference/pod-workflows.md
Deploy / iterate a serverless endpoint — Hub vs flash vs custom, invoke + verifyreference/endpoint-workflows.md
Run many requests offline on a queue endpoint — batch jobs: create, finalize, results, limitsreference/batch-jobs.md
Install software on a pod — package hygiene, uv, non-interactive, cachingreference/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) contractreference/building-images.md
Where data lives — container disk vs network volume, model caching, S3 accessreference/storage.md
Which GPU / how much VRAM / which CUDA version / cost & availability / data centersreference/gpu-selection.md
Why a stopped pod may not restart with a GPU — pods are bound to one machine; what else is per machinereference/pods-and-machines.md
Endpoint releases, rolling updates, version overlap, GitHub buildsreference/endpoint-builds-and-releases.md
Storing API tokens and keys as secrets and referencing them from env varsreference/secrets.md
Reaching a pod or endpoint over HTTP (proxy URLs, exposed ports)reference/networking.md
Common mistakes and how to avoid themreference/gotchas.md

Exact facts: the concept files

The reference files explain. For a precise fact, or a rule an action must satisfy, read the concept files in concepts/ next to this file. There is one YAML file per concept (pod.yaml, network-volume.yaml, machine.yaml, …), each with its fields, states, relations and rules, and every rule cites the public source it comes from.

bash
grep -il "volume disk" concepts/*.yaml    # find the concept by name or alias
grep -n "statement:" concepts/pod-volume-disk.yaml
  • rules[].statement is the fact. see: points at related rules on other concepts.
  • A rule with conflict: true records two public sources that disagree. Give both readings.
  • A kind: process file explains a flow step by step. pod-deployment.yaml covers deploy,

stop and restart, including why a restart can fail while the data center has stock.

du même dépôt

Autres Skills

Tous les Skills
runpod
Communauté

runpod

Start here when the Runpod lane is unclear: picks the skill for a task (runpod-mcp and the journey playbooks it routes to, such as runpod-serverless-deploy, runpod-pod-deploy, runpod-pod-doctor and runpod-cost-audit; runpodctl, runpod-flash, runpod-companion-clis, runpod-usage, runpod-templates, runpod-build-template, runpod-migrate, runpod-cloud-migrate) and indexes two dozen end-to-end worked examples (golden paths). Use it before any multi-step or provisioning task, even when the lane is clea

Installations / 1h
3
GitHub Stars
50
Mis à jour
19 nov.
runpod
Communauté

runpod-build-template

Create or improve a complete Runpod template project from an application request, local code, or GitHub repository, with a documented Dockerfile and app-specific files for Pods or queue/load-balanced Serverless. Use runpod-templates for finding or operating existing official templates, runpod-mcp/runpodctl to register an already-built image as a template, runpod-flash for its code-first workflow, and runpod-companion-clis for standalone image build/push commands.

Installations / 1h
3
GitHub Stars
50
Mis à jour
19 nov.
runpod
Communauté

runpod-cloud-migrate

Move a workload from another cloud or GPU platform to Runpod: Vast.ai, Lambda, CoreWeave, Paperspace, Modal, Replicate, Baseten, Together AI, Fireworks AI, fal, Hugging Face Inference Endpoints, AWS, Google Cloud or Azure. Inventories what the project uses, maps it to Runpod, plans, then migrates one workload at a time with verification. To move Runpod code between Runpod API versions, use runpod-migrate instead.

Installations / 1h
3
GitHub Stars
50
Mis à jour
19 nov.
runpod
Communauté

runpod-companion-clis

Companion CLIs for Runpod workflows — HuggingFace, GitHub, Docker, and AWS. Use runpod-build-template for complete template project authoring, and the ComfyUI model-repair guide in runpod-templates for imported workflows lacking model download metadata.

Installations / 1h
3
GitHub Stars
50
Mis à jour
19 nov.