Agent skill · software engineering · jeremylongshore
runway-debug-bundle
Assemble a support-ready Runway failure bundle with task, contract, timing, and media metadata while excluding secrets and signed URLs. Use when escalating a reproducible issue. Trigger with: "Runway debug bundle", "collect Runway evidence", "escalate Runway task".
Why this skill is useful
Provides specific implementation patterns and error handling for Runway's AI video generation 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
Redacted Runway Generation Debug Bundle Overview A useful bundle proves exactly what contract ran and where it failed without redistributing sensitive prompts, customer media, bearer secrets, or temporary output access. Collect metadata and hashes first, then add narrowly approved samples only when support requires them. Prerequisites Internal operation ID or provider task ID Access to redacted application traces and current contract sources An approved destination and retention period for support evidence Instructions Step 1: Freeze identifiers Record environment, organization alias, internal operation ID, task ID, endpoint, model or router config ID, API version, SDK name/version, and UTC timestamps. Step 2: Capture the request contract Store a canonical request hash plus field names, lengths, MIME metadata, dimensions, duration, and source checksums. Omit bearer headers, raw customer media, unsafe prompts, and reachable input URLs. Step 3: Capture state and timing Include create response correlation, PENDING, THROTTLED, RUNNING, and terminal transitions as observed; add local queue, upload, poll, download, and storage timings. Step 4: Capture the failure plane For HTTP failure, include status, safe headers, request ID, and redacted error. For task failure, include failureCode and sanitized diagnostic. For malformed success, include output count and validation errors, not the signed URLs. Step 5: Prove local controls Attach retry attempt bounds, backoff/jitter settings, timeout, cancellation action, duplicate check, selected model schema fingerprint, and relevant fixture result. Step 6: Minimize and share Review every field, replace values with hashes where possible, encrypt the bundle, set access and expiry, and record the recipient and deletion owner. Authentication Task retrieval uses the server-side Runway secret, but the bundle never contains the secret or an authorization header. Temporary input and output URLs are credentials to media and must be redacted. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/runway-debug-bundle--72c9a8