Menu
Auto-activate when the user mentions runpod or scripts/runpod.py
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Investigate a Helion benchmark dashboard regression (helionlang.com/dashboard) — find the cause and classify it. Auto-activate when the user reports a perf drop/spike on a dashboard platform (e.g. b200 cute) around a given date.
Address CI failures and unresolved review comments on a Helion pull request. Auto-activate when the user mentions a URL like https://github.com/pytorch/helion/pull/<number>.
Context for working on Helion's TPU/Pallas backend. Auto-activate when the user mentions TPU or Pallas in the context of Helion development.
| name | runpod |
| description | Auto-activate when the user mentions runpod or scripts/runpod.py |
python scripts/runpod.py --start when you expect to need remote GPU runs. This avoids paying startup latency on every command.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.python scripts/runpod.py HELION_BACKEND=cute pytest test.python scripts/runpod.py './lint.sh && pytest test'. Do not wrap it in bash -lc; the script handles shell execution itself.python scripts/runpod.py --cleanup so it does not keep billing while idle.