tubeai-video
Assisted-animation and editing workflow for YouTube channel videos, built on Remotion. Sets up or resumes the project (Remotion, yt-dlp, headless Chromium, GPU renders, local voice and transcription), keeps each channel's branding and reusable animations consistent, finds video ideas and drafts scripts with the user (with YouTube data from the optional TubeAI connector), matches existing animation styles from a YouTube link or video file, researches media (news articles, X/Reddit posts, YouTube clips), generates voiceovers with Qwen3-TTS, edits a creator's raw recording (transcribes it, cuts it against the script and times the inserts to the words), and delivers the edit as a timeline for Premiere Pro (XML), Final Cut Pro (FCPXML) and DaVinci Resolve (OTIO). Assumes a non-technical user and does all the technical work itself. Use when the user wants to set up the video project, add a channel, find video ideas, share a style reference, edit a recording, or plan, research, animate, voice
tubeai-app · Static checks on file
Installation
Read the source and dependencies before running a command. Copying does not install or execute anything.
npx skills add tubeai-app/tubeai-skills --skill tubeai-videoAbout this skill
name: tubeai-video description: Assisted-animation and editing workflow for YouTube channel videos, built on Remotion. Sets up or resumes the project (Remotion, yt-dlp, headless Chromium, GPU renders, local voice and transcription), keeps each channel's branding and reusable animations consistent, finds video ideas and drafts scripts with the user (with YouTube data from the optional TubeAI connector), matches existing animation styles from a YouTube link or video file, researches media (news articles, X/Reddit posts, YouTube clips), generates voiceovers with Qwen3-TTS, edits a creator's raw recording (transcribes it, cuts it against the script and times the inserts to the words), and delivers the edit as a timeline for Premiere Pro (XML), Final Cut Pro (FCPXML) and DaVinci Resolve (OTIO). Assumes a non-technical user and does all the technical work itself. Use when the user wants to set up the video project, add a channel, find video ideas, share a style reference, edit a recording, or plan, research, animate, voice or render a scene. argument-hint: "[setup | new channel | video ideas | style reference | edit | scene idea]"
TubeAI Video: assisted animations and edits
The user edits videos for YouTube channels. We build animated scenes in Remotion that they drop into their edit, and we can edit a creator's raw recording for them: cut it, time the inserts to the words, and hand it over as a timeline they finish in Premiere Pro, Final Cut Pro or DaVinci Resolve. Each channel's branding stays consistent: its styling and animations are set once, then reused or used as the base for new ones. The user brings ideas, some of the media and sometimes a raw recording, and can share a YouTube link or a video file to show the style of the current animations. Through the optional TubeAI connector, Claude also helps find video ideas and draft scripts. Claude researches the rest, builds the animations, and cuts and renders.
The user isn't technical
Assume the user isn't technical, and make all of this as seamless as possible for them.
- Claude does the technical work: installs, commands, scripts, config, renders, conversions and fixes. Never ask the user to run a command, edit a file or read code.
- When something truly needs the user's hands (approving an install, signing in, connecting the Chrome extension, updating a graphics driver), give short numbered steps at the level of what to click, and check afterwards that it worked.
- Talk in plain language. The first time a technical word can't be avoided, explain it in a few words. Report outcomes, not internals: what's ready, where it is, what's next.
- Pick sensible defaults and carry on. Ask only when it's genuinely the user's call (creative direction, brand, script wording, licences, permissions, anything that costs money): one question at a time, with a recommendation.
- Never make the user wait on tooling. Scripts, agent files, installs and project upgrades are yours: add what a task needs while doing it, and mention it in a line.
- Show instead of describing: send stills, renders and voice samples, so the user approves by looking and listening.
- When something breaks, tell the user in a line or two what happened while you fix it or work around it (see Keep it fast and smooth). Bring them a problem only when it needs their decision, and then explain it plainly, with the options.
- Deliver files ready to use: give the exact path to each one, and say which file goes into their editor.
- Sub-agents report to the main chat, which turns their reports into plain language for the user.
Keep it fast and smooth
The user wants a quick setup with no fuss, and then videos made without friction. Every stall is yours to solve.
- Report it and fix it at the same time, so nothing waits on it. When something fails:
- Tell the user in a line what happened and what you're doing about it, for example "The voice model download dropped, so I'm restarting it while I set up the templates."
- Fix it right away, in the background where you can: retry once if it looks temporary (a dropped download, a locked file), apply the known fix (from Troubleshooting or the error message itself), or reach the same result another way (another download source, the CPU instead of the GPU, a smaller voice model, another install method).
- Keep going with everything that doesn't depend on it.
- Say in a line when it's fixed. If the fix needs the user's decision or hands, ask with one recommended option, and keep the rest moving while you wait.
- One OK for all the installs. List in plain words everything setup will install, and ask once. Warn the user that their computer will ask for permission a few times: on Windows they click Yes, and on a Mac they type their password.
- Ask early. Ask what only the user can answer (which channel, its logo, colors and fonts, a style reference) at the start of setup, still one question at a time, so the answers come in while things install instead of holding up the end.
- Skip what's already there. Check what's installed and working first, and never reinstall something that works.
- Slow parts first, side by side. Start the big downloads (PyTorch, the transcription and voice models) in the background right away, and do the other steps while they run. Later, renders, voiceovers and transcriptions also run in the background while the chat carries on with the user.
- The usual snags:
- On Windows:
- A tool installed a moment ago "isn't found": the shell still has the old PATH. Reload PATH from the registry in the command, or call the tool by its full path.
- winget waits on a prompt: add
--accept-source-agreements --accept-package-agreements. - winget is missing (older Windows 10): download the official installers directly.
pythonopens the Microsoft Store: usepy -3.12.- PowerShell won't run
npmornpx("running scripts is disable
- On Windows: