Runway Dev Models logo

Runway Dev Models

Organization
runwayml
runway-dev-models

Build, modify, debug, or verify Runway model generation in an application: discover accessible models and constraints with MCP, implement SDK calls, and wire inputs and outputs into the product UI. Use with +runway-dev. Not for Model Routers, Characters, recipes, or agent-side generate scripts.

Overview

Publisherrunwayml
Repositoryskills
Skill namerunway-dev-models
Stars
68
Forks
17
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by runwayml on GitHub. Read the source before you install it.

Installation

Install the Runway Dev Models AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/runwayml/skills.git /tmp/skills
mkdir -p .claude/skills
cp -r /tmp/skills/skills/runway-dev-models .claude/skills/runway-dev-models
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Runway Dev Models in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Runway Dev Models on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Runway Dev Models is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Runway Dev — Models

Companion: Use +runway-dev for shared guidance when available. If it is not installed, inspect the workspace, probe RUNWAYML_API_SECRET without printing it, and read current docs. Encourage connecting Dev MCP for live model access and constraints. If the user declines or cannot connect, continue from current docs and existing model configuration.

Goal

Help the user choose and integrate a model endpoint (/v1/text_to_video, /v1/text_to_image, etc.) across their application, including its backend call and existing UI. Verify changes with one working SDK call when safe.

MCP tools

  • list_models — discover models the selected project can call and read each model's inputConstraints.
  • get_credit_balance — check budget before billable verification.
  • get_task — inspect or debug an existing task, not replace SDK wait helpers in application code.

Workflow

  1. Inspect the existing application. Confirm the user experience, target modality, and where generation inputs and outputs belong.
  2. If the task requires model selection, access verification, or current constraints, call list_models with { projectId, endpoint }. If existing code pins a model, proceed from current docs unless live access must be verified.
  3. Follow the endpoint docs linked by llms.txt; do not infer request fields from another model.
  4. Keep RUNWAYML_API_SECRET behind the application's server boundary.
  5. Implement or update the SDK call by chaining .waitForTaskOutput() in Node or .wait_for_task_output() in Python directly from the create call.
  6. If the application has a UI, wire its controls to the backend and render loading, error, and generated-output states.
  7. When verification is appropriate, submit one test generation. Present the result and offer to persist output before its signed URL expires.

Input media

  • Follow the current input docs linked by llms.txt: use a public HTTPS URL, a small data URI, or an ephemeral upload.
  • Send browser-selected files to the application's server, then use the SDK upload helper and pass its runway:// URI to generation. Local filesystem paths cannot be API inputs.
  • Do not accept arbitrary remote URLs from clients. Prefer uploads or allowlisted origins.
  • Ephemeral inputs and generated output URLs expire; persist anything the application must retain.

Do not

  • Guess model ids, ratios, or durations from memory or other models.
  • Put API keys in frontend bundles.
  • Add manual polling when the SDK wait helper fits, or resubmit on transient read errors.

Docs

Frequently asked questions

What does the Runway Dev Models AI skill do?

Build, modify, debug, or verify Runway model generation in an application: discover accessible models and constraints with MCP, implement SDK calls, and wire inputs and outputs into the product UI. Use with +runway-dev. Not for Model Routers, Characters, recipes, or agent-side generate scripts.

Why use Runway Dev Models on TypingMind?

Because you install it once and use it with any model. Runway Dev Models is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Runway Dev Models in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/runwayml/skills/tree/main/skills/runway-dev-models. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Runway Dev Models?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Runway Dev Models?

As many as you like. As long as a model supports skills, you can use Runway Dev Models with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Runway Dev Models AI skill free?

Yes. It is published on GitHub by runwayml under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇