Agent skill

Video Audio Continuity

by nodetool-ai in nodetool-ai/nodetool

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…

AGPL-3.0Auto-check passedMedia & Creative

Install Video Audio Continuity

skills CLI
$ npx skills add nodetool-ai/nodetool --skill video-audio-continuity -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install nodetool-ai/nodetool video-audio-continuity --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/nodetool-ai/nodetool.git skills-src && mkdir -p .claude/skills && cp -r skills-src/packages/system-skills/video-audio-continuity .claude/skills/video-audio-continuity && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
video-audio-continuity
GitHub stars
560
Token cost
~1.2k tokens
SKILL.md length
684 words
Files
1
Skills in repo
127
Repo updated
First seen
Licence
AGPL-3.0

At a glance

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…

  • A piece has more than one scene and the video model writes its own audio (Seedance 2
  • SKILL.md covers The rule, A sound brief that is not…, Check what came back and Where the rest picks up
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Kling 2.6 and later)

What it does

Video Audio Continuity is an agent skill from nodetool-ai/nodetool. 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…

Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Media & Creative, covering AI video generation and Music and audio generation. It works with Google Veo, MiniMax and Seedance. The repository describes itself as: Agent-first Creative Workspace. The licence is AGPL-3.0.

When your agent uses it

  • A piece has more than one scene and the video model writes its own audio (Seedance 2
  • Kling 2.6 and later)
  • A cuts sound drops out at the shot changes

Example prompts

  • “/video-audio-continuity”

What it can do on your machine

Read from SKILL.md and the folder at commit 339f069. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Video Audio Continuity loads about 1.2k tokens when it runs. Until then it costs about 141 tokens; SKILL.md has 684 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~141
When it runs · the whole SKILL.md, loaded when a task matches
~1.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from nodetool-ai/nodetool at commit 339f069, republished under its AGPL-3.0 licence (© nodetool-ai). 684 words, ~1,229 tokens.

Download SKILL.mdSave it as .claude/skills/video-audio-continuity/SKILL.md (or your agent's skills folder).
name
video-audio-continuity
description
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.
featured
true

One clip, one bed

A generated clip carries its own audio, and that audio starts and stops at the clip's own edges. So the obvious build — one generated clip per shot, laid end to end — hard-cuts or drops to silence at every boundary. Stills and contact sheets never show it; it only exists on playback, and it is the most common audio defect in a multi-scene piece.

The rule

When sound has to carry across the scene changes, generate one clip holding all the scenes.

  • One generate_video call, the scenes written as "cut to" beats inside the prompt, and one continuous audio brief across the whole thing.
  • Lay that clip under the sequence as the base bed and time the type and graphics to it.
  • Use a model line that writes native audio, and load its prompting skill first: seedance-2-prompting (its JSON beat sheet is built for exactly this — global audio_note, one audio line per beat), veo-3-prompting, minimax-h3-prompting, kling-video-prompting.

Separate per-shot clips are right in two cases:

  • the piece is silent, or
  • the continuity comes from a track you add yourself — narration from generate_speech (or voice_script_lines, which voices every line of a board's script in one call), a bed from generate_music — on its own timeline track. Then the visual beds can be separate and the shots are muted under it. elevenlabs-audio-prompting directs the voice and the music plan, stable-audio-prompting the bed and any effects; a bed generated with a stated BPM is a bed whose grid beat-sync-editing already knows.

Two video lines force the second build: Wan 2.6 takes an audio file as input but writes none, and Hailuo has no native audio at all, so a piece on either gets its sound from a track of your own.

On a storyboard this means one shot, not seven. A board whose shots each render their own native-audio clip cannot be assembled into a continuous mix; decide which of the two builds you are doing before the first render, because the fix afterwards is a re-render. The board skills (commercial-beat-sheet, trailer-template, explainer-storyboard, music-video-treatment) each say which build they default to; the sound brief itself goes into the shot's motion and action, the only fields the clip prompt is built from.

Show full SKILL.md (315 more words)Show less

A sound brief that is not refused

Providers copyright-filter the generated audio track, and a brief asking for a "swell", a "chord", a "score", a "soundtrack" or a named musical genre can come back blocked — failing the whole render, not just the audio. For an underscore, describe sound design instead:

  • Hum, digital pulses, ticking, airy whooshes, risers, sparkle textures, one low sub-bass boom.
  • Close with "no music, no melody, no song, no voice".
  • Put each transition in the sound design — a whoosh on every "cut to" — not in a musical cue. A cue tends to restart at the cut, which is the discontinuity you are avoiding.

Dialogue is not affected by this: quoted lines are the model's own voice track, and the model-line skill says how to write them.

Check what came back

  • Length. duration_seconds is honoured loosely and clamped to the lengths a model supports. Measure with analyze_video before cutting to it.
  • Frame. Aspect ratio is not guaranteed — an image-to-video route often ignores a 9:16 source and emits 16:9. analyze_video reports it; fix it with an ffmpeg crop to the target frame before compositing, not after.
  • The mix. Judge it with understand_video (Gemini gets the audio; every other vision model is sent silent stills), analyze_audio for the levels, and detect_video_scenes to confirm the cuts landed where the beats said. Never from a contact sheet.
  • The file. Build on a stored asset. generate_video saves its result; probing a generation node with invoke_node hands back whatever the node returned, which can be a run-local path that is gone by the time you assemble.

Where the rest picks up

motion-graphics carries the timeline op contract for laying the bed and muting shot audio under a narration track. beat-sync-editing sits the cuts on that bed once it exists, and caption-titles times the type to it — a title card is never rendered into the clip, whichever build you chose.

© nodetool-ai, AGPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in packages/system-skills/video-audio-continuity of nodetool-ai/nodetool.

Open the folder on GitHubat commit 339f069

Compare with similar skills

Video Audio Continuity next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Video Audio Continuity compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Video Audio Continuity this skillnodetool-ai/nodetool560—~1.2kAutomated safety check: PassAGPL-3.0
Video PromptingSquare-Zero-Labs/video-prompting-skill182—~1.9kAutomated safety check: PassApache-2.0
Higgsfield AudioOSideMedia/higgsfield-ai-prompt-skill713—~11kAutomated safety check: PassMIT
Higgsfield ModelsOSideMedia/higgsfield-ai-prompt-skill713—~7kAutomated safety check: PassMIT
HiggsfieldOSideMedia/higgsfield-ai-prompt-skill713—~9.1kAutomated safety check: PassMIT
VideoNexus-JPF/note-companion8703 repos~3.6kAutomated safety check: PassMIT

Similar skills

  • Video Prompting

    Square-Zero-Labs/video-prompting-skill

    Draft and refine prompts for video generation models (including text-to-video, image/keyframe-to-video, and reference-driven generation), and create character-sheet prompts for image models when the…

    182 GitHub stars~1.9k tokensUpdated 1 mo ago
    Media & CreativeAuto-check passed
  • Higgsfield Audio

    OSideMedia/higgsfield-ai-prompt-skill

    A skill your agent uses when the user asks about audio in Higgsfield videos, needs to add dialogue or lip-sync, wants sound effects or ambient sound in generated video, asks about music or BGM in…

    713 GitHub stars~11k tokensUpdated 13 days ago
    Media & CreativeAuto-check passed
  • Higgsfield Models

    OSideMedia/higgsfield-ai-prompt-skill

    A skill your agent uses when the user asks which model to use, wants to compare models, or needs guidance on selecting between Kling, Wan (incl.

    713 GitHub stars~7k tokensUpdated 13 days ago
    Media & CreativeAuto-check passed
  • Higgsfield

    OSideMedia/higgsfield-ai-prompt-skill

    A skill your agent uses whenever the user asks anything about Higgsfield AI — writing or refining video/image prompts, choosing a model (Kling, Veo, Wan, Seedance, Minimax Hailuo, DoP, Soul, Nano…

    713 GitHub stars~9.1k tokensUpdated 13 days ago
    Media & CreativeAuto-check passed
  • Video

    Nexus-JPF/note-companion

    When the user wants to create, generate, or produce video content using AI tools or programmatic frameworks.

    870 GitHub starsUsed in 3 repos~3.6k tokens
    Media & CreativeAuto-check passed
  • AI Video Gen

    calesthio/OpenMontage

    Generate AI videos from text prompts using multiple provider gateways.

    66k GitHub stars~3k tokensUpdated 7 days ago
    Media & CreativeAuto-check passed

More from nodetool-ai/nodetool

All 127 skills in this repo
  • Beat Sync Editing

    nodetool-ai/nodetool

    Cut a NodeTool timeline to music and shape its pacing — detect the beat grid, place cuts on phrases, pick a cut type, build speed ramps with time remap, and give the piece an arc.

    560 GitHub stars~2.6k tokensUpdated today
    Auto-check passed
  • Caption Titles

    nodetool-ai/nodetool

    Add and animate a consistent text layer on an existing NodeTool timeline.

    560 GitHub stars~1.9k tokensUpdated today
    Auto-check passed
  • Color Motion

    nodetool-ai/nodetool

    Choose and animate colour on a NodeTool timeline, including shape and text gradients, colour grades, 3D LUTs, and dither.

    560 GitHub stars~2.3k tokensUpdated today
    Auto-check passed
  • Commercial Beat Sheet

    nodetool-ai/nodetool

    Write a shootable, precisely timed commercial beat sheet and store it as a NodeTool storyboard, with a consistent entity roster behind every shot.

    560 GitHub stars~4.6k tokensUpdated today
    Auto-check passed
  • Elevenlabs Audio Prompting

    nodetool-ai/nodetool

    Direct ElevenLabs speech, dialogue, sound effects and music — the bracketed audio tags v3 acts on and why the voice decides whether a tag lands, stability as the delivery dial, punctuation instead…

    560 GitHub stars~1.9k tokensUpdated today
    Auto-check passed
  • Frame Composition

    nodetool-ai/nodetool

    Stage the frame on a NodeTool timeline — grids, focal placement, safe areas per aspect ratio, depth layers and parallax, camera moves, and where elements enter and leave.

    560 GitHub stars~3.5k tokensUpdated today
    Auto-check passed

Questions about Video Audio Continuity

What does Video Audio Continuity do?

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…. Video Audio Continuity is an agent skill from nodetool-ai/nodetool. 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.

When should I use Video Audio Continuity?

Video Audio Continuity fits situations like: A piece has more than one scene and the video model writes its own audio (Seedance 2; kling 2.6 and later); A cuts sound drops out at the shot changes.

How do I install Video Audio Continuity in Claude Code?

Run `npx skills add nodetool-ai/nodetool --skill video-audio-continuity -a claude-code`. Or copy the skill folder (packages/system-skills/video-audio-continuity in nodetool-ai/nodetool) into .claude/skills/video-audio-continuity in your project. Claude Code loads it when a task matches its description.

How do I install Video Audio Continuity in Codex?

Run `npx skills add nodetool-ai/nodetool --skill video-audio-continuity -a codex`. Or copy the skill folder (packages/system-skills/video-audio-continuity in nodetool-ai/nodetool) into .agents/skills/video-audio-continuity in your project. Codex loads it when a task matches its description.

Can I use Video Audio Continuity in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add nodetool-ai/nodetool --skill video-audio-continuity -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/video-audio-continuity, .gemini/skills/video-audio-continuity, .github/skills/video-audio-continuity and .opencode/skills/video-audio-continuity in your project.

What does Video Audio Continuity need to run?

SKILL.md names no scripts, command-line tools or credentials: Video Audio Continuity is instructions for the agent only.

Does Video Audio Continuity access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Video Audio Continuity safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Video Audio Continuity use?

Video Audio Continuity is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Video Audio Continuity use?

About 1.2k tokens (SKILL.md is roughly 4.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Video Audio Continuity?

Skills that share tags, products or a category with Video Audio Continuity: Video Prompting (Square-Zero-Labs/video-prompting-skill, 182 stars), Higgsfield Audio (OSideMedia/higgsfield-ai-prompt-skill, 713 stars), Higgsfield Models (OSideMedia/higgsfield-ai-prompt-skill, 713 stars) and Higgsfield (OSideMedia/higgsfield-ai-prompt-skill, 713 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Video Audio Continuity?

nodetool-ai (a GitHub organization) maintains it in nodetool-ai/nodetool, which has 560 GitHub stars. The repository holds 127 skills in this directory. The repository was last updated on October 10, 2026.

Source: nodetool-ai/nodetool on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.