Agent skill · creative production · jeremylongshore
runway-hello-world
Create, observe, and preserve one approved Runway text-to-video task using the current per-model contract. Use when proving the first billable generation path. Trigger with: "Runway hello world", "first Runway video", "smoke test Runway generation".
Why this skill is useful
Adds executable scripts for video generation using Runway's Gen-3 Alpha model that aren't in public docs.
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
One Controlled Runway Generation Overview Prove the minimum asynchronous generation path without pretending that task creation is completion. A Runway generation consumes credits and may be moderated, so the smoke test requires an explicit cost ceiling, safe prompt, terminal-state evidence, and owned output storage. Prerequisites Server-side Runway authentication and available organization credits An operator-approved model, prompt, duration, ratio, and maximum credit budget Durable task storage and an output bucket with retention controls Instructions Step 1: Read the current model schema Open the current models guide and the exact texttovideo model variant in the API reference. Confirm model identifier, required fields, prompt limit, ratio set, duration range, and price immediately before the test. Step 2: Freeze the billable intent Record a unique operation ID, normalized request fingerprint, model, duration, ratio, estimated ceiling, and approval. Use gen4.5 only when its current schema still matches the request; never revive retired gen3aturbo. Step 3: Create one task Submit one server-side request. Persist the returned task ID before waiting. Treat the create response as acceptance into the task system, not a generated asset. Step 4: Wait with a bound Use the SDK wait helper or poll GET /v1/tasks/<task-id> no more frequently than every five seconds with jitter and backoff. Set a deadline. Remember that a client timeout does not cancel the provider task. Step 5: Classify the terminal state Accept output only from SUCCEEDED. For FAILED, retain redacted failureCode and diagnostic text; for CANCELLED, record who cancelled. Treat THROTTLED as queued, not failed. Step 6: Own the output Download successful output promptly, validate type and size, store it under the operation ID, and retain the source URL only as sensitive temporary evidence because Runway output URLs expire. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/runway-hello-world