setup-runpod

Guide RunPod account setup, API key management, GPU selection, and cluster configuration.

5|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/Zayne-sprague/Dr-Claude-Code --skill setup-runpod
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup-runpod
Source: https://github.com/Zayne-sprague/Dr-Claude-Code/tree/main/.claude/skills/setup-runpod
Command: npx skills add https://github.com/Zayne-sprague/Dr-Claude-Code --skill setup-runpod

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill guides users through setting up RunPod as a compute provider for RACA, enabling seamless access to cloud GPUs and easy cluster configuration.

Core Features & Use Cases

  • Phase-based walkthrough: account creation, API key management, GPU options, Pod vs Serverless choice, and known issues.
  • Write cluster entry: automatically generates or updates .raca/clusters.yaml with RunPod settings.
  • Verification and safety: API connectivity check and cost-awareness prompts.

Quick Start

Run the RunPod setup skill and follow the prompts to configure your API key, choose a default GPU, and write the cluster entry to .raca/clusters.yaml.

Frequently Asked Questions about setup-runpod

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

FAQPage Schema
How do I configure RunPod cloud GPUs for RACA workflows?

Setting up RunPod for RACA requires a guided phase-based walkthrough covering account creation, API key management, GPU selection, and cluster configuration. The process writes settings directly to .raca/clusters.yaml and verifies API connectivity.

What is the difference between RunPod Pods and serverless compute for RACA clusters?

RunPod Pods and serverless compute offer different execution models for RACA clusters. The setup process guides users through choosing between persistent Pods for interactive workloads and serverless compute for event-driven tasks, ensuring the chosen option is written to .raca/clusters.yaml.

Do I need an API key to provision RunPod cloud computing resources?

An API key is required to provision RunPod cloud computing resources. The setup workflow guides users through API key generation and management, validates API connectivity, and integrates the key into the .raca/clusters.yaml configuration file for secure access.

How do I write and update the .raca/clusters.yaml file with RunPod settings?

Writing to .raca/clusters.yaml is automated during the RunPod setup process. The workflow generates or updates the cluster entry with your selected GPU type, API key, and compute model, while providing cost-awareness prompts before finalizing the configuration.

Are there known issues or cost considerations when setting up RunPod GPU clusters?

Known issues and cost considerations are addressed during RunPod GPU cluster setup. The workflow includes cost-awareness prompts for cloud computing resources, troubleshooting guidance for known issues, and safety prompts to prevent unexpected billing during Pod or serverless provisioning.

Can I use RunPod for RACA if I need to validate API connectivity before deploying?

Validating API connectivity is a built-in feature of the RunPod setup for RACA. After configuring your API key and writing the .raca/clusters.yaml entry, the workflow performs a connectivity check to ensure your environment can successfully communicate with RunPod cloud computing resources.