- name
SKILL.md
स्किल फ़ाइल पब्लिशर की रिपॉज़िटरी में ही रहती है।
कॉपी की गई कमांड टर्मिनल में पेस्ट करें। यह इस SKILL.md को उस एजेंट में इंस्टॉल करती है।
npx skills add ChatCut-Inc/agent-plugin --skill video-gen -a cursor -yकॉपी की गई कमांड टर्मिनल में पेस्ट करें। यह इस SKILL.md को उस एजेंट में इंस्टॉल करती है।
npx skills add ChatCut-Inc/agent-plugin --skill video-gen -a claude-code -yकॉपी की गई कमांड टर्मिनल में पेस्ट करें। यह इस SKILL.md को उस एजेंट में इंस्टॉल करती है।
npx skills add ChatCut-Inc/agent-plugin --skill video-gen -a codex -yकॉपी की गई कमांड टर्मिनल में पेस्ट करें। यह इस SKILL.md को उस एजेंट में इंस्टॉल करती है।
npx skills add ChatCut-Inc/agent-plugin --skill video-gen -a grok -yकॉपी किया गया संदेश Grok Bot चैट में भेजें। Bot यह SKILL.md GitHub से लाता है और उसे उन स्किल में जोड़ देता है जो आपके सभी Bot साझा करते हैं।
Install this skill: https://github.com/ChatCut-Inc/agent-plugin/tree/HEAD/antigravity/skills/video-genपब्लिशर से
If submit_video is not loaded yet, load it with ToolSearch before calling it, so you use its real parameters instead of guessing.
Submits one video generation job per call and returns a jobId. Job status and later check-backs belong to track_progress; this skill does not place videos on the timeline automatically.
Any time the user wants to generate a video clip — text-to-video, image-to-video, first-last-frame transition, reference-based generation, or generatively editing / extending an existing video (producing new generated footage based on a source clip; not timeline trimming).
IMPORTANT: Before generating, READ the chosen model's reference for capabilities, input channels, modes, prompt structure, and model-specific behavior.
For a new generation, seedance-2-5 is the default. Only switch when one of:
minimax-h3.minimax-h3-max.kling and confirm before submitting.omni (360p drafts, ≤10s, supports targeted edits) and confirm before submitting.seedance-2-5; it and full seedance2 support 1080p.seedance2mini (4-15s, ~50% of the 2.0 full-model cost) and confirm before submitting.seedance2fast (480p or 720p, 4-15s, ~80% of the 2.0 full-model cost, returns much sooner) and confirm before submitting.Otherwise stay on seedance-2-5.
For revising a clip that already exists, the choice is made in Step 4 — not here. A revision request is not a reason to change the default for future fresh generations. Omni 1.1 replaces the previous Omni choice; keep the omni alias and do not invent a second legacy choice.
Access note: all eight models require ChatCut paid video-generation entitlement (subscription or paid credits). Never present another model as a free workaround for a subscription gate; offer free Motion Graphic animation instead when the user asks for a free path.
Model-specific params (e.g., Kling mode, Seedance refImages / refVideos / refAudios) — see the model's reference.
firstFrame / lastFrame / refImages / refVideos / refAudios all take a project asset reference. Prefer a full UUID or short prefix from browse_assets; asset://<id> and same-project asset URLs returned by asset tools 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 sandbox workspace, import the local file through asset-import + push_asset, and pass the resulting asset id.
Four-step loop. For each new generation, restart from Step 1 if the user's intent has shifted.
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:
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:
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:
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:
name is 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".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.ratio controls 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 with manage_timelines action=update (e.g. ratio:"9:16") before placing the completed asset. If the user asked for no black bars / full-bleed, pass fit:"cover" when setting the canvas or updating/adding the visual item.track_progress for an immediate status read and follow its later check-back guidance.When the user wants a next clip, a revision, or a continuation, first decide what the existing clip is in the next call:
A localized change defaults to omni + continueFrom. For an explicitly chosen Omni continuation use taskMode:"extend" + continueFrom; for transitions between two images use firstFrame + lastFrame. Keep Seedance 2.5 as the general edit/extend path otherwise. Do not wait for the user to say "keep everything else" — "把气球改成黄色" / "remove the text in the corner" already means it. Route to seedance-2-5 only when the change genuinely needs re-inference (motion, camera, duration, whole-clip style), not because Seedance is more familiar.
omni source edits/extensions require a project video of up to 10 seconds. For longer sources use seedance-2-5 + refVideos or ask to trim first. This integration is stateless: do not promise the upstream 40-second multi-turn workflow.
No generative edit is lossless. Omni 1.1 supports upscaled 1080p/4k, but higher resolution does not guarantee detail or unchanged pixels. Review the result before replacing a timeline item; the original asset remains available.
Then apply the standing rules:
omni continueFrom for targeted changes, seedance refVideos for re-generation).submit_video reports the omni edit round; when it warns about chain depth, relay the suggestion to the user instead of silently continuing.Text alone cannot reliably maintain visual identity across shots; visual references constrain output far more precisely than words.
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.
Have reference awareness. When the user's request involves a recurring character / object / scene, think about what anchor to use before writing prompts:
When no existing asset fits and one must be generated, propose it to the user first — it costs credits and shapes every downstream shot. Model-specific paths — see the chosen model's ref.
@Image1 / @Video1 in the prompt — not vague phrases like "the same car as before".track_progress action=wait and do what its result says (an automatic follow-up turn where supported, otherwise later check-backs) until it is terminal, then use its outputAssetId as the anchor reference. Neither action blocks. Do not submit dependent shots in parallel.When a project has multiple named characters with distinct attributes (e.g. Faz with fire energy, Kev with ice energy), treat each character as a separate anchor — one reference asset per character. In every prompt:
Missing either explicit attribution or negation causes cross-character attribute mixing.
Multiple characters in the same frame. For shots where multiple characters appear together (especially facing the camera), the model is prone to face-swap or body-clipping. Add strong positional + outfit anchors to each character and prefer a fixed camera for that shot:
Positional words (left / right / foreground / background) + distinctive outfit colors give the model enough signal to keep the characters apart.
If a visual-identity issue (wrong character, drift, color mismatch) persists after two text-prompt adjustments on the same shot, stop adjusting text. Text is not a substitute for an anchor. Escalate to:
Do not submit a third text-only retry on the same consistency issue.
Simple, one-off, or exploratory requests do not need anchors — generate directly.
// Text-to-video (Seedance 2.5 default)
submit_video({
model: "seedance-2-5",
prompt: "A cat walks across a sunny windowsill",
name: "Cat on windowsill",
});
// Image-to-video with Seedance 2.5 — pass the project asset id directly
submit_video({
model: "seedance-2-5",
prompt: "The scene comes to life, gentle breeze rustles the curtains",
firstFrame: "abc12345",
name: "Living room animation",
});
// Kling text-to-video — only after Model Selection check
submit_video({
model: "kling",
prompt: "A sports car drifts around a wet corner",
name: "Car drift shot",
});
After submission, return the jobId and end the turn by default. Call track_progress only when the user asks for status (action=status) or a dependent step needs the completed asset (action=wait, then do what its result says). Both return immediately; do not loop.
For complex multimodal jobs, build the full args object up front and pass it in a single call:
submit_video({
model: "seedance-2-5",
prompt: "...",
name: "...",
refImages: ["def67890", "ghi24680"],
refVideos: ["abc99999"],
refAudios: ["jkl55555"],
durationSeconds: 8,
ratio: "9:16",
});
name with a descriptive asset name.submit_video — status and later check-backs belong to track_progress.AI video generation via Seedance, Kling, Gemini Omni, MiniMax H3, and MiniMax H3 Max. Use when the user wants to generate a video clip — text-to-video, image-to-video, first/last-frame transitions, re
---name: video-gendescription: AI video generation via Seedance, Kling, Gemini Omni, MiniMax H3, and MiniMax H3 Max. Use when the user wants…---# antigravity/skills/video-gen/SKILL.mdओवरव्यू
AI video generation via Seedance, Kling, Gemini Omni, MiniMax H3, and MiniMax H3 Max. Use when the user wants to generate a video clip — text-to-video, image-to-video, first/last-frame transitions, reference-guided generation — or wants to modify / edit / extend an existing generated clip.
FAQ
पब्लिशर से antigravity/skills/video-gen/SKILL.md डाउनलोड करें, या पाथ कॉपी करके रिपॉज़िटरी खोलें। PlugMCP स्किल को सूचीबद्ध करता है, फ़ाइल होस्ट नहीं करता।
पब्लिशर इसे https://github.com/ChatCut-Inc/agent-plugin पर रखता है।
Claude, Cursor, Codex और Grok Build वह SKILL.md पढ़ सकते हैं जिसे आप पब्लिशर की रिपॉज़िटरी से जोड़ते हैं। जब आप चैट में स्किल के GitHub फ़ोल्डर का लिंक भेजते हैं, तो Grok Bot उसे इंस्टॉल कर देता है।