runpod-ops

Provision, manage, and terminate RunPod GPU instances for LLM workflows.

1|Updated Nov 12, 2025
One-click install
npx skills add https://github.com/grahama1970/fetcher --skill runpod-ops
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: runpod-ops
Source: https://github.com/grahama1970/fetcher/tree/main/.agents/skills/runpod-ops
Command: npx skills add https://github.com/grahama1970/fetcher --skill runpod-ops

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provision, manage, and terminate RunPod GPU instances for LLM training and inference.

Core Features & Use Cases

  • Auto-provision RunPod GPU pods on demand for model training, evaluation, and inference.
  • Monitor pod status and usage, with lifecycle management including termination.
  • Self-contained, auto-installs via uv; requires RUNPOD_API_KEY for access.

Quick Start

Spin up a GPU pod by running the provided script, then monitor or terminate it when finished.

Frequently Asked Questions about runpod-ops

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate RunPod GPU provisioning for LLM training?

You can automate RunPod GPU provisioning for LLM training by using a self-contained script that requires a RUNPOD_API_KEY to spin up on-demand pods. It auto-installs via uv and exposes commands for creating, monitoring, and terminating instances.

Can I monitor RunPod pod lifecycle and usage during inference?

You can monitor RunPod pod lifecycle and usage during inference using the provided monitor command. It tracks pod status and usage, enabling cost-aware management across your training and inference workflows.

What is needed to manage RunPod instances using this automation approach?

To manage RunPod instances, you need a valid RUNPOD_API_KEY for access and the uv package manager for auto-installation. Once configured, you can provision and terminate GPU pods on demand.

Does this approach work for both LLM training and inference workflows?

This approach works for both LLM training and inference workflows by providing on-demand GPU provisioning and lifecycle management. It covers cost-aware usage across typical RunPod deployments for model training, evaluation, and inference.

What is the best way to handle cost-aware usage of RunPod GPU instances?

The best way to handle cost-aware usage of RunPod GPU instances is to monitor pod status and terminate them when finished. The automation script exposes lifecycle commands to ensure you only pay for active training and inference time.

Why do I need a RUNPOD_API_KEY to provision GPU pods?

You need a RUNPOD_API_KEY to provision GPU pods because it authenticates your requests to the RunPod cloud platform. This access is required to create, manage, and terminate on-demand instances for your LLM workflows.