Agent skill · software engineering · jeremylongshore
runway-common-errors
Diagnose Runway transport errors, queued states, moderation failures, and malformed model requests without duplicate generation. Use when a task or API call fails. Trigger with: "debug Runway error", "Runway task failed", "Runway 429".
Why this skill is useful
Provides specific error handling patterns and SDK usage 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 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 HTTP and Task Failure Triage Overview Runway has two failure planes: synchronous HTTP responses and asynchronous task terminal states. Triage must preserve the task ID, selected model schema, and redacted evidence before deciding whether a retry is safe. Prerequisites Task ID or redacted HTTP response with request correlation Model, endpoint, API version, SDK version, and request fingerprint Access to current HTTP-error and task-failure guidance Instructions Step 1: Identify the failure plane If create returned no task ID, classify the HTTP status. If a task exists, retrieve it and classify THROTTLED, FAILED, CANCELLED, or malformed SUCCEEDED output separately. Step 2: Protect against duplicates Search durable operation and task records before any retry. A client timeout or lost response is not proof that create failed; reconcile by task ID or operation evidence first. Step 3: Handle request errors Treat 400, 401, 404, and 405 as non-retryable until their cause changes. For 400, compare the request against the exact selected model variant instead of editing fields by guesswork. Step 4: Handle transient HTTP errors Retry 429, 502, 503, and 504 only with a bound, exponential backoff, and random jitter up to 50 percent. Respect the operation deadline and credit budget. Step 5: Handle task failures Inspect failureCode. Never retry safety failures automatically; they still consume credits. Internal or preprocessing-internal failures may permit a delayed, bounded retry according to current documentation. Step 6: Close the incident Record the corrected contract or provider recovery, duplicate check, credits at risk, final task state, stored output disposition, and whether a docs or fixture update is required. Authentication Triage reads provider tasks using the server-side organization key. Evidence must redact bearer secrets, unsafe prompt bodies, customer media, and signed output URLs while retaining identifiers and hashes needed for correlation. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/runway-common-errors