← Back to list
🎬

gemini-omni Checked

Generate and conversationally edit short videos with Google Gemini Omni Flash (`gemini-omni-flash…
🎬 Video & Motion skills By calesthio Version v1.0.0 Added 2026-09-07 Updated 2026-09-07 Source ↗
8.7Overall rating
2Views
5Downloads
56.5kStars

Installation

🤖 Install via AI

Copy the prompt below and send it to your AI assistant (e.g. Claude Code) — it will follow the instructions and install automatically.

Install the "gemini-omni" skill by following the instructions at https://skill123.me/install/gemini-omni.
⌨️ Command line install

Run in your terminal — downloads and installs to ~/.claude/skills/.

curl -fsSL https://skill123.me/install/gemini-omni.sh | bash
📦 Download ZIP

Download the zip and extract it into your skills directory (e.g. ~/.claude/skills/), then restart your session.

⬇ Download v1.0.0 · 4 KB
📊 Static rating
8.7/10
Trigger
9.0
Structure
8.0
Workflow
7.6
Content
9.0
Engineering
9.0
Security
10.0

Six-dimension rubric with reviewer rationale.

View scorecard ↓
🛡 Dynamic test
—

Not live-tested yet — this skill is rated on static analysis only.

About this skill

Generate and conversationally edit short videos with Google Gemini Omni Flash (gemini-omni-flash-preview). Use when: (1) iterating on a clip with natural-language edits instead of regenerating ("make the phone invisible, keep everything else the same"), (2) generating 3-10s 720p clips with synthesized audio, rendered on-screen text, or timecoded beats, (3) binding reference images to roles with <FIRST_FRAME>/<IMAGE_REF_N> prompt tags, (4) editing an existing uploaded video. Accessed via the gemini_omni_video tool using the project's GEMINI_API_KEY/GOOGLE_API_KEY — the same key as Imagen and Google TTS.

Gemini Omni Flash (Google DeepMind)

Gemini Omni is Google DeepMind's video generation **and editing** model family, announced at I/O 2026. The first model, **Gemini Omni Flash** (gemini-omni-flash-preview, developer access since June 30, 2026), generates 3-10 second clips at 720p/24fps with synthesized audio via the Gemini **Interactions API**. Its differentiator in the OpenMontage fleet is **stateful conversational editing**: each generation returns an interaction_id, and a follow-up call with previous_interaction_id edits that video in place — no other wrapped provider can refine a clip without regenerating it.

OpenMontage wraps it as gemini_omni_video (native Gemini API, no gateway). It shares GOOGLE_API_KEY/GEMINI_API_KEY with google_imagen and google_tts — one key, three capabilities. Paid tier only: ~$0.10 per second of output video (billed as 5,792 output tokens/sec at $17.50/1M).

Other documented routes are available when the direct Google key is not the

chosen provider:

| Route | OpenMontage call | Important limitation |

|-------|------------------|----------------------|

| fal.ai | gemini_omni_fal | T2V, I2V, reference video, and edit endpoints; no Google interaction ID is returned |

| Runway | runway_video, model: "gemini_omni_flash" | T2V/I2V/V2V; video edits accept up to five image references |

| ComfyUI Partner Node | comfyui_video, model_family: "gemini_omni_flash" | Hosted paid node; requires network, Comfy login, and credits |

Use the direct gemini_omni_video route for stateful conversational editing.

Gateway routes return ordinary provider tasks and cannot preserve Google's

previous_interaction_id workflow. The fal edit endpoint can still be iterated

by feeding each output video URL into the next edit call.

Documentation

Generate and conversationally edit short videos with Google Gemini Omni Flash (gemini-omni-flash-preview). Use when: (1) iterating on a clip with natural-language edits instead of regenerating ("make the phone invisible, keep everything else the same"), (2) generating 3-10s 720p clips with synthesized audio, rendered on-screen text, or timecoded beats, (3) binding reference images to roles with <FIRST_FRAME>/<IMAGE_REF_N> prompt tags, (4) editing an existing uploaded video. Accessed via the gemini_omni_video tool using the project's GEMINI_API_KEY/GOOGLE_API_KEY — the same key as Imagen and Google TTS.

Gemini Omni Flash (Google DeepMind)

Gemini Omni is Google DeepMind's video generation **and editing** model family, announced at I/O 2026. The first model, **Gemini Omni Flash** (gemini-omni-flash-preview, developer access since June 30, 2026), generates 3-10 second clips at 720p/24fps with synthesized audio via the Gemini **Interactions API**. Its differentiator in the OpenMontage fleet is **stateful conversational editing**: each generation returns an interaction_id, and a follow-up call with previous_interaction_id edits that video in place — no other wrapped provider can refine a clip without regenerating it.

OpenMontage wraps it as gemini_omni_video (native Gemini API, no gateway). It shares GOOGLE_API_KEY/GEMINI_API_KEY with google_imagen and google_tts — one key, three capabilities. Paid tier only: ~$0.10 per second of output video (billed as 5,792 output tokens/sec at $17.50/1M).

Other documented routes are available when the direct Google key is not the

chosen provider:

| Route | OpenMontage call | Important limitation |

|-------|------------------|----------------------|

| fal.ai | gemini_omni_fal | T2V, I2V, reference video, and edit endpoints; no Google interaction ID is returned |

| Runway | runway_video, model: "gemini_omni_flash" | T2V/I2V/V2V; video edits accept up to five image references |

| ComfyUI Partner Node | comfyui_video, model_family: "gemini_omni_flash" | Hosted paid node; requires network, Comfy login, and credits |

Use the direct gemini_omni_video route for stateful conversational editing.

Gateway routes return ordinary provider tasks and cannot preserve Google's

previous_interaction_id workflow. The fal edit endpoint can still be iterated

by feeding each output video URL into the next edit call.

When to pick it (and when not)

View full documentation

| Use it for | Prefer another provider for |

|---|---|

| Iterative refinement — generate, review, then edit the same clip in layers | One-shot cinematic hero clips (→ Seedance 2.0, see seedance-2-0) |

| Editing an existing/uploaded clip (restyle, add/remove objects, change text) | Clips longer than 10s or above 720p |

| On-screen rendered text and word-by-word text beats | Seed-reproducible generations (no seed support) |

| Reference-image-bound subjects/styles via prompt tags | First/last-frame interpolation (→ veo_video) |

| Timecode-scheduled multi-beat clips from one prompt | Non-English narration (English only fully supported) |

Route through video_selector for generation operations. **Editing (edit_video) is a direct-tool operation** — call gemini_omni_video from the registry, because the multi-turn interaction state lives outside the selector's model.

Generation prompting

Describe **scene + camera + lighting + motion + audio**. Official example:

> Continuous, unbroken handheld shot of a fluffy tabby cat sitting on a sunny windowsill, looking out into a leafy garden. The cat's tail twitches slowly, and its ears rotate slightly toward ambient noises. Sunbeams illuminate dust motes in the air.

  • **Force a single shot** explicitly: "In a single continuous shot," / "No scene cuts." Otherwise the model may cut between scenes.
  • **Negatives go in prose** — there is no negative_prompt parameter: "No dialogue," "No extra sound effects."
  • **No sampler controls**: system instructions, temperature, top_p, and seeds are all unsupported. The prompt is the only lever.
  • **Meta-prompt for quality**: "Consider micro-detail, expression and timing to create a very rich, detailed but entirely natural scene."

### Timecode syntax

Schedule beats with bracketed ranges or natural language — this maps directly onto OpenMontage scene-plan timings:


[0-3s] A person is walking [3-6s] They stop and turn around

> "After 3 seconds, a woman enters the scene." / "At 5s the chorus starts in the background audio."

### Audio and on-screen text

Audio is synthesized automatically; direct it in the prompt: "Include calm background music," "The audio is a low tinny radio broadcast in the background." Rendered text works and can be timed:

> One word on the screen at a time: 'did, you, know, that, Omni, can, do, awesome, text?' Each word appears for 1s.

Reference images (`<FIRST_FRAME>` / `<IMAGE_REF_N>` tags)

Pass local images via reference_image_paths (they are sent in order), then bind them to roles **inside the prompt** with tags. <IMAGE_REF_N> indexes from 0 in the order supplied:


in the style of <IMAGE_REF_0> a woman <IMAGE_REF_1> is walking

[0-3s] A studio fashion sequence. Starting with woman <IMAGE_REF_0>, she is
holding <IMAGE_REF_1> [3-6s] Then we see the man <IMAGE_REF_2> holding <IMAGE_REF_3>
  • <FIRST_FRAME> makes an image the opening frame: <FIRST_FRAME> a woman is walking.
  • Use high-resolution images; describe the intended motion specifically rather than "make it move."
  • Say what each image *is* (product / character / style / background reference) — the model decides usage from context.

Conversational editing (the differentiator)

**Editing prompts are the opposite of generation prompts: short and surgical.** Overly descriptive edit prompts cause unintended changes.

1. Generate the base clip (subject + scene + motion). The tool returns interaction_id in its result data.

2. Pass it back as previous_interaction_id with operation="edit_video" and describe **only the delta**.

3. Append **"Keep everything else the same."** to pin unmentioned elements.

4. Refine in layers — one turn for lighting, one for camera, one for action, one for audio.

Official good/bad pairs:

| Avoid | Instead |

|---|---|

| "In the video of the man sitting on the sofa, please add a small black cat..." | "Add a cat that jumps onto his lap, he begins to pet it. Keep everything else the same." |

| "Please remove the cell phone... and fill in the background so it looks like..." | "Make the phone invisible. Keep everything else the same." |

Other working edit prompts: "Make this video anime" / "Put a fashionable hat on this person" / "Change the lighting to be more dramatic" / "Change the text on the sign to say 'Omni Flash'".

**Gotcha — store:** editing via previous_interaction_id only works if the *prior* call kept the interaction server-side (store defaults to true in gemini_omni_video). Set store=false only for one-shot generations you will never edit.

**Editing uploaded videos:** pass input_video_path instead of previous_interaction_id; the tool uploads it via the Files API. Unavailable in the EEA, Switzerland, and the UK (editing *generated* videos works everywhere).

Hard limitations (preview)

  • Output: 3-10s, 720p, 24fps, MP4 with audio; aspect ratio 16:9 or 9:16. All output carries an invisible SynthID watermark.
  • No seed, negative prompt, temperature, top_p, or system instructions.
  • No video extension or first/last-frame interpolation; no voice editing.
  • Audio reference inputs unsupported. Video references ≤3s are accepted by the schema but **not processed correctly** — don't rely on them.
  • Multi-video prompting unsupported; may degrade output.
  • English fully supported; other languages untested.
  • Images of minors (EEA/CH/UK) and certain recognizable people are blocked for upload/editing.

Score breakdown

Trigger
9.0
Description gives what plus four concrete when-scenarios and tool/env names; when-not covered by provider-comparison table.
Structure
8.0
127-line single file with clear sections; no scripts or references layer needed at this size.
Workflow
7.6
Numbered edit workflow with layered refinement, store gotcha, and routing rule for edit vs selector; no validation loop.
Content
9.0
Concrete official prompt examples and avoid/instead pairs; timecode syntax demonstrated.
Engineering
9.0
Valid rich frontmatter (allowed-tools, env_any); sources are official ai.google.dev links.
Security
10.0
Env-var keys, official Google domains, no scripts or injection; regional content limits documented.
Strong provider guide for Gemini Omni Flash: description with four numbered use scenarios and env keys, when-to/when-not table, surgical conversational-editing workflow with good/bad prompt pairs, store gotcha, and hard limitations. Single-file reference; no verification steps beyond provider guidance.