- name
SKILL.md
स्किल फ़ाइल पब्लिशर की रिपॉज़िटरी में ही रहती है।
कॉपी की गई कमांड टर्मिनल में पेस्ट करें। यह इस SKILL.md को उस एजेंट में इंस्टॉल करती है।
npx skills add ChatCut-Inc/agent-plugin --skill talking-head-guide -a cursor -yकॉपी की गई कमांड टर्मिनल में पेस्ट करें। यह इस SKILL.md को उस एजेंट में इंस्टॉल करती है।
npx skills add ChatCut-Inc/agent-plugin --skill talking-head-guide -a claude-code -yकॉपी की गई कमांड टर्मिनल में पेस्ट करें। यह इस SKILL.md को उस एजेंट में इंस्टॉल करती है।
npx skills add ChatCut-Inc/agent-plugin --skill talking-head-guide -a codex -yकॉपी की गई कमांड टर्मिनल में पेस्ट करें। यह इस SKILL.md को उस एजेंट में इंस्टॉल करती है।
npx skills add ChatCut-Inc/agent-plugin --skill talking-head-guide -a grok -yकॉपी किया गया संदेश Grok Bot चैट में भेजें। Bot यह SKILL.md GitHub से लाता है और उसे उन स्किल में जोड़ देता है जो आपके सभी Bot साझा करते हैं।
Install this skill: https://github.com/ChatCut-Inc/agent-plugin/tree/HEAD/antigravity/skills/talking-head-guideपब्लिशर से
Before using this skill, read the required continuation in full. It is part of this skill and contains mandatory workflow, tool-contract, and safety instructions; do not act from this entry file alone.
Required input: an existing speech-led source registered or imported into the project — for example a single-speaker talking-head / 口播, a two- or multi-speaker interview / 访谈, a video podcast, lecture, tutorial, or course. For transcript-based A-roll editing, follow asset-import, then start as soon as the transcript is ready. If the user wants to start without source footage (e.g., generate a fresh talking-head from scratch), this skill doesn't apply.
asset-import when an attachment or readable local path still needs import. Reuse editor-uploaded registered assets without importing them again.When creating, targeting, or opening a project for visible work, provide the clean editorUrl before nontrivial edits and again before final delivery if the visible project no longer matches. Antigravity's browser agent may open it when the user asks; do not require an internal browser handoff.
Independent treatments that can be applied to speech-led videos. Pick the ones that match what the user wants — not all are needed every time.
voice-isolation skill.When the user's language is Chinese, use the exact product terms in parentheses above in widget options, choices options, and conversation copy. Do not retranslate them; that would conflict with terminology elsewhere in the product.
Beyond picking treatments, a talking-head edit is shaped by several orthogonal variables. When the user's ask is vague, these are what's worth clarifying first:
When more than one of these variables is missing, ask concise related text questions after loading widget-forms, keeping stable choice ids internally. Do not emit native form or <choices/> tags.
When multiple treatments have been aligned with the user, they depend on each other and must be finalized in dependency order. This section is only relevant after alignment — it doesn't tell you what to start with on a fresh request.
The speech timing (set by A-roll editing) anchors everything downstream — MG placement, B-roll cut-covers, music duration, and caption sync all reference the final speech timeline.
So: finalize A-roll editing before committing any visual, audio, or text layer. Don't write captions against pre-edit speech, don't cut music to pre-edit length, don't place MG against timing that will shift.
Once the cut structure is final, run smooth_audio once as the last audio step — it micro-crossfades every hard audio cut and fades exposed edges so edits don't pop. Run it after apply_script/clean_script restructuring (reflow drops transitions); it's idempotent, so re-run it if the timeline changes again.
You must confirm the result with the user after each major step before starting the next, unless the user has explicitly asked to run end-to-end without stopping. Key checkpoints when multiple treatments apply: after A-roll editing finalizes the speech timing; before MG generation (confirm style and direction, and, when it isn't obvious, whether it sits over the video as an overlay or takes the whole frame); after MG generation; same pattern for B-roll, music, and captions. Don't bundle multiple checkpoints into one response — confirm each step separately. An upstream mistake forces redoing everything downstream (e.g., MG placed against pre-cleanup timing wastes generation credits when the timeline shifts).
In a talking-head workflow, the first step is usually A-roll editing: editing the original spoken footage.
A-roll edits are ultimately applied to the timeline and change what the viewer actually hears and sees. However, the editing decisions should usually start from the transcript, because the core question is: what spoken content should the viewer hear, and what should be removed, compressed, or reordered?
A-roll editing is not only cleanup. First decide what spoken-content task the user is asking for, then choose the editing strategy and tools.
Common tasks:
Cleanup is the most common task and the one most likely to fail from bad boundary decisions. It is described in detail below. Other tasks get shorter rules, but still follow the shared A-roll principles: complete meaning, clear boundaries, and natural listening flow.
These principles apply to all A-roll tasks, not only cleanup.
[sN] segment it sits in; keeping a whole segment for one requested sentence is over-keeping that drags in unrequested speech. This applies only when the task names what to keep — never to open-ended cleanup, where you keep complete units (above).[sN], [cN], [gap], word indices, clip ids, or segment ids. The user cannot see those addresses and will not understand what they mean. Use the actual spoken content, a short quote, or a plain-language description of the edit.Good cleanup does not mean making the video as short as possible, and it does not mean rewriting the speaker into a different script.
Good cleanup means:
Bad cleanup usually falls into two failure modes:
Default principle: remove defects without changing meaning; make speech smoother, not harder; prefer small local cuts over whole-sentence or whole-segment deletion; when unsure whether a cut harms meaning, keep it.
Below are the common cleanup categories and how to make editing decisions for each.
Fillers fall into two categories.
The first category is clearly meaningless hesitation sounds. These are usually safe to remove:
umuherah呃额えー / えーと / えっとあーんーWhen they do not carry special meaning, use clean_script for bulk cleanup of its supported literal tokens: um, uh, er, ah, 呃, and 额. Japanese hesitation sounds require a Script edit (read_script → edit timeline.md → apply_script); clean_script does not currently remove them.
The second category depends on context and must not be removed by word list alone:
solike然后就是嗯啊那个那对所以但是あの / あのーその / そのーまあなんかちょっとでうーんやっぱりHow to decide:
Examples:
um, I think this solves the main problem -> remove um.It works like a checklist -> keep like; it is a comparison.The upload failed, so we retried it -> keep so; it carries cause/result.right after the call, send the recap -> keep right; it modifies timing.然后我们再看第二点 -> keep 然后; it marks sequence.えーと、次のポイントです -> remove えーと; it is pure hesitation.あの人が言っていた通りです -> keep あの; it is a demonstrative, not hesitation.あの、ちょっと待ってください -> remove the leading あの; it is hesitation here.まあ、悪くないと思います -> keep まあ; it softens the judgement and carries tone.なんか違和感がある -> keep なんか; it means "somehow" here, not padding.A retake is when the speaker retries the same intended idea because they misspoke, got stuck, forgot words, or restarted. Retake cleanup is not "delete repeated text." The goal is to keep one complete, natural, logically coherent version of the intended idea.
Use this decision path:
A repeated lead-in is redundant only when another equivalent lead-in remains naturally connected to the kept content. If removing every copy makes the result lose structure or sound abrupt, keep one natural copy and remove only the extra restarts. Do not stitch unfinished fragments from different attempts into one artificial sentence.
Examples are patterns, not a closed list:
There, there's no After Effects, no Premiere, no DaVinci Resolve learning.
Keep the complete sentence, but remove the abandoned restart:
There's no After Effects, no Premiere, no DaVinci Resolve learning.
Do not keep the stray first word just because the full sentence is otherwise useful.And secondly, ... and secondly, we're introducing a brand new UI.
Remove the extra restart, but keep one natural lead-in attached to the kept content:
And secondly, we're introducing a brand new UI.
Do not delete every structural marker and leave only:
We're introducing a brand new UI.Then the next one is different from comedy. It is popular on Disney Plus. It is called...
Later retake:
It is a popular Disney Plus show called Love Story.
Keep useful setup that the later retake does not repeat, and cut from the failure point:
Then the next one is different from comedy. It is a popular Disney Plus show called Love Story.Use false starts / unfinished fragments for this category. False start is the more natural editing/transcription term for a speaker beginning a phrase and then restarting or abandoning it; unfinished fragment makes the dangling half-sentence case explicit.
Only remove a fragment when it clearly does not form useful information.
Safe to remove:
Do not remove:
If only part of a sentence or segment is wrong, do not delete the useful content around it. Remove only the bad word, phrase, or pause; if a local cut cannot sound natural, keep the segment.
Pause cleanup should default to compression, not zeroing out. Spoken video needs natural breathing room.
Default rules:
Load only the reference for the branch the user selected. Do not preload references for unrequested treatments; default cleanup requires no reference.
For A-roll editing scenarios other than cleanup — including highlight extraction, restructure, hook / short version, target-script / script alignment, or building versions, highlights, and excerpts — read references/other-a-roll-editing-scenarios.md from this skill's base directory completely before planning or editing that A-roll branch.
Guide for editing speech-led videos where spoken delivery or conversation drives the cut — single-speaker talking-head / 口播, two- or multi-speaker interview / 访谈, video podcast, lecture, tutorial, cou
---name: talking-head-guidedescription: Guide for editing speech-led videos where spoken delivery or conversation drives the cut — single-speaker…---# antigravity/skills/talking-head-guide/SKILL.mdओवरव्यू
Guide for editing speech-led videos where spoken delivery or conversation drives the cut — single-speaker talking-head / 口播, two- or multi-speaker interview / 访谈, video podcast, lecture, tutorial, course, and similar formats. Load before analyzing, planning, or performing non-trivial edits of those formats, including speech cleanup (剪口播 / 口播剪辑 / 去口癖 / clean up fillers / smooth speech), pause or repeated-take removal, motion graphics layered onto the footage (口播加 MG / 加动画), B-roll (加 B-roll / add B-roll), music, or captions. For motion graphics specifically, use this together with the active Motion Graphics skill/workflow available in the current ChatCut environment — this skill adds speech-specific guidance (rhythm-aware timing, frame-aware placement, subject/caption protection, placement verification).
FAQ
पब्लिशर से antigravity/skills/talking-head-guide/SKILL.md डाउनलोड करें, या पाथ कॉपी करके रिपॉज़िटरी खोलें। PlugMCP स्किल को सूचीबद्ध करता है, फ़ाइल होस्ट नहीं करता।
पब्लिशर इसे https://github.com/ChatCut-Inc/agent-plugin पर रखता है।
Claude, Cursor, Codex और Grok Build वह SKILL.md पढ़ सकते हैं जिसे आप पब्लिशर की रिपॉज़िटरी से जोड़ते हैं। जब आप चैट में स्किल के GitHub फ़ोल्डर का लिंक भेजते हैं, तो Grok Bot उसे इंस्टॉल कर देता है।