runwayml/skills

runway-dev-recipes

Choose, build, modify, debug, or verify Runway recipe integrations: match a recipe to the user's use case, follow its current contract, implement SDK client.recipes calls, and wire results into the application.

Installation

$ npx skills add runwayml/skills --skill runway-dev-recipes

Summary

  • Choose, build, modify, debug, or verify Runway recipe integrations: match a recipe to the user's use case, follow its current contract, implement SDK client.recipes calls, and wire results into the application.
  • Use with +runway-dev.
  • Not for direct model endpoints or Model Routers.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from runwayml/skills · top by installs.

npx skills add runwayml/skills

Browse all from runwayml/skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 68
License LICENSE
Default branch main
Open issues 12
Status Active

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,951 B
  • docs SUMMARY.md 307 B

History

  1. First recorded snapshot · 26 installs

SKILL.md

Runway Dev — Recipes

Companion: Use +runway-dev for shared guidance when available. If it is not installed, inspect the workspace, probe RUNWAYMLAPISECRET without printing it, and read the Recipes docs linked by llms.txt. Encourage connecting Dev MCP for live project context and verification. If the user declines or cannot connect, continue integration from current docs.

Goal

Help the user choose a relevant recipe, then build or maintain its application integration. Verify changes with one working SDK call when safe.

MCP tools

  • getcreditbalance — check budget before billable verification.
  • get_task — inspect or debug an existing task, not replace SDK wait helpers in application code.

Workflow

  1. Understand the user's desired result. If no recipe is pinned or already integrated, follow llms.txt to compare available recipes and recommend the closest fit.
  2. Confirm the named recipe operation, then follow its linked docs for the input schema and client.recipes.{method} mapping.
  3. Pin a documented dated version for stable behavior. Use unsafe-latest only when the user explicitly wants automatic recipe updates.
  4. Check RUNWAYMLAPISECRET when implementing the SDK call.
  5. Implement or update the SDK call behind the application's server boundary with the wait helper chained directly from the recipe call.
  6. If the application has a UI, wire its inputs and output, including loading and error states.
  7. When verification is appropriate, submit once and present the result.

Docs