Skip to main content
skill CX Codex

runway-dev-models — Claude Code skill for direct Runway Dev endpoints

runway-dev-models — a skill that walks an agent through adding direct Runway Dev model endpoints to an app. Covers image, video, audio and task handling through the official SDK.

MIT 844 installs ★ 76 updated 2026-10-20

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add runwayml/skills --skill runway-dev-models -a claude-code
Open on GitHub

What runway-dev-models does

The skill starts by looking at the app to see where users hand over inputs and receive outputs. Runway calls stay behind the server boundary, so browser code never touches credentials. When a model is not explicitly chosen, the agent queries list_models from Dev MCP for the relevant project and endpoint instead of guessing IDs.

Before writing any integration code, the skill reads the exact endpoint reference from https://docs.dev.runwayml.com/llms.txt and https://docs.dev.runwayml.com/api.md. Fields, allowed values, inputs and outputs differ between models, so nothing is copied from a neighbouring endpoint. The official SDK for the app's language handles the calls.

Task-creating calls chain waitForTaskOutput() or wait_for_task_output() from the unawaited create() response. Documented task errors are surfaced to the user for inspection or recovery rather than silently resubmitted. Live generation costs money, so the skill runs it only on request and checks the project credit balance right before. RUNWAYML_API_SECRET lives in the server's existing secret mechanism and never lands in MCP configuration.

What it helps with

  • Wire a direct model endpoint into the app's server and user flow
  • Check actual model access for a project without guessing IDs
  • Follow the exact contract of the chosen endpoint
  • Chain task output waiting and surface documented errors
  • Keep the API secret out of browser code and MCP config

Example prompts for the agent

  • Add a direct Runway Dev image generation endpoint to my app
  • List the models this project can actually use via Dev MCP
  • Integrate the official SDK and wire up task output waiting

How to install runway-dev-models

1Skills CLI (Vercel)

npx skills add runwayml/skills --skill runway-dev-models -a claude-code

2Manually: put the files in place

~/.claude/skills/runway-dev-models/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/runway-dev-models/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about runway-dev-models

How do I install runway-dev-models in Claude Code?

Run npx skills add runwayml/skills --skill runway-dev-models -a claude-code. The skill lands in ~/.claude/skills/runway-dev-models/SKILL.md.

What does the runway-dev-models skill do?

It guides the agent through connecting a direct Runway Dev model endpoint to an application: finding the integration point, checking model access, reading the current endpoint docs and using the official SDK.

How is it different from runway-dev-model-routers?

This skill handles direct connections to a specific model. For configured model-agnostic routing, the repository points to runway-dev-model-routers instead.

Source text

SKILL.md · MIT
---
name: runway-dev-models
description: "Use when adding or maintaining a direct Runway Dev model endpoint in an application, including image, video, audio, or task handling. Discover current model access and constraints when needed, follow the exact endpoint contract, and integrate through the official SDK. For configured model-agnostic routing, use runway-dev-model-routers instead."
user-invocable: true
---

# Runway Dev models

Integrate a direct model endpoint into the application's existing server and user flow. Consult `runway-dev` for account setup, credential boundaries, and shared SDK guidance when that skill is installed.

## Workflow

1. Inspect the app and determine where users provide inputs and consume outputs. Keep Runway requests behind the app's server boundary.
2. Honor a model the user or existing app explicitly selected. If a model must be selected or current project access and constraints matter, use Dev MCP's `list_models` for the relevant project and endpoint. Never guess a project ID or infer access from a model name.
   For catalog summaries, preserve each endpoint's returned price units and constraints, and verify model counts against the full response.
3. Read the exact current endpoint reference from `https://docs.dev.runwayml.com/llms.txt` and `https://docs.dev.runwayml.com/api.md`. A model's fields, allowed values, inputs, and outputs can differ from other models; copy no schema from a neighboring endpoint.
4. Use the official SDK for the app's language. For task-creating calls, chain `waitForTaskOutput()` or `wait_for_task_output()` from the unawaited `create()` response. Handle documented task errors and let the user inspect or recover the task rather than silently submitting it again.
5. Wire success, loading, and error states into the existing interface. Treat signed output URLs as temporary; persist media if the application needs it later.
6. Run appropriate local validation. A live generation is billable: perform one only when requested or approved, and check the selected project's credit balance immediately beforehand.

## Inputs and credentials

Follow the current input documentation for HTTPS URLs, data URIs, and upload URIs. For browser-selected files, send the file to the application's server and use the SDK's documented upload flow. Do not pass local filesystem paths to the API or accept arbitrary client-supplied remote URLs without validation.

Keep `RUNWAYML_API_SECRET` on the server in the project's existing secret mechanism. Never expose it to browser code or place it in MCP configuration; Dev MCP uses OAuth separately.

## Current docs

- [Runway Dev agent context](https://docs.dev.runwayml.com/ai-context.md)
- [Models](https://docs.dev.runwayml.com/guides/models/)
- [Inputs](https://docs.dev.runwayml.com/assets/inputs/)
- [Outputs](https://docs.dev.runwayml.com/assets/outputs/)
- [SDK task waiting and errors](https://docs.dev.runwayml.com/api-details/sdks/)

© runwayml · MIT · runwayml/skills

Similar skills

All skills for Agent setup: memory, context, orchestration →

From the same set7

Project sponsors

Companies that keep this analytics open