Skip to content

ericrisco/rsc-harness / skills/runpod

runpod

Verified

Use when running GPU compute on RunPod and deciding between Pods (hourly, always-on) and Serverless (per-second, autoscaling) for training, fine-tuning or inference — serverless endpoints, handler workers, worker Docker templates, network volumes, timeout and worker-count tuning, cold starts, and runaway bills. NOT Python-native serverless GPU with snapshot autoscaling (that is `modal`), NOT calling hosted prebuilt model APIs (that is `replicate`), NOT pulling weights from the Hub (that is `huggingface`).

FileKindSize
SKILL.mdskill md11.1 KB
evals/README.mdmarkdown800 B
evals/cases.yamlconfig3.0 KB
references/cost-and-scaling.mdmarkdown3.3 KB
references/serverless-workers.mdmarkdown3.1 KB
scripts/verify.shexecutablescript5.3 KB

evals/cases.yaml

View on GitHub
skill: runpod

should_trigger:
  - prompt: "Deploy my fine-tuned Llama as a RunPod serverless endpoint with vLLM."
    why: Direct serverless deployment plus the worker-vllm path — core of the skill.
  - prompt: "My RunPod bill exploded this month and the workers never seem to scale down."
    why: Cost / idle-timeout / max-workers symptom with no 'serverless' keyword; the non-obvious cost-control trigger.
  - prompt: "Write me a handler(job) function and start the serverless worker."
    why: Handler authoring — the runpod.serverless.start pattern.
  - prompt: "Necesito entrenar un modelo en una GPU H100 por horas, ¿pod o serverless en RunPod?"
    why: Spanish phrasing of the Pod-vs-Serverless decision plus SKU pick.
  - prompt: "Should I use a network volume or bake the weights into the container image on RunPod?"
    why: Volume-vs-image decision; non-obvious framing of the storage/template tradeoff.
  - prompt: "Cold starts on my endpoint are 20 seconds, how do I make them faster?"
    why: FlashBoot / active-worker tuning; non-obvious, no provider named but RunPod endpoint context.

should_not_trigger:
  - prompt: "Deploy this model with Python-native autoscaling and snapshots, no Dockerfile."
    route_to: modal
    why: Snapshot autoscaling with no container is Modal's niche, not RunPod's image-based workers.
  - prompt: "Call the SDXL endpoint on Replicate and get the image URL back."
    route_to: replicate
    why: Hosted prebuilt model API the user does not self-host — not RunPod GPU rental.
  - prompt: "Download Mistral-7B weights from the Hub and push my fine-tune back."
    route_to: huggingface
    why: Hub artifact transfer, not GPU compute.
  - prompt: "Run Llama 3 locally on my Mac with Ollama."
    route_to: ollama
    why: Local on-device inference, not cloud GPU.
  - prompt: "Containerize my FastAPI service with a multi-stage Dockerfile."
    route_to: docker
    why: Generic containerization unrelated to RunPod's worker image shape.
  - prompt: "Build a cross-provider GPU spend dashboard across AWS, GCP and RunPod."
    route_to: cost-tracking
    why: Provider-agnostic cost attribution, not RunPod-specific knobs.

capability:
  - scenario: "I serve a 7B LLM, about 100k requests/day at ~2s each, bursty during business hours. Set up a cost-efficient RunPod serverless endpoint."
    must_include:
      - Recommends Serverless (flex) over a 24/7 Pod for bursty traffic, with utilization reasoning.
      - Picks a right-sized GPU (e.g. RTX 4090 or L40S), not H100 by default.
      - Sets Max Workers as a bounded cost ceiling (~20% over peak).
      - Sets Idle Timeout and Execution Timeout explicitly rather than leaving defaults.
      - Enables FlashBoot to cut cold-start cost on flex workers.
      - Worker uses runpod.serverless.start and reads job["input"], or uses worker-vllm with MODEL_NAME env var.
      - Reads the API key from RUNPOD_API_KEY env, never hardcoded.
      - Mentions local test (python worker.py --rp_serve_api or test_input.json) before deploying.
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 322kUpdated Claude CodeCodexVerifiedInstall
xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.Stars: 118kUpdated Claude CodeCodexVerifiedInstall