Runpod

pytorch/runpod

Auto-activate when the user mentions runpod or scripts/runpod.py

267 tokens

context cost

the whole folder, loaded on every use

files

instructions only

copies elsewhere

how many repositories repackaged it

915

stars on the repo

on the repository, not the skill itself

Install

one command, takes just this skill from the repository

npx skills add https://github.com/pytorch/helion --skill runpod

found in the instruction text

Bash runs shell commands — read the instruction before connecting

1 sections, as written by the author

Start a persistent pod early with python scripts/runpod.py --start when you expect to need remote GPU runs. This avoids paying startup latency on every command.
Run remote commands with python scripts/runpod.py .... If a matching persistent pod is already running, the script reuses it automatically. If not, it falls back to one-shot start-run-stop behavior.
For normal commands, pass argv directly. Inline env prefixes work too: python scripts/runpod.py HELION_BACKEND=cute pytest test.
For compound shell commands, pass one quoted string: python scripts/runpod.py './lint.sh && pytest test'. Do not wrap it in bash -lc; the script handles shell execution itself.
Before waiting on the user, shut down any persistent pod you started or reused with python scripts/runpod.py --cleanup so it does not keep billing while idle.
If the script warns that a pod was left running, do not ignore it. Clean it up before waiting for user input.

Copy the folder

Take pytorch/runpod from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.