video-gen
AI video generation via Fal.ai, Seedance 2.0, Kling, MiniMax Hailuo, xAI Grok Imagine, Google Gemini Omni, OFox, and Agnes Video
Install / Use
npx skills add 0xsline/OpenChatCut --skill video-genInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
AutomationSupported Platforms
Our assessment of video-gen
video-gen scores 92/100 on our quality scale, 861st of 2,790 Automation skills we index (top 31%).
Its SKILL.md is 17 KB long, well organised into 24 sections with 2 code examples: a thorough specification that gives an agent plenty to work with.
With 1,986 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so video-gen is actively maintained.
- Our last check on 2026-10-31 found the source still online.
- It is released under AGPL-3.0, a copyleft license: you can use it, but modified versions you distribute must carry the same license.
- 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-10-01. Automated pattern scan on 2026-09-30. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
video-gen compared with similar skills
All 4 of these similar skills score higher than video-gen; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| video-gen (this skill)by 0xsline | 92 | 2.0k | 56d 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 |
| Claude-Code-Game-Studiosby Donchitos | 100 | 39.7k | 7d ago | CLAUDE.md |
Frequently asked questions
- How do I install video-gen?
- Run
npx skills add 0xsline/OpenChatCut --skill video-gen. The install tabs above show the steps for each supported agent. - Which AI agents does video-gen work with?
- It is written for Gemini CLI, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is video-gen 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 AGPL-3.0-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 video-gen still maintained?
- The repository was last updated about 2 months ago, so video-gen is actively maintained.
Skill content
View source on GitHubname: video-gen description: | AI video generation via Fal.ai, Seedance 2.0, Kling, MiniMax Hailuo, xAI Grok Imagine, and OFox. Use when the user wants to generate a video clip — text-to-video, image-to-video, first/last-frame transitions, reference-guided generation, multi-shot, or generatively editing / extending an existing clip. user-invocable: true
Video Gen
Submits one video generation job per call and returns a jobId. Job management (wait / status) belongs to track_progress; this skill does not place videos on the timeline automatically.
When to Use
Any time the user wants to generate a video clip — text-to-video, image-to-video, first-last-frame transition, reference-based generation, multi-shot storyboard, or generatively editing / extending an existing video (producing new generated footage based on a source clip; not timeline trimming).
Models
| Model | Reference | Strengths |
| --- | --- | --- |
| fal + falModel | references/fal.md | Explicit Fal catalog; see tool schema for per-model limits |
| seedance2 | references/seedance2.md | Default when configured. Multimodal refs, first/last, edit/extend/bridge, 2–15s, 480p/720p/1080p/4k, audio/seed/camera/watermark/last-frame/task controls. |
| kling | references/kling.md | Technical camera/performance; Omni multi-shot; images ≤7 (≤4 with one feature refVideos); std/pro; 3–15s. |
| hailuo | references/hailuo.md | MiniMax 海螺. T2V / I2V / first+last; 6s or 10s; 512P (Hailuo-02), 720p→768P, 1080P (6s); no multi-ref / multi-shot. |
| grok-imagine-video | references/grok-imagine-video.md | xAI Grok Imagine. Text-to-video only; 1–15s; 480p/720p/1080p; audio track included. |
| ofox | references/ofox.md | OFox multi-model gateway (Seedance/Wan and more behind one key). Text/image-to-video, first+last frame, up to 9 image refs; 2–30s with per-model API limits; 480p/720p/1080p per model. |
IMPORTANT: Before generating, READ the chosen model's reference for capabilities, input channels, modes, prompt structure, and model-specific behavior. Never invent params the reference forbids.
Model Selection
Respect configured vendors from the capabilities prompt (only call a model whose key is on).
- User named a vendor ("用海螺", "MiniMax", "Kling", "Seedance") → that
model, if configured. - If Fal.ai is selected or requested, use
model: "fal"and the requestedfalModelor saved Fal default from capabilities. Ask if no Fal model is selected. Read the Fal catalog constraints in the tool schema; the native-provider limits below do not apply. - Else default
seedance2when Seedance is configured. - Else if only Kling is on →
kling. Else if only MiniMax is on →hailuo. Else if only xAI is on →grok-imagine-video. Else if only OFox is on →ofox. - Switch away from default when:
- Need multi-shot customize / intelligence →
kling(confirm if not user-named). - Need rich multi-modal refs (video/audio refs, edit/extend) →
seedance2. - Need a short single beat and only MiniMax is available, or user wants Hailuo →
hailuowith duration 6 or 10.
- Need multi-shot customize / intelligence →
If the required model is not configured, say so and offer: another configured video vendor, upload, or Motion Graphic — do not pretend the API exists.
Briefly tell the user what you will generate before submitting.
Tool Params
| Param | Values | Default |
| --- | --- | --- |
| model | seedance2, kling, hailuo, grok-imagine-video, ofox, fal | seedance2 when available |
| durationSeconds | model-specific | seedance/kling ~5; hailuo 6 or 10 (1080p → 6 only); grok 1–15; ofox 2–30 (per-model API limits) |
| ratio | see model docs | 16:9 (seedance/kling/grok/ofox); ignored on hailuo |
| resolution | 480p, 512p, 720p, 1080p, 4k | provider-specific; hailuo adds 512p for Hailuo-02; grok: 480p/720p/1080p |
| refVideoMode | feature, base | kling only, with refVideos |
| promptOptimizer / fastPretreatment | boolean | hailuo only |
| generateAudio, seed, cameraFixed, watermark | controls | seedance only |
| returnLastFrame, executionExpiresAfter, priority | controls | seedance only; requested last frame becomes another image asset |
| name | descriptive asset name | required for good pool UX |
| firstFrame | project image asset ref | optional |
| lastFrame | project image asset ref | seedance / kling / hailuo (requires firstFrame; not with multi-ref on seedance) |
| refImages / refVideos / refAudios | asset refs | seedance full; kling: images + 1 feature video (no audio); hailuo: none (frames / S2V subject) |
| mode / shotType / multiPrompts | Kling multi-shot | kling only |
Model-specific params — see the model's reference.
Input Resolution
firstFrame / lastFrame / refImages / refVideos / refAudios all take a project asset reference. Prefer a full UUID or short prefix from read_project; asset://<id> and same-project asset URLs returned by read_project are also accepted. Per-slot type: frame slots and refImages → image; refVideos → video; refAudios → audio.
External URLs and base64 are not accepted. If the source is a public URL, download it into the project first (download_media for video/audio, submit_image for images) and pass the resulting asset id.
Workflow
Four-step loop. For each new generation, restart from Step 1 if the user's intent has shifted.
Step 1 — Align scope with the user
Before writing any prompt, align on three dimensions:
-
Duration & segments — total length, how many shots, and whether they live in one clip or several.
If the user has already stated a direction ("做一段", "in one video", "分别生成", "split into N shots", etc.), follow it — don't second-guess.
Otherwise, surface the two paths and let the user pick:
- Multi-shot within one clip (see model ref) — single inference, subject / lighting / style physically consistent across sub-shots; fits a coherent narrative within the per-clip duration cap.
- Multiple clips — each clip is independently controllable and re-rollable, but identity and style continuity have to be carried by anchors; fits durations beyond the cap or hard scene breaks.
Offer the trade-off; do not pick for the user.
-
Content — what each clip depicts. Summarize back what you understood, segment by segment. When content is vague (e.g. "generate a video of a girl dancing"), the user typically hasn't specified one or more of:
- Subject: who / what is the main subject (appearance, outfit, defining features)?
- Action: what are they doing? (For talking / emotional shots, what micro-expression?)
- Scene: where — setting, time of day, environmental details?
- Lighting / color mood: what atmosphere?
- Camera: any shot-size / angle / movement preference?
- Style: visual style or reference (cinematic / anime / documentary / ...).
Focus on the items that matter for this specific request and can't be safely inferred — don't turn this into a blank-filling exercise. Summarize the understood parts back to the user before proceeding.
-
Consistency anchors — only when multiple shots reuse a character, object, or scene: identify which anchor (reference image or video) to pin across shots. For sourcing rules, see §Visual consistency across shots below.
For each dimension, check the user's words:
- Clear — proceed.
- Ambiguous or missing — ASK the user. Do not guess, do not default to your own interpretation. A round-trip confirmation is cheaper than a wasted generation.
What NOT to do
- Do not "tell then submit" — announcing "I'll make this as 2 clips" and immediately submitting is not alignment, it's a unilateral decision with announcement.
- Do not default to splitting a single-video request into multiple clips. A single clip can carry multiple sub-shots (see model ref), with subject / lighting / style physically consistent across them. Surface the trade-off, then let the user choose.
- Do not skip the ask because you think the answer is obvious.
Hard overrides (user's explicit word wins)
- "one clip / single clip / 一条 / 一个镜头 / in 1 clip" → never split, even if the description is objectively long.
- "N shots / N 段 / N 个镜头" → generate exactly N.
- "use this image / 用这张图" → use as reference, don't substitute.
Step 2 — Write the prompt
See the chosen model's reference for prompt structure and param combinations (e.g., Seedance's 8-element structure and modes; Kling's prompt tips). Before submitting, check:
nameis a descriptive asset name — descriptive enough for the user (and you in later turns) to recognize this asset in the project library. Avoid vague names like "Untitled" or "clip 1".- Param combination matches the user's intent — see the Modes section in the model's reference.
- Generated video audio is not a tool parameter (provider-side). Hailuo has no ratio/multi-ref; do not invent those params.
- On validation failure, read the error and fix the inputs — do not blindly retry the same invalid arguments.
Step 3 — Submit one, wait, confirm
Submit one generation job at a time. Unless the user explicitly asked for multiple clips in parallel, do not submit the next clip until the current one completes and the user has reviewed it. Parallel submission hides problems: if the first shot has drift or wrong framing, the user would rather redo it once than have several misaligned shots to discard.
submit_video.ratiocontrols the generated asset only; it does not change the project timeline canvas. If the user requested a final output aspect ratio (for example "9:16 vertical" or "16:9 landscape"), set the timeline canvas to the same ratio withmanage_timelinesaction=update (e.g. ratio:"9:16") before placing the completed asset. If the user asked for no black bars / full-bleed, passfit:"cover"when setting the canvas or updating/adding the visual item.- Do not use this skill for job management — use the
track_progresstool for status/wait. - After submitting, end your turn (tell the user the job was created) unless a follow-up task is already queued.
- When the job finishes, surface the result to the user for review before proceeding to the next shot.
- Model-specific failure handling — see the model's reference.
Step 4 — Iterate
When the user wants a next clip, a revision, or a continuation:
- If it's the next shot in a multi-shot sequence — reuse the established anchor (see §Visual consistency across shots below for principles, model ref for flag-level details).
- If the user's feedback is ambiguous ("it doesn't feel right") — ask what specifically to change before regenerating.
- If the same text-prompt adjustment has failed twice — stop adjusting text. Switch to reference images, or switch to edit mode where the model supports it (see model ref).
- Each new generation restarts the loop at Step 1 — realign if scope shifted.
Visual consistency across shots
Text alone cannot reliably maintain visual identity across shots; visual references constrain output far more precisely than words.
Anchors: the cornerstone of consistency
An anchor is a reference image or video pinned across every shot that shares the same character, object, or style. Any multi-shot sequence with recurring visual elements needs an anchor — don't try to reproduce them from text.
Sourcing an anchor
Have reference awareness. When the user's request involves a recurring character / object / scene, think about what anchor to use before writing prompts:
- Check the project first. What has the user already provided or approved? Uploaded images, previously generated and approved shots, or earlier project asse
Truncated for display — read the full file on GitHub.
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
Claude-Code-Game-Studios
39.7kTurn Claude Code into a full game dev studio — 49 AI agents, 72 workflow skills, and a complete coordination system mirroring real studio hierarchy.
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.
