Agent skill · software engineering · jeremylongshore
runway-prod-checklist
Approve or reject a Runway launch using contract, billing, capacity, moderation, storage, observability, and rollback evidence. Use when preparing go-live. Trigger with: "Runway production checklist", "launch Runway integration", "Runway readiness review".
Why this skill is useful
Provides specific implementation patterns and error handling for the Runway API that the AI wouldn't reliably generate on its own.
What it needs
Requires runwayml 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
Runway Production Readiness Gate Overview Go-live is an evidence gate, not a list of intentions. The release must prove model-aware validation, durable asynchronous state, credit and concurrency controls, moderation handling, owned output storage, secret rotation, observability, and a rollback that does not orphan provider tasks. Prerequisites Release SHA, environment, owner, SLO, budget, and rollback candidate Current first-party API, models, limits, pricing, and go-live guidance Passing contract, security, load, failure, and canary evidence Instructions Step 1: Verify contract and supply chain Pin the reviewed SDK, API version, model or router schemas, and lockfile. Reject retired identifiers such as gen3aturbo and any request shape copied across model variants. Step 2: Verify identity and secrets Confirm organization, roles, key consumers, secret-manager delivery, redaction, rotation owner, and explicit old-key disable procedure. Prove the browser has no provider credential. Step 3: Verify task reliability Prove operation and task ID persistence, restart recovery, all six states, bounded polling, transient retry classes, explicit cancellation, and no duplicate create after ambiguity. Step 4: Verify capacity and billing Record tier, per-model concurrency, rolling daily quota, spend cap, credit balance, autobilling alerts, canary ceiling, and stop conditions. Treat THROTTLED as queued work. Step 5: Verify content and storage Confirm rights, moderation policy, supported input, crop review, failed-safety handling, output validation, owned private storage, URL expiry, retention, and deletion. Step 6: Run and decide Execute one approved canary, trace it through terminal state and storage, test alerts, then rehearse rollback: stop admission, drain or cancel compatible tasks, and preserve reconciliation. Authentication Production keys live only in the secret manager and are scoped operationally through server access controls. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/runway-prod-checklist