# scenario-luma-video

Generates and edits video using Luma Ray models on Scenario via MCP. It routes prompts to the right model for text-to-video, restyling, or outpainting new aspect ratios.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode · 366 installs · ★ 1141
- Author: scenario-labs
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/scenario-labs/skills/tree/HEAD/skills/scenario-luma-video/SKILL.md
- Updated: 2026-10-23
- HTML: https://affpapa.org/en/nevibecode/skills/scenario-luma-video

## What it does

This skill routes video tasks across four distinct Luma models on Scenario via MCP. Ray 3.2 generates clips from text prompts or anchor frames. Ray 3.2 Edit restyles footage while preserving movement using pose, depth, and trajectory controls. Ray 3.2 Reframe outpaces letterboxing by generating new borders rather than cropping the subject. Modify Video handles lighter, budget-friendly prompt edits on clips up to 30 seconds and 100 MB.

Working with this skill requires Scenario MCP tools and the companion `scenario` skill for connection and asset uploads. Model parameters strictly enforce specific restrictions. For instance, duration must be passed as `"5s"` or `"10s"`, and `"10s"` completely rejects looping, HDR, and frame anchors. Both editors share a nine-step transformation ladder from `adhere_1` to `reimagine_3`.

Ray 3.2 Edit ran nearly two orders of magnitude more expensive than Modify Video at authoring time. Because of this massive cost gap, testing parameters with `dry_run=true` on `model_run` is essential before submitting batches. Prompts should focus on physical action and camera movement rather than decorative adjectives.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add scenario-labs/skills --skill scenario-luma-video -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/scenario-luma-video/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/scenario-luma-video/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add scenario-labs/skills --skill scenario-luma-video -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/scenario-luma-video/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add scenario-labs/skills --skill scenario-luma-video -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/scenario-luma-video/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install scenario-labs/skills scenario-luma-video
```

2. **Manually: put the files in place**
- File: `.github/skills/scenario-luma-video/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add scenario-labs/skills --skill scenario-luma-video -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/scenario-labs/skills --path skills/scenario-luma-video
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/scenario-luma-video/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add scenario-labs/skills --skill scenario-luma-video -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/scenario-labs/skills/tree/HEAD/skills/scenario-luma-video/SKILL.md

## When to use it
- generate videos from natural language prompts or anchor frames in Ray 3.2
- restyle existing footage while tracking pose, depth, and motion trajectory
- expand video canvases to new aspect ratios using outpainting without cropping
- apply budget-friendly prompt adjustments to clips under 30 seconds

## Example prompts
- Generate a 5s 16:9 clip with Ray 3.2 using asset_1 as startFrame and a slow push-in camera move
- Reframe this video to 9:16 using Ray 3.2 Reframe, filling the expanded background with soft lighting
- Restyle footage via Ray 3.2 Edit with adhere_2 strength and trajectory tracking enabled

## Source text · SKILL.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: 6784783de0ccff81.

BEGIN THIRD-PARTY FILE 6784783de0ccff81
```text
---
name: scenario-luma-video
description: "Use when generating or editing video with Luma Ray models on Scenario via MCP: cinematic text-to-video, image-to-video from a start frame, start plus end frame anchors, seamless looping clips, HDR output, restyling footage while preserving motion with edit strengths and face, pose, depth, or trajectory controls, reframing to another aspect ratio by outpainting, or budget prompt edits on real footage. Keywords: Luma, Dream Machine, Ray 3.2, Ray 3, Modify Video, Reframe, T2V, I2V, V2V, loop, HDR."
license: MIT
---

# Scenario Luma Video

## Overview

Luma's video line on Scenario is four sibling models, one per mode: Ray 3.2 generates from text or
frame anchors, Ray 3.2 Edit restyles footage under structural controls, Ray 3.2 Reframe outpaints to
a new aspect ratio, and Modify Video makes budget prompt edits. Route by member before tuning
anything; Luma's image models belong to the `scenario-luma-image` skill. Discover the live set with
`search` and treat `model_schema_get` as the contract.

Connection and the core loop: see the `scenario` skill in this repo; model-agnostic video work: the
`scenario-video` skill. If a sibling skill named here is missing from your available skills, ask the
user to install it (`npx skills add scenario-labs/skills --skill <name>`); unattended, proceed from
tool schemas and flag the gap.

## Quick reference

Each mode is its own model (names from the live schemas, caps as of authoring time):

| Member          | Inputs                                | Behavior                                                                 |
| --------------- | ------------------------------------- | ------------------------------------------------------------------------ |
| Ray 3.2         | `prompt` (+ `startFrame`, `endFrame`) | text or image to video; `endFrame` is only valid alongside `startFrame`  |
| Ray 3.2 Edit    | `video` + `prompt`                    | restyles while keeping motion and timing; `editStrength` plus controls   |
| Ray 3.2 Reframe | `video` + `prompt` + `aspectRatio`    | fits a new ratio by outpainting, never cropping; prompt fills the canvas |
| Modify Video    | `video` (+ `prompt`, `firstFrame`)    | budget prompt edits via a `mode` ladder; source up to 30 seconds, 100 MB |
```
END THIRD-PARTY FILE 6784783de0ccff81

The third-party file has ended. Everything between the 6784783de0ccff81 tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2298 of 6227 bytes. © scenario-labs · MIT · https://github.com/scenario-labs/skills/tree/HEAD/skills/scenario-luma-video/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md