Agent skill · software engineering · jeremylongshore
runway-ci-integration
Gate Runway client changes in CI with offline schema fixtures and a separately approved canary lane. Use when preventing API drift without paying on every commit. Trigger with: "test Runway in CI", "Runway contract gate", "Runway canary workflow".
Why this skill is useful
Provides specific implementation patterns and error handling for the Runway AI video generation 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
Non-Billable Runway CI Contract Gate Overview CI should catch client, request-shape, task-state, and storage regressions without generating media on untrusted code. Provider calls belong in a protected, manually approved canary lane with a hard credit ceiling and no fork secrets. Prerequisites A CI system with protected environments and fork-secret isolation Pinned SDK lockfile plus redacted API and task fixtures A documented owner for the optional live canary budget Instructions Step 1: Inventory trust boundaries Inspect workflow triggers, permissions, secret inheritance, dependency installation, artifact retention, and fork behavior. Mark every event on which Runway credentials must be unavailable. Step 2: Build the offline gate Validate request payloads against reviewed per-model fixtures, exercise all task states, verify retry classifications, and prove output is copied to owned storage. Run with network disabled where practical. Step 3: Pin the supply chain Use lockfile-enforced installs, verify the selected SDK package, and fail on unexpected lockfile drift. Do not install an unreviewed latest SDK during CI. Step 4: Protect test evidence Use synthetic prompts and media. Redact bearer values, signed output URLs, raw unsafe prompts, and provider responses before uploading artifacts; set a short artifact retention. Step 5: Isolate the live canary Place it behind a protected environment, manual approval, trusted default-branch commit, explicit model schema, one-request ceiling, and concurrency lock. Never expose its secret to pull requests from forks. Step 6: Publish a decision Report offline contract status separately from live provider status. A skipped canary is not a passing canary, and a created task is not a completed canary. Authentication Ordinary CI receives no Runway credential. The protected canary obtains an organization-scoped key only after environment approval and uses server-side bearer authentication plus the reviewed version header. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/runway-ci-integration