Agent skill · software engineering · jeremylongshore
runway-deploy-integration
Deploy a restart-safe Runway generation service with durable tasks, bounded polling, cancellation, and output ownership. Use when moving an integration to production. Trigger with: "deploy Runway worker", "productionize Runway API", "Runway job architecture".
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 pip:runwayml installed locally. Requires runway account access. About 3k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Deploy an Asynchronous Runway Worker Overview Runway generation does not fit a synchronous request-response handler. Production deployment should accept intent quickly, persist it, execute through bounded workers, reconcile provider task state after restarts, and move successful assets into owned storage. Prerequisites A deployment environment with queues, durable database, and object storage Server-side secrets, egress policy, and reviewed Runway contract Capacity, credit, moderation, retention, and rollback owners Instructions Step 1: Split API from worker Make the public endpoint validate intent, assign an operation ID, persist approval and request fingerprint, enqueue work, and return an internal status handle. Do not hold an HTTP request open for generation. Step 2: Persist provider identity The worker records the provider task ID immediately after create. Retries and restarts must retrieve that task before any new create decision. Step 3: Control capacity Apply per-model concurrency, deadline, priority, and credit guards. Treat provider THROTTLED tasks as already accepted; never resubmit them just because they have not started. Step 4: Reconcile state Run a bounded scheduler that retrieves nonterminal tasks, adds jitter/backoff, handles all terminal states, and can resume after deployment. A local shutdown or timeout does not cancel provider work. Step 5: Own successful assets Download successful output promptly to controlled object storage, verify it, set access and retention, and discard signed provider URLs from normal application records. Step 6: Roll out and roll back Deploy a no-create read probe, one approved canary, then staged traffic. Rollback stops new admission while the old compatible worker drains or cancels existing tasks according to policy. Authentication Workers receive RUNWAYMLAPISECRET from the deployment secret manager and use the reviewed API version. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/runway-deploy-integration