scenario-luma-video
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 traject…
Install / Use
npx skills add scenario-labs/skills --skill scenario-luma-videoInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Development & EngineeringSupported Platforms
Our assessment of scenario-luma-video
scenario-luma-video scores 82/100 on our quality scale, 3395th of 4,698 Development & Engineering skills we index.
Its SKILL.md is 6.1 KB long, split into 7 sections and no code examples: a thorough specification that gives an agent plenty to work with.
With 1,048 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated 29 days ago, so scenario-luma-video is actively maintained.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-11-09. Automated pattern scan on 2026-11-09. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
scenario-luma-video compared with similar skills
All 4 of these similar skills score higher than scenario-luma-video; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| scenario-luma-video (this skill)by scenario-labs | 82 | 1.0k | 29d ago | SKILL.md |
| taste-skillby Leonxlnx | 100 | 116.8k | 8d ago | CLAUDE.md |
| Agent-Reachby Panniantong | 100 | 112.3k | 8d ago | CLAUDE.md |
| rufloby ruvnet | 100 | 81.9k | today | CLAUDE.md |
| headroomby headroomlabs-ai | 100 | 79.8k | today | CLAUDE.md |
Frequently asked questions
- How do I install scenario-luma-video?
- Run
npx skills add scenario-labs/skills --skill scenario-luma-video. The install tabs above show the steps for each supported agent. - Which AI agents does scenario-luma-video work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is scenario-luma-video safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is scenario-luma-video still maintained?
- The repository was last updated 29 days ago, so scenario-luma-video is actively maintained.
Skill content
View source on GitHubname: 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, load it
with skill_get (Scenario MCP) or ask the user to install it
(https://github.com/scenario-labs/skills#install); 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 |
On Ray 3.2 the options veto one another. At authoring time duration was a unit string, "5s" or
"10s", never a number; "10s" refused loop, hdr, startFrame, and endFrame. hdr required
720p or 1080p from the 540p, 720p, 1080p resolution list; six aspectRatio values ran 9:16
through 21:9. Edit and Reframe share that resolution list; Modify Video has no resolution parameter.
duration, resolution, and hdr each move the price (1080p ran several times 720p's cost and
wait), so dry_run the option set before a batch.
Two editors, one strength ladder
Ray 3.2 Edit and Modify Video restyle through the same nine-value ladder, adhere_1 through
reimagine_3 (adhere stays close, flex restyles but keeps recognizable elements, reimagine
transforms), and share little else. Edit names the ladder editStrength; Modify names it mode.
Edit takes a guide image as startFrame; Modify's firstFrame is an edited copy of the source's
own first frame, not an arbitrary style image. Edit alone offers keyframes (up to 64
image-and-index anchors, mutually exclusive with the single startFrame guide), face, pose, depth,
normals, and trajectory conditioning toggles, resolution choice, and hdr; or pass
autoControls: true instead of a manual editStrength. The price gap ran near two orders of
magnitude at authoring time, so dry_run the same clip on both and pay for Edit's controls only
when the edit needs them.
Prompt motion, not adjectives
Ray rewards natural-language prompts of roughly 50 to 300 words built around motion: a subject
mid-action, one named camera move (slow push-in, handheld follow), and one physical consequence of
the action (droplets scattering, dust rising). Concrete lighting language lands directly. With
loop, hold motion intensity constant (steady rain, drifting steam) so the cycle closes cleanly. On
Reframe, prompt only the edges: describe what the new canvas should contain and leave the original
subject alone.
Worked example: a 16:9 hero clip recut for 9:16
searchwithtarget="models",query="luma",public=true. Prefer the newest non-deprecated generation, e.g.model_luma-ray-3-2and its Edit and Reframe siblings (live hits at authoring time: re-discover each session).model_schema_getwith the generator id: options and their vetoes before anything else.upload_assetthe product still (see thescenarioskill) to get an asset id.model_runwith thatmodel_id,dry_run=true, and the exactparameters={"prompt": "A crystal perfume bottle catches soft window light as a single drop arcs off the stopper, slow push-in, product commercial style.", "startFrame": "asset_a", "duration": "5s", "resolution": "1080p", "aspectRatio": "16:9"}; re-estimate after any option change.- Repeat
model_runwithwait=false, thenjobs_waitwith the returned job id, re-called withpending_job_idson timeout, never a secondmodel_run. model_schema_getthe Reframe sibling, thenmodel_runwithparameters={"video": "<generated asset id>", "aspectRatio": "9:16", "prompt": "continue the marble counter downward and the softly lit wall upward", "resolution": "1080p"}, same wait discipline.asset_displayboth and inspect the outpainted edges before delivery.
Common mistakes
duration: 5or"5": Ray 3.2 takes the unit string,"5s"or"10s".- A 10 second loop, HDR grade, or frame anchor:
"10s"excludes all three; drop to"5s". - Ray parameter names on Modify Video: it takes
firstFrameandmode, notstartFrameandeditStrength. editStrengthwithautoControls, orstartFramewithkeyframes: each pair is mutually exclusive on Edit.- Prompting the whole scene on Reframe: the prompt describes only the added canvas; the source subject stays.
- Vibrant, whimsical, or hyper-realistic in a Ray prompt: they degrade quality in this family.
Related Skills
taste-skill
116.8kAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
Agent-Reach
112.3kGive your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu — one CLI, zero API fees.
ruflo
81.9k🌊 The original agent harness. Deploy intelligent multi-player swarms, coordinate autonomous workflows, and build conversational AI systems. Features adaptive memory, self-learning intelligence, federation, vector RAG integration, and native Claude Code / Codex / Hermes and many more Integrated
headroom
79.8kCompress tool outputs, logs, files, and RAG chunks before they reach the LLM. 20% fewer tokens for coding agents, 60-95% fewer tokens for JSON, same answers. Library, proxy, MCP server.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
