Agent skill · software engineering · jeremylongshore
runway-install-auth
Install and verify a server-side Runway Dev client without spending generation credits or exposing an organization key. Use when bootstrapping or rotating an integration. Trigger with: "configure Runway API", "install Runway SDK", "verify Runway authentication".
Why this skill is useful
Adds installation scripts and environment configuration for the Runway ML SDK, enabling AI video generation capabilities that the AI wouldn't generate on its own.
What it needs
Requires node, python installed locally. Requires runwayml account access. About 3k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Secure Runway SDK and REST Bootstrap Overview Establish a reproducible client, explicit API-version contract, and non-billable authentication probe. Runway API keys are organization-scoped credentials, so a working client is not evidence that a user should retain access or that a billable generation is approved. Prerequisites Runway Dev organization and an operator authorized to manage API keys Node.js 18+ or Python 3.8+, or an HTTP client for the REST path A secret manager and a reviewed X-Runway-Version value Instructions Step 1: Discover the integration boundary Use Read and Grep to locate runtime manifests, lockfiles, existing Runway clients, environment-variable names, and browser/server boundaries. Separate Runway Dev API access from the consumer Runway web application and from the OAuth-based Runway Dev MCP. Step 2: Resolve and pin the client Choose @runwayml/sdk, runwayml, or direct REST. Query the package registry and official SDK page at implementation time, review the changelog, and pin the selected compatible version in the project lockfile instead of copying a stale version from this skill. Step 3: Provision the key safely Create or rotate a key in the Developer Portal under the intended organization. Store it as RUNWAYMLAPISECRET in the deployment secret manager. Never place it in source, logs, screenshots, browser bundles, MCP configuration, or client-visible environment variables. Step 4: Configure the protocol The official SDKs read RUNWAYMLAPISECRET and supply the version header. For direct HTTP, send Authorization: Bearer <secret> and X-Runway-Version: 2024-11-06 to https://api.dev.runwayml.com; centralize both headers in one server-side client. Step 5: Run a read-only probe Use a documented organization or task read endpoint that the key is authorized to access. Record status, request ID, API version, and organization identity in redacted form. Do not create a generation merely to prove authentication. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/runway-install-auth