Menu
Resume a paused RunPod pod.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Interactive onboarding for zombuul. Walks through prerequisites, API keys, .env creation, and verifies everything works. Run this after installing the plugin.
End-to-end smoke test of zombuul. Pre-flight, then 3 parallel agents (API, pod list, full pod lifecycle), then a serial e2e step that runs /zombuul:run-experiment on a tiny canned spec to exercise the orchestration + PR flow. Use before publishing a release. Takes ~10–15 minutes and costs roughly $0.10 in RunPod GPU time.
Run an experiment from a spec or description. If given a path to an existing spec, runs it directly. If given a natural language description, synthesizes a spec first, then runs it. Argument $ARGUMENTS — `<spec_path_or_description> [--remote] [--no-pr]`. Pass `--remote` to execute autonomously on a GPU pod (survives local disconnects); otherwise runs local-first. Pass `--no-pr` to skip the draft-PR-on-the-experiment-branch flow.
Finalize an experiment after the main work is done — sync pod results back, run analysis, spawn report review, commit and push. Argument $ARGUMENTS — `<spec_path> [--pod <pod_name>]`. Invoked automatically by `/zombuul:babysit --on-complete` when a long-running job finishes, or directly by you when an experiment doesn't use a babysitter (no pod, no cron).
Spin up a RunPod GPU pod. Argument $ARGUMENTS — optional pod name, optionally followed by `--remote` to install Claude Code + zombuul plugin on the pod (needed when the pod itself will run an agent, not just receive SSH commands).
Pause a RunPod pod: stop GPU billing; keep /workspace only (container disk is wiped on resume).
| name | zombuul:resume-runpod |
| description | Resume a paused RunPod pod. |
| user-invocable | true |
| allowed-tools | Bash, AskUserQuestion |
Resume a previously paused RunPod pod. Waits for SSH to be ready.
List pods: Run ${CLAUDE_PLUGIN_ROOT}/scripts/runpod_ctl.py list. Look for pods with EXITED status (these are paused).
If there are multiple paused pods, ask the user which one to resume using AskUserQuestion.
Resume: Run ${CLAUDE_PLUGIN_ROOT}/scripts/runpod_ctl.py resume <pod_id>.
If no paused pods are found, tell the user.
