Agent skill · software engineering · jeremylongshore
runway-rate-limits
Analyze and control Runway generation concurrency, rolling daily quota, spend limits, and queued tasks without inventing an RPM cap. Use when production traffic is throttled or scaling. Trigger with: "Runway rate limits", "Runway THROTTLED tasks", "Runway concurrency".
Why this skill is useful
Provides specific implementation patterns and error handling for the Runway AI video generation platform that the AI wouldn't reliably generate on its own.
What it needs
Requires 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
Runway Concurrency and Quota Control Overview Runway generation capacity is governed by usage-tier limits, not a universal requests-per-minute number. The application must distinguish accepted-but-queued THROTTLED tasks from create requests rejected with 429, then apply local admission control to protect deadlines and budget. Prerequisites Current organization tier and per-model limit evidence Task creation, state, latency, daily-generation, and credit metrics A durable queue with priority, deadline, and cancellation policy Instructions Step 1: Read live authority Review the organization Usage page and current tiers documentation. Record per-model concurrency, rolling 24-hour generation cap, 30-day spend cap, and any approved enterprise exception. Step 2: Measure by model Count create attempts, accepted task IDs, THROTTLED depth and age, running tasks, terminal states, queue wait, execution time, and rolling daily use per model and organization. Step 3: Set local admission control Use per-model semaphores below the provider concurrency boundary, a global budget guard, priority queues, and customer deadlines. Do not add arbitrary RPM sleeps that hide the actual capacity model. Step 4: Treat THROTTLED correctly Keep the existing task ID and continue bounded observation. Do not create a replacement task; Runway has already stored and queued it. Step 5: Handle 429 correctly Determine whether the rolling daily generation quota or another documented limit was exceeded. Stop new admission, calculate when capacity returns, and retry only within the documented transient policy and operation deadline. Step 6: Tune with evidence Adjust worker concurrency from queue age, terminal throughput, failure rate, and spend—not request count alone. Request an official exception when the documented tiers cannot meet the service objective. Authentication Usage and task reads use the same server-side organization credential as generation. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/runway-rate-limits--1b622e