scenario-labs/skills

scenario-grok-imagine-video

Use when generating or editing video with Grok Imagine models on Scenario via MCP: text-to-video, image-to-video from a first frame, reference-to-video with @image tags for consistent people, products, or clothing, prompt-based editing, extending a clip fro…

View source

How to use

  1. Copy the installation command and review the source package before installing it in your own agent environment.
  2. Check the source document for required tools, credentials and supported hosts.
  3. Describe your input and desired deliverable; review the output against the source material.
npx skills add https://github.com/scenario-labs/skills --skill scenario-grok-imagine-video

Before you start

  • Installation does not include a model subscription, API allowance or permission to access your files.
  • Repository stars and installation counts describe activity, not an independent quality or security test.
Original skill document

Rendered from the source repository. Headings, examples, code, tables, links, and referenced images are preserved.

Scenario Grok Imagine Video

Overview

Grok Imagine, xAI's video family on Scenario, splits its modes across single-purpose members: text and first-frame generation, reference-to-video, prompt editing, and clip extension each live in their own model, so picking the member is picking the mode. Discover them with search and treat model_schema_get as the contract: members agree on prompt style and disagree on every cap. The Grok Imagine image models belong to the scenario-grok-imagine-image skill.

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

Pick the member by intent (input names from the live schema):

IntentMemberInputs
Text-to-videoVideo 1.5prompt alone; aspectRatio auto lands on 16:9
Animate a stillVideo 1.5image + prompt; auto follows the image ratio
Identity, opening freeVideo 1.5 R2VreferenceImages + prompt tagging @image1
Restyle or swap in placeEdit Videovideo + a prompt naming only the changes
Continue a clipExtend Videovideo + a continuation prompt; duration is new seconds

Caps are per member, so read them off model_schema_get. At authoring time the generation members took 1 to 15 seconds, 1 to 4 numOutputs, and eight aspectRatio values including auto; 1080p existed only on Video 1.5's text and first-frame modes, while R2V stopped at 720p and defaulted to 480p. The earlier unversioned Grok Imagine Video takes the same inputs as Video 1.5, also caps at 720p, and runs cheaper per dry_run. R2V took up to 7 referenceImages; Extend generated 2 to 10 new seconds; Edit exposed no duration or resolution and preprocessed its source down to 8.7 seconds at 720p, so trim to the segment first (see scenario-video). No seed, negative prompt, or camera parameter exists anywhere in the family.

First frame or references

image locks frame one: the video opens on that exact composition and animates out of it. referenceImages (its own member, R2V) carries people, products, and clothing across the shot without deciding how it opens. Tags bind by array order: @image1 is referenceImages[0] (<IMAGE_1> also works), and one clean subject per reference keeps control; a busy reference dilutes it. If the opening must match a composition exactly, render that still and pass it as image; when only a face, product, or outfit must stay consistent, use R2V and tag each reference where it acts.

Sound is prompted, not switched

Generation members produce native audio and no parameter controls it: the prompt is the whole mixing desk. Left unaddressed, the track tends toward generic background music, so end every prompt with named sounds ("Audio: rain on glass, distant traffic") or "no music". Dialogue written in quotes with a delivery verb lip-syncs: She says calmly: "We're live." Structure the rest like a director: scene, camera, style, motion, audio, in present tense, one continuous shot, one dominant camera move, physical actions instead of named emotions. 80 to 150 words touching at least three of those layers beat a one-line scene; editing prompts run shorter, naming only what changes. Extension prompts describe the next beat, not a new scene: open with a bridge ("the shot continues"), keep the established light and cast, and restate the audio.

Worked example: dialogue over an animated hero still

  1. search with target="models", query="grok imagine video", public=true. Match the member by

name: first-frame animation wants e.g. model_xai-grok-imagine-video-1-5 (a live hit at authoring time: re-discover each session).

  1. model_schema_get with that id: fields, caps, and defaults before anything else.
  2. upload_asset the hero still (see the scenario skill) to get its asset id.
  3. model_run with that model_id, dry_run=true, and the exact

parameters={"prompt": "The frame shows a knight on a cliff at dusk. She lowers her sword, turns to the camera, and says quietly: 'It ends tonight.' Slow dolly-in, wind lifting her cloak. Audio: wind, distant thunder, her line clear. No music.", "image": "asset_abc", "duration": 8, "resolution": "1080p"} for the cost estimate; re-estimate after any change to duration, resolution, or numOutputs.

  1. Repeat model_run with wait=false, then jobs_wait with the returned job id, re-called with

pending_job_ids on timeout, never a second model_run.

  1. asset_display the output and watch it with sound: the audio direction is judged by ear.

Common mistakes

  • Leaving audio to the default: generic music appears; direct the sound or state "no music" in every

prompt.

  • Prompting an exact opening frame in R2V: references guide identity, not frame one; pass the still

as image on Video 1.5.

  • Expecting 1080p everywhere: at authoring time it existed only on Video 1.5 text and first-frame

runs, and R2V silently defaults to 480p.

  • Feeding Edit Video a long clip and expecting full-length output: the source is preprocessed down

(8.7 seconds at authoring time); trim to the segment first.

  • Reading Extend's duration as total length: it counts only new footage.
  • Stacking camera moves or contradictory directions ("zoom in as the camera pulls back"): one

dominant move per shot.

from this repository

More skills

All skills
scenario-labs
Community

scenario-blender-expert

Use when doing any 3D work in Blender through Python or an MCP bridge, headless or in a live session: modeling, sculpting a character or head, retopology, UV unwrapping, baking, texturing, rigging, animating, previs, geometry nodes, lighting and rendering, grease pencil, or finishing an AI-generated mesh into a production asset. Also before exporting or handing off an asset, to check it is ready for a game engine, a render or a 3D print (floating parts, z-fighting, inside-out normals, unapplied

1h installs
3
GitHub stars
4K
Updated
Nov 22
scenario-labs
Community

scenario-blender-sculpting

Use when sculpting in Blender through Python: sculpt a head, face or bust, a stylized or cartoon character, a creature or a realistic portrait; block out from primitives; cut planes, a jaw or gonial angle, cheekbones; fix a jaw or face that looks like a ball or balloon; stylized hair clumps; eyelids; an expression or smirk; plan remesh or multires resolution; reproduce Clay Strips, Crease, Draw Sharp, Scrape, Grab or mask moves without a tablet; final clay renders; or when a sculpt operator cras

1h installs
3
GitHub stars
4K
Updated
Nov 22
scenario-labs
Community

scenario-blender-texturing-shading

Use when texturing, shading or look-developing in Blender: building a PBR material from a texture set, displacement, procedural materials, edge wear, dirt, grime, color variation, decals, box or triplanar mapping on meshes without UVs, stylized character skin (subsurface, pores), eyes and cornea, hand-painted stylized textures, texture painting or painting masks headless. Also when a material looks plastic, CG, waxy or blown out, color spaces are wrong, or EEVEE and Cycles disagree.

1h installs
3
GitHub stars
4K
Updated
Nov 22
scenario-labs
Community

scenario

Use when connecting an AI agent to Scenario (scenario.com) through MCP, or when a task involves generating images, video, 3D, audio, sprites, textures, or game assets. Also when picking a Scenario model, running a LoRA, refining a generation prompt, uploading reference images, waiting on generation jobs, checking credits or quota, hitting Scenario auth, scope, or Forbidden errors, or setting up mcp.scenario.com in Claude Code, Cursor, VSCode, or another agent.

1h installs
2
GitHub stars
4K
Updated
Nov 22