runapi-sdklisted

# RunAPI SDK selection Use this skill to help an **application developer** pick and wire up RunAPI SDK packages for JavaScript, Python, Ruby, Go, Java, or PHP. Choose from the requested deliverable: a one-off artifact or result uses the RunAPI CLI; an app, backend, worker, library, or production code integration uses an SDK. ## Critical: SDK Integration Runtime When the user is integrating RunAPI into an app, backend, worker, library, Rails service, Node service, Ruby codebase, Go service, webhook pipeline, or production workflow, start here before CLI/API docs. First confirm the target language and current Provider Client package, then inspect the package README or source for install commands, client methods (`create`, `get`, `run`), response shape, and error classes. Never shell out to the `runapi` CLI as the production runtime integration layer. ## When NOT to use this skill Do not use for one-off generation or agent-executed media tasks. If the user just wants an agent to create, edit, transform, or transcribe media once, use the RunAPI CLI skill instead: https://github.com/runapi-ai/cli-skill. Reach for an SDK only when building a web app, backend, worker, library, or production codebase that calls RunAPI from its own code. ## Core SDK vs Provider Client packages - **Core SDK** — shared client primitives (auth, HTTP, polling, errors). Install it transitively via a Provider Client package; depend on it directly only for custom clients. - JavaScript / TypeS