Runway Dev Workflows

by runwaymle3dffc15498eNo licenseListed Oct 8, 2026Updated Oct 8, 2026

Build, modify, debug, or verify integrations that expose Runway app workflows as API endpoints. Use get_workflows_setup_guide for current setup and API guidance. Use with +runway-dev. Not for model generation, routers, or Characters sessions.

AI-generated overview

Guides building, modifying, debugging, and verifying Runway app workflow integrations exposed as API endpoints.

What it does
This skill provides instructions for connecting Runway app workflows to callable API endpoints. It directs the agent to fetch current setup and API guidance through the get_workflows_setup_guide MCP tool, inspect the existing workflow contract and application integration, then implement, modify, debug, or verify the server-side call. It also covers wiring inputs, invocation state, errors, and outputs into the existing UI or consumer, and running one representative invocation when verification is appropriate.
When to use it
Use it when working on integrations that expose Runway app workflows as API endpoints, including setup, changes, debugging, or verification. It is intended to be used alongside the shared +runway-dev guidance when available. It is not for model generation, routers, or Characters sessions.
Requirements
Requires the Runway Dev MCP tool get_workflows_setup_guide for current setup and API guidance, or fallback inspection of the workspace and current documentation. May need the RUNWAYML_API_SECRET credential, which should be probed without printing it, and network access to Runway documentation. Ships no scripts; instructions only.

Runway Dev — Workflows

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 project-specific setup guidance. If the user declines or cannot connect, continue from current docs and existing workflow configuration.

Goal

Keep the connection between Runway app workflows and callable API endpoints correct.

MCP tools

  • get_workflows_setup_guide — get current setup, connections, help, and API reference links.

Workflow

  1. Call get_workflows_setup_guide with the selected projectId when setup or current project-specific guidance is required. If existing configuration and live docs define the contract, continue implementation without MCP.
  2. When used, follow the returned guide; do not invent workflow publishing steps.
  3. Inspect the existing workflow contract and application integration before changing either.
  4. Implement, modify, debug, or verify the server-side call per the returned API docs. Wire inputs, invocation state, errors, and outputs into the existing UI or consumer.
  5. When verification is appropriate, run one invocation with representative inputs and present the result.

Docs

Source and attribution

Source:runwayml/skillsinskills/runway-dev-workflowsat commite3dffc1

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal