[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6BXZ2G5V7MZPR70X2JN5QMX":3,"skill-same:01M6BXZ2G5V7MZPR70X2JN5QMX":63},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":35,"linkOnly":36,"markdownContent":37,"markdownBody":38,"frontMatter":39,"refName":41,"commitSha":42,"skillDirectory":43,"forksCount":44,"repositoryHtmlUrl":45,"repositoryHomepageUrl":46,"ownerHtmlUrl":47,"ownerBlogUrl":12,"ownerDescription":48,"updatedAt":49,"install":50,"resources":62},"01M6BXZ2G5V7MZPR70X2JN5QMX","caption-titles",null,"Add and animate a consistent text layer on an existing NodeTool timeline. Use for titles, lower-thirds, captions, callouts, end cards, number tickers, deterministic scrambles, and text on a path.","nodetool-ai\u002Fnodetool","nodetool-ai","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F164873569?v=4","01M6BXPFDW36K9K1MR8ZH63HG2","nodetool.ai","01M6BXPFJ893XM219GQN60B0WK",635,"AGPL-3.0","https:\u002F\u002Fgithub.com\u002Fnodetool-ai\u002Fnodetool\u002Fblob\u002Fmain\u002Fpackages\u002Fsystem-skills\u002Fcaption-titles\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34],"caption titles","timeline","Captions","text","animate","nodetool","use","deterministic","end","add","number","true","layer","path","for","Existing","2026-11-10 10:12:30",false,"---\nname: caption-titles\ndescription: Add and animate a consistent text layer on an existing NodeTool timeline. Use for titles, lower-thirds, captions, callouts, end cards, number tickers, deterministic scrambles, and text on a path.\nfeatured: true\n---\n\n# Caption & Titles → Timeline Agent\n\nWork directly with timeline capabilities and open-timeline tools. Do not build a workflow or fabricate a cut.\n\n`timeline-edit-ops` carries the op contract for every call named here. `motion-principles` gives the entry and exit durations and easing behind each tier's presets, `frame-composition` fixes the safe inset and where a tier sits, `color-motion` the scrim and contrast fixes when type does not read, and `logo-reveal` owns the brand mark at the head or tail.\n\n## Type is post, never a render prompt\n\nEvery board skill and every video prompting skill sends its on-screen copy here. A title card, a super, a lyric or a CTA is a text clip on the timeline, not words in a `generate_video` or `generate_image` prompt: generators letter unreliably, and copy baked into pixels cannot be corrected, translated or re-timed. When a board's shot `action` carries `Text: …`, that is the caption map's input, and the render prompt should not have asked for it.\n\n## Hard gate\n\nList and read the selected timeline first. When the job is to caption or title footage, the timeline must contain picture clips. If it is missing or has none, stop and ask for a real cut; route users to storyboard or script-to-timeline work instead. A typographic piece built from type and shapes alone, such as a title sequence, kinetic text or a standalone end card, needs no picture clips: build it through `motion-graphics` and use the tiers below for its type. Snapshot the timeline before editing with `create_timeline_version`.\n\nRead `fps`, `width` and `height` off `get_timeline` before setting a size: `fontSizePx` is authored against the sequence resolution, and the tiers below are fractions of `height`.\n\n## Lock one type system before adding text\n\nResolve type family and tier weights, five size tiers as fractions of frame height, text\u002Faccent\u002Fscrim palette, safe inset and maximum width, and per-tier motion presets. Prefer a supplied brand kit, then existing text on the timeline, then a platform-safe system. Keep these tiers consistent: T1 title\u002Fend card, T2 lower-third, T3 captions, T4 callouts, T5 CTA.\n\nThe family is one NodeTool ships — `Inter`, `Space Grotesk`, `Bebas Neue`, `Playfair Display`, `Lora`, `JetBrains Mono` — or every host resolves it against its own installed fonts, the editor and the render disagree on line widths, and `validate_timeline` reports `font_not_portable`. Sizes below 2.5% of frame height report `text_illegible`; body copy sits at 2.5–4%. `motion-direction` holds the same rule for the whole piece, so when a motion language already exists, take its type family rather than picking a second one.\n\nMotion per tier follows `motion-principles`: `fade` or `slide` in at 300–500ms, out at 200–300ms, role-default easing. Stagger only on a T1 or a kinetic T3 line of five words or fewer, and work out the span (`durationMs + offsetMs × (words − 1)`) against the clip — a span that does not fit is compressed silently and only `stagger_compressed` says so.\n\nEach tier has a shipped composition. Insert it with `{\"op\": \"insert_composition\", \"composition_id\": \"\u003Cid>\", ...}` and override its `params` rather than building the rig from bare clips — the timing and motion inside it are already balanced.\n\n| Tier | Composition id |\n|---|---|\n| T1 title | `title-card` |\n| T2 lower-third | `lower-third` |\n| T3 captions | `caption-bar` |\n| T4 callouts | `callout` |\n| T5 CTA \u002F end card | `cta-end-card` |\n\nA brand mark at the head or tail is `logo-sting`.\n\nEvery live-picture T2–T4 element gets a matching scrim unless the plate is demonstrably controlled.\n\n## Caption map\n\nWrite the timed map before editing: tier, exact text, start\u002Fend, position, and scrim. Caption duration is at least `max(1200ms, words × 350ms)`. Titles\u002Fend cards stay on screen at least 2000ms, which leaves the read hold `motion-principles` § Holds sets between their in and out. Lower-thirds arrive about 500ms after a person appears and hold 2500–4000ms. One text idea per frame. Unknown facts use `[INPUT NEEDED: …]`.\n\n## Animate the letters and their content\n\nFor a number that changes during a text clip, store `textAnimator` on an\nanimation with `kind: \"ticker\"`, `from`, and `to`. It also accepts `decimals`,\n`padTo`, `prefix`, and `suffix`. Set `groupSeparator` to `\",\"` to show\nthousands as `2,847`; omitting it keeps existing tickers ungrouped. For a\ndeterministic decode into the clip's\nauthored text, use `kind: \"scramble\"` with a fixed `seed` and optional\n`charset`. These operate over the animation window, so a held final frame\nshows the finished value.\n\n```json\n{\"id\": \"count-in\", \"role\": \"in\", \"preset\": \"fade\", \"durationMs\": 900,\n \"textAnimator\": {\"kind\": \"ticker\", \"from\": 1, \"to\": 7,\n  \"padTo\": 2, \"suffix\": \" \u002F 07\"}}\n```\n\nFor unit-by-unit motion, set `stagger.unit` to `character`, `word`, or `line`\nand give it `offsetMs`. With a text stagger, `styleTracks` can target\n`glyph.color`, `glyph.blurPx`, or `glyph.trackingPx`. The colour uses CSS\ncolour values; blur and tracking use sequence pixels. Use `text.color` or\n`text.fill.stops.0.color` for a whole line. A text fill gradient also exposes\n`text.fill.angle` and stop offsets. The target must refer to an existing\nstyle field; `text.color` is hidden while a gradient fill is set.\n\nTo lay a title along a curve, set `textStyle.path` to an SVG path in\nnormalized canvas coordinates. This places the baseline on the path. It does\nnot make each character travel along it. Shape and mask paths can morph through\n`shape.d` and `mask.d` style tracks when both paths have matching commands and\npoint counts. Use `followPath` when the whole clip should move along a path.\n\n`edit_timeline`'s `animate_clip` input accepts presets and custom numeric\ncurves, but does not accept `textAnimator` or `styleTracks`; those fields are\ndropped from that call. To author them, read the current document and use\n`set_timeline_document` with the animation fields in the clip. That call\nvalidates the complete document and snapshots the previous state. Preserve\nthe other tracks and clips from the document. `timeline-edit-ops` owns the full\ntool contract.\n\n## Build and verify\n\nAdd separate overlay and subtitle tracks. For each map item, add scrim before text, apply the locked tier style, then animate it with that tier’s entry and exit preset. No hard cut-on. Use stagger only for tone-appropriate kinetic captions. Keep all text within safe margins and clear of faces and product moments.\n\nTwo facts about stacking decide whether the text is seen at all. The lowest track `index` draws on top, so the scrim's track index sits between the picture's and the text's — picture, scrim, text, in descending index. And word-level captions generated from a voiceover clip composite above every real track regardless of where that clip sits, so no title can cover them: time a T1 around the narration rather than over it.\n\nVerify in two passes, and they answer different questions. `validate_timeline` reads the document: `text_illegible` (size, or under 3:1 contrast against the text's own `background` plate or a full-frame shape behind it), `font_not_portable`, `stagger_compressed`, `animation_exceeds_clip`, overlaps, and clips shorter than a frame. Its contrast check refuses to guess — a translucent scrim, gradient type or a plate it cannot prove is behind the text produces no finding — so a silent pass is not a pass. Then `preview_timeline_frame` at each item's entry midpoint, a held moment, and its exit: that is where text over a busy plate, a scrim covering a face, or a caption still finishing when its clip ends shows up. Re-read the map against the frames: timing, reading floors, scrim ordering, one CTA at the end. Then render with `render_timeline` before calling the layer done, as `timeline-edit-ops` § The render loop describes: the frames show one timecode, the render shows the timing at speed.\n","# Caption & Titles → Timeline Agent\n\nWork directly with timeline capabilities and open-timeline tools. Do not build a workflow or fabricate a cut.\n\n`timeline-edit-ops` carries the op contract for every call named here. `motion-principles` gives the entry and exit durations and easing behind each tier's presets, `frame-composition` fixes the safe inset and where a tier sits, `color-motion` the scrim and contrast fixes when type does not read, and `logo-reveal` owns the brand mark at the head or tail.\n\n## Type is post, never a render prompt\n\nEvery board skill and every video prompting skill sends its on-screen copy here. A title card, a super, a lyric or a CTA is a text clip on the timeline, not words in a `generate_video` or `generate_image` prompt: generators letter unreliably, and copy baked into pixels cannot be corrected, translated or re-timed. When a board's shot `action` carries `Text: …`, that is the caption map's input, and the render prompt should not have asked for it.\n\n## Hard gate\n\nList and read the selected timeline first. When the job is to caption or title footage, the timeline must contain picture clips. If it is missing or has none, stop and ask for a real cut; route users to storyboard or script-to-timeline work instead. A typographic piece built from type and shapes alone, such as a title sequence, kinetic text or a standalone end card, needs no picture clips: build it through `motion-graphics` and use the tiers below for its type. Snapshot the timeline before editing with `create_timeline_version`.\n\nRead `fps`, `width` and `height` off `get_timeline` before setting a size: `fontSizePx` is authored against the sequence resolution, and the tiers below are fractions of `height`.\n\n## Lock one type system before adding text\n\nResolve type family and tier weights, five size tiers as fractions of frame height, text\u002Faccent\u002Fscrim palette, safe inset and maximum width, and per-tier motion presets. Prefer a supplied brand kit, then existing text on the timeline, then a platform-safe system. Keep these tiers consistent: T1 title\u002Fend card, T2 lower-third, T3 captions, T4 callouts, T5 CTA.\n\nThe family is one NodeTool ships — `Inter`, `Space Grotesk`, `Bebas Neue`, `Playfair Display`, `Lora`, `JetBrains Mono` — or every host resolves it against its own installed fonts, the editor and the render disagree on line widths, and `validate_timeline` reports `font_not_portable`. Sizes below 2.5% of frame height report `text_illegible`; body copy sits at 2.5–4%. `motion-direction` holds the same rule for the whole piece, so when a motion language already exists, take its type family rather than picking a second one.\n\nMotion per tier follows `motion-principles`: `fade` or `slide` in at 300–500ms, out at 200–300ms, role-default easing. Stagger only on a T1 or a kinetic T3 line of five words or fewer, and work out the span (`durationMs + offsetMs × (words − 1)`) against the clip — a span that does not fit is compressed silently and only `stagger_compressed` says so.\n\nEach tier has a shipped composition. Insert it with `{\"op\": \"insert_composition\", \"composition_id\": \"\u003Cid>\", ...}` and override its `params` rather than building the rig from bare clips — the timing and motion inside it are already balanced.\n\n| Tier | Composition id |\n|---|---|\n| T1 title | `title-card` |\n| T2 lower-third | `lower-third` |\n| T3 captions | `caption-bar` |\n| T4 callouts | `callout` |\n| T5 CTA \u002F end card | `cta-end-card` |\n\nA brand mark at the head or tail is `logo-sting`.\n\nEvery live-picture T2–T4 element gets a matching scrim unless the plate is demonstrably controlled.\n\n## Caption map\n\nWrite the timed map before editing: tier, exact text, start\u002Fend, position, and scrim. Caption duration is at least `max(1200ms, words × 350ms)`. Titles\u002Fend cards stay on screen at least 2000ms, which leaves the read hold `motion-principles` § Holds sets between their in and out. Lower-thirds arrive about 500ms after a person appears and hold 2500–4000ms. One text idea per frame. Unknown facts use `[INPUT NEEDED: …]`.\n\n## Animate the letters and their content\n\nFor a number that changes during a text clip, store `textAnimator` on an\nanimation with `kind: \"ticker\"`, `from`, and `to`. It also accepts `decimals`,\n`padTo`, `prefix`, and `suffix`. Set `groupSeparator` to `\",\"` to show\nthousands as `2,847`; omitting it keeps existing tickers ungrouped. For a\ndeterministic decode into the clip's\nauthored text, use `kind: \"scramble\"` with a fixed `seed` and optional\n`charset`. These operate over the animation window, so a held final frame\nshows the finished value.\n\n```json\n{\"id\": \"count-in\", \"role\": \"in\", \"preset\": \"fade\", \"durationMs\": 900,\n \"textAnimator\": {\"kind\": \"ticker\", \"from\": 1, \"to\": 7,\n  \"padTo\": 2, \"suffix\": \" \u002F 07\"}}\n```\n\nFor unit-by-unit motion, set `stagger.unit` to `character`, `word`, or `line`\nand give it `offsetMs`. With a text stagger, `styleTracks` can target\n`glyph.color`, `glyph.blurPx`, or `glyph.trackingPx`. The colour uses CSS\ncolour values; blur and tracking use sequence pixels. Use `text.color` or\n`text.fill.stops.0.color` for a whole line. A text fill gradient also exposes\n`text.fill.angle` and stop offsets. The target must refer to an existing\nstyle field; `text.color` is hidden while a gradient fill is set.\n\nTo lay a title along a curve, set `textStyle.path` to an SVG path in\nnormalized canvas coordinates. This places the baseline on the path. It does\nnot make each character travel along it. Shape and mask paths can morph through\n`shape.d` and `mask.d` style tracks when both paths have matching commands and\npoint counts. Use `followPath` when the whole clip should move along a path.\n\n`edit_timeline`'s `animate_clip` input accepts presets and custom numeric\ncurves, but does not accept `textAnimator` or `styleTracks`; those fields are\ndropped from that call. To author them, read the current document and use\n`set_timeline_document` with the animation fields in the clip. That call\nvalidates the complete document and snapshots the previous state. Preserve\nthe other tracks and clips from the document. `timeline-edit-ops` owns the full\ntool contract.\n\n## Build and verify\n\nAdd separate overlay and subtitle tracks. For each map item, add scrim before text, apply the locked tier style, then animate it with that tier’s entry and exit preset. No hard cut-on. Use stagger only for tone-appropriate kinetic captions. Keep all text within safe margins and clear of faces and product moments.\n\nTwo facts about stacking decide whether the text is seen at all. The lowest track `index` draws on top, so the scrim's track index sits between the picture's and the text's — picture, scrim, text, in descending index. And word-level captions generated from a voiceover clip composite above every real track regardless of where that clip sits, so no title can cover them: time a T1 around the narration rather than over it.\n\nVerify in two passes, and they answer different questions. `validate_timeline` reads the document: `text_illegible` (size, or under 3:1 contrast against the text's own `background` plate or a full-frame shape behind it), `font_not_portable`, `stagger_compressed`, `animation_exceeds_clip`, overlaps, and clips shorter than a frame. Its contrast check refuses to guess — a translucent scrim, gradient type or a plate it cannot prove is behind the text produces no finding — so a silent pass is not a pass. Then `preview_timeline_frame` at each item's entry midpoint, a held moment, and its exit: that is where text over a busy plate, a scrim covering a face, or a caption still finishing when its clip ends shows up. Re-read the map against the frames: timing, reading floors, scrim ordering, one CTA at the end. Then render with `render_timeline` before calling the layer done, as `timeline-edit-ops` § The render loop describes: the frames show one timecode, the render shows the timing at speed.\n",{"name":5,"featured":40,"description":7},true,"main","c7226baa82daca42a19a5855c116544f97aa8bac","packages\u002Fsystem-skills\u002Fcaption-titles",91,"https:\u002F\u002Fgithub.com\u002Fnodetool-ai\u002Fnodetool","https:\u002F\u002Fnodetool.ai\u002F","https:\u002F\u002Fgithub.com\u002Fnodetool-ai","No-code AI development","2026-11-15 03:27:49",{"source":8,"skillName":5,"commands":51,"prompt":61,"zipAvailable":40},[52,55,58],{"tool":53,"command":54},"npx","npx skills add nodetool-ai\u002Fnodetool --skill caption-titles",{"tool":56,"command":57},"bunx","bunx skills add nodetool-ai\u002Fnodetool --skill caption-titles",{"tool":59,"command":60},"pnpm","pnpm dlx skills add nodetool-ai\u002Fnodetool --skill caption-titles","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fnodetool-ai\u002Fnodetool\u002Fblob\u002Fmain\u002Fpackages\u002Fsystem-skills\u002Fcaption-titles\u002FSKILL.md",[],[64,73,108,136,151,167],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":68,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":72},"01M742MX3Y2ZYK884ZXTRFKB9P","humanizer","Rewrite AI-sounding text so it reads like the writer without changing what it says.\nUse when editing or reviewing prose for AI tells: not-X-but-Y contrasts, one-line\nclosers, staged openers, forced triads, dashes everywhere, inflated claims, sales\nlanguage, stock AI words, bold labels, or filler.","MIT","https:\u002F\u002Fgithub.com\u002Fnodetool-ai\u002Fnodetool\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fhumanizer\u002FSKILL.md",[],[],"2026-11-11 15:11:14",{"skillNo":74,"name":24,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":88,"publishedAt":35},"01M6BY4D93R0Q9400ZHJ04DXP1","Use the NodeTool MCP server to build, validate, run, and debug visual AI workflows, and to work with assets, collections, and jobs. Use when the user mentions NodeTool or asks for a workflow graph, a node, or a media generation run on their NodeTool server.","https:\u002F\u002Fgithub.com\u002Fnodetool-ai\u002Fnodetool\u002Fblob\u002Fmain\u002Fplugins\u002Fchatgpt\u002Fnodetool\u002Fskills\u002Fnodetool\u002FSKILL.md",[78,83],{"categoryNo":79,"categoryName":80,"taxonomyType":81,"taxonomyTypeDesc":82},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",{"categoryNo":84,"categoryName":85,"taxonomyType":86,"taxonomyTypeDesc":87},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[24,89,90,91,92,93,94,95,96,25,97,33,98,99,100,101,102,103,104,105,106,107],"MCP","Media","workflows","when","generation","media generation","with","visual","collections","node","work","debug","graph","validate","assets","run","server","mcp server","workflow",{"skillNo":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":117,"publishedAt":35},"01M6BY4AEB05ZPBRVD078ATR2H","wan-2-6-prompting","Prompt Alibaba's Wan 2.6 video — text-to-video with a global style line plus timing-bracketed shots, and image-to-video that describes only what changes over time. Covers the shot-mode switch per provider, the prompt budget, negative prompts, motion intensity wording, audio input and prompt expansion. Use whenever the model id names a Wan 2.6 video route (alibaba\u002Fwan-2.6\u002Ftext-to-video, alibaba\u002Fwan-2.6\u002Fimage-to-video, wan-video\u002Fwan-2.6-t2v, wan-video\u002Fwan-2.6-i2v, wan-video\u002Fwan2.6-i2v-flash) on generate_video, animate_image or a TextToVideo node. Not for Wan 2.5 or 2.7, or the Wan 2.6 image routes.","https:\u002F\u002Fgithub.com\u002Fnodetool-ai\u002Fnodetool\u002Fblob\u002Fmain\u002Fpackages\u002Fsystem-skills\u002Fwan-2-6-prompting\u002FSKILL.md",[114],{"categoryNo":115,"categoryName":116,"taxonomyType":81,"taxonomyTypeDesc":82},"01JBSEEDCAT000000000000016","图像与多媒体",[118,119,120,121,122,123,124,98,125,126,127,128,129,130,131,22,132,23,133,134,135],"prompting","wan 2 6 prompting","line","expansion","input","image-to-video","text-to-video","route","only","mode","time","flash","Budget","generate","image","model","Audio","Video",{"skillNo":137,"name":138,"nameZh":6,"description":139,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":140,"categories":141,"keywords":144,"publishedAt":35},"01M6BY47T4748ZG5ZMTAR97ZWZ","video-workflow","Build a reusable NodeTool video workflow for batches or repeated inputs. For a single finished piece, use a storyboard skill.","https:\u002F\u002Fgithub.com\u002Fnodetool-ai\u002Fnodetool\u002Fblob\u002Fmain\u002Fpackages\u002Fsystem-skills\u002Fvideo-workflow\u002FSKILL.md",[142,143],{"categoryNo":115,"categoryName":116,"taxonomyType":81,"taxonomyTypeDesc":82},{"categoryNo":79,"categoryName":80,"taxonomyType":81,"taxonomyTypeDesc":82},[107,145,135,146,147,148,149,25,150,24,33],"video workflow","reusable","storyboard","build","batches","single",{"skillNo":152,"name":153,"nameZh":6,"description":154,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":155,"categories":156,"keywords":158,"publishedAt":35},"01M6BY4587N2SYN315SXGEMZC3","video-clone","Analyze a reference video and recreate its shot structure with a new product or cast in NodeTool.","https:\u002F\u002Fgithub.com\u002Fnodetool-ai\u002Fnodetool\u002Fblob\u002Fmain\u002Fpackages\u002Fsystem-skills\u002Fvideo-clone\u002FSKILL.md",[157],{"categoryNo":115,"categoryName":116,"taxonomyType":81,"taxonomyTypeDesc":82},[159,160,135,95,161,162,24,163,164,165,166],"clone","video clone","cast","new","analyze","product","structure","reference",{"skillNo":168,"name":169,"nameZh":6,"description":170,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":171,"categories":172,"keywords":174,"publishedAt":35},"01M6BY4257C2KQYYMD9EK6DK8E","video-audio-continuity","Keep sound continuous across a multi-scene piece cut from generated video — why one clip per scene hard-cuts the audio at every boundary, when to write all the scenes into a single generation instead, the sound-design vocabulary that survives a provider's copyright filter, and how to check the length, the aspect ratio and the mix of what came back. Use when a piece has more than one scene and the video model writes its own audio (Seedance 2, Veo 3, MiniMax H3, Kling 2.6 and later), or when a cut's sound drops out at the shot changes.","https:\u002F\u002Fgithub.com\u002Fnodetool-ai\u002Fnodetool\u002Fblob\u002Fmain\u002Fpackages\u002Fsystem-skills\u002Fvideo-audio-continuity\u002FSKILL.md",[173],{"categoryNo":115,"categoryName":116,"taxonomyType":81,"taxonomyTypeDesc":82},[175,135,134,176,177,178,179,180,181,182,183,184,185,92,186,187,133,188,189,190,191],"video audio continuity","continuity","write","why","back","veo 3","at","cut","later","across","filter","generated","how to","mix","design","boundary","how"]