Agent skill · software engineering · jeremylongshore
runway-upgrade-migration
Migrate Runway SDK, API, model, or request contracts through inventory, compatibility fixtures, canaries, and reversible rollout. Use when removing retired behavior. Trigger with: "upgrade Runway SDK", "migrate gen3a_turbo", "Runway API migration".
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 python 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 SDK and Model Contract Migration Overview A Runway upgrade can change client types, model availability, allowed fields, output behavior, cost, latency, and quality at once. Preserve operation and task compatibility while migrating from retired identifiers through explicit per-model contracts and controlled comparisons. Prerequisites Current dependency lock, model/request inventory, and task-state schema Target SDK changelog, API reference, models, and pricing evidence Representative fixtures, canary budget, and rollback owner Instructions Step 1: Inventory the current surface Use Read and Grep to find SDK imports, raw endpoints, version headers, model identifiers, ratio and duration literals, wait helpers, error classes, task persistence, output handling, and docs. Step 2: Define the target contract Resolve the target SDK and review its changelog. For model changes, inspect exact input/output variants; gen3aturbo is retired, while gen4.5 and gen4turbo have different input capabilities and cannot be substituted mechanically. Step 3: Build compatibility fixtures Capture accepted request shapes, every task state, HTTP and task failures, cancellation, timeout, and output-copy behavior. Add explicit rejection tests for retired identifiers and cross-model fields. Step 4: Separate code and policy rollout Introduce a client adapter that can read existing task IDs, then deploy target support disabled. Change model or router policy separately so dependency regressions and output-quality changes remain distinguishable. Step 5: Canary both paths Use safe representative prompts/media and fixed ceilings. Compare schema acceptance, queue/run latency, terminal rate, credits, dimensions, duration, moderation, and blinded product quality. Step 6: Migrate and retire Ramp by tenant or workload, keep retrieval compatibility for old tasks, stop new old-contract admission, then remove deprecated code only after the reconciliation horizon. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/runway-upgrade-migration