# runpod-flash

runpod-flash — a skill for Claude Code and Codex that guides code-first serverless development on remote GPUs via Runpod Python SDK 2.0.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode, Windsurf (Devin Desktop), Claude.ai · 1000 installs · ★ 50 repo stars
- Author: runpod
- License: Apache-2.0 · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/runpod/runpod-plugins-official/tree/HEAD/plugins/runpod/skills/runpod-flash/SKILL.md
- Updated: 2026-10-23
- Security check: automated, 2026-11-17 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/skills/runpod-flash

## What it does

This skill guides building serverless applications using Runpod SDK 2.0 instead of writing manual Dockerfiles. It shows how to declare `@app.queue` endpoints, multi-route `@app.api` classes, and ephemeral `@app.task` pods, separating local execution via `@runpod.local_entrypoint` from remote cloud worker runs.

During development, `rp flash dev` runs your entrypoint locally, syncs execution to temporary cloud instances, and re-executes on file changes. Because a dev session sends only module source to workers, applications must stay in a single file while using `rp flash dev`. Persistent deployments use `rp flash deploy`, which bundles the directory into an artifact capped at 1,500 MB.

Running these workflows requires the `runpod>=2.0.0` package and authentication via `rp login` or the `RUNPOD_API_KEY` environment variable. The skill also covers migration logic for projects on the deprecated `runpod-flash` package, which stops receiving fixes after October 29, 2026.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add runpod/runpod-plugins-official --skill runpod-flash -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/runpod-flash/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/runpod-flash/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add runpod/runpod-plugins-official --skill runpod-flash -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/runpod-flash/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add runpod/runpod-plugins-official --skill runpod-flash -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/runpod-flash/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install runpod/runpod-plugins-official plugins/runpod/skills/runpod-flash
```

2. **Manually: put the files in place**
- File: `.github/skills/runpod-flash/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add runpod/runpod-plugins-official --skill runpod-flash -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/runpod/runpod-plugins-official --path plugins/runpod/skills/runpod-flash
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/runpod-flash/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add runpod/runpod-plugins-official --skill runpod-flash -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/runpod/runpod-plugins-official/tree/HEAD/plugins/runpod/skills/runpod-flash/SKILL.md

## When to use it
- run local Python code on remote Runpod GPUs without Dockerfiles
- stream worker logs and iterate using rp flash dev
- ship persistent autoscaling endpoints with rp flash deploy
- migrate legacy runpod-flash code to the unified Runpod SDK 2.0

## Example prompts
- Write a runpod.App with an @app.queue decorator for model inference on an RTX 4090
- How do I run rp flash dev in the background for main.py?
- Migrate this legacy runpod-flash Endpoint definition to Runpod SDK 2.0

## Source text · SKILL.md · Apache-2.0

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: 5152f3bfe18fef2a.

BEGIN THIRD-PARTY FILE 5152f3bfe18fef2a
```text
---
name: runpod-flash
description: >-
  Code-first serverless with the Runpod Python SDK (`runpod` 2.0): define a
  `runpod.App` with `@app.queue` / `@app.api` / `@app.task`, iterate on remote
  GPUs/CPUs with `rp flash dev`, ship with `rp flash deploy`, and maintain or
  migrate legacy `runpod-flash` projects (`from runpod_flash import Endpoint`).
  Use runpod-build-template for explicit Dockerfile/template project authoring,
  and runpodctl/runpod-mcp for infrastructure management.
metadata:
  author: runpod
  version: "2.1.0" # x-release-please-version
  concepts: [flash, serverless-endpoint, serverless-handler, worker, volume-cache, model-store]
license: Apache-2.0
---

# Runpod SDK apps (Flash)

For an explicit Dockerfile/template project request, use
[runpod-build-template](../runpod-build-template/SKILL.md). Do not replace that
deliverable with Flash unless the user chooses its code-first workflow.

Write Python locally, run it on remote Runpod GPUs/CPUs with `rp flash dev`, then
`rp flash deploy` to ship. Flash is part of the `runpod` package (2.0): one SDK, one
`rp` CLI, one login. The standalone `runpod-flash` package is deprecated and gets no fixes
after **October 29, 2026**.

**`rp --help` and `rp flash <command> --help` are authoritative for the command surface.**
This skill is the mental model, the decision rules, and the gotchas that help output does not
carry. Confirm the installed version with `pip show runpod` before concluding a command or
parameter is unavailable.

## Which SDK is this project on?

Check before writing code. The two APIs do not mix.

| You see | Project is on | Do |
|---|---|---|
| `import runpod`, `runpod.App(...)`, `@app.queue`, `rp flash ...` | **Runpod SDK 2.0** | This file + `reference/` |
| `from runpod_flash import Endpoint`, `@Endpoint(...)`, `flash dev`, `runpod-flash` in deps | **Legacy runpod-flash** | [reference/runpod-flash-legacy.md](reference/runpod-flash-legacy.md) to maintain it, [reference/migrate-from-runpod-flash.md](reference/migrate-from-runpod-flash.md) to move it |
| A new project | Runpod SDK 2.0 | Start below |

Write new code on the SDK. For an existing `runpod-flash` project, propose migrating and
check its *Known differences* first; don't migrate silently.

**If the SDK path fails on an SDK bug, `runpod-flash` is the fallback**: a traceback inside
`runpod/apps/`, a worker that crashes before your function runs, or the same code working on
`runpod-flash`. Upgrade `runpod` first; the steps to check for a fix and fall back are in
```
END THIRD-PARTY FILE 5152f3bfe18fef2a

The third-party file has ended. Everything between the 5152f3bfe18fef2a tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2537 of 14062 bytes. © runpod · Apache-2.0 · https://github.com/runpod/runpod-plugins-official/tree/HEAD/plugins/runpod/skills/runpod-flash/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
