SkillAgentSearch skills...

vaibhav-video-editor

Full start-to-finish video editing that runs every installed video skill as one pipeline. Cuts silences and retakes, plans the edit from the transcript, then adds captions, motion graphics, face-tracked effects, transitions, camera moves, b-roll, sound effects and music, checks its own work and expo…

Install / Use

npx skills add V413havai/vaibhav-video-editor

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

73/100

Category

Automation

Supported Platforms

Gemini CLI

Our assessment of vaibhav-video-editor

vaibhav-video-editor scores 73/100 on our quality scale, 2561st of 2,771 Automation skills we index.

Its SKILL.md is 24 KB long, well organised into 14 sections and no code examples: a thorough specification that gives an agent plenty to work with.

It has no GitHub stars yet, so there is no community track record; judge it on its content.

Substance
30/30
Structure
13/20
Description
15/15
Adoption
0/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated 15 days ago, so vaibhav-video-editor is actively maintained.
  • No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
  • Its trust signals score 80/100, with 2 cautions from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

vaibhav-video-editor compared with similar skills

All 4 of these similar skills score higher than vaibhav-video-editor; compare them before choosing.

SkillScoreStarsUpdatedFormat
vaibhav-video-editor (this skill)by V413havai73015d agoSKILL.md
Agent-Reachby Panniantong100113.3k12d agoCLAUDE.md
rufloby ruvnet10082.1ktodayCLAUDE.md
Claude-Code-Game-Studiosby Donchitos10040.2k10d agoCLAUDE.md
Scraplingby D4Vinci100104.4k2d agoMCP Server

Frequently asked questions

How do I install vaibhav-video-editor?
Run npx skills add V413havai/vaibhav-video-editor. The install tabs above show the steps for each supported agent.
Which AI agents does vaibhav-video-editor work with?
It is written for Gemini CLI, as a SKILL.md file. Other agents that read the same format can often use it too.
Is vaibhav-video-editor safe to use?
It declares no license and scores 80/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is vaibhav-video-editor still maintained?
The repository was last updated 15 days ago, so vaibhav-video-editor is actively maintained.

name: vaibhav-video-editor description: Full start-to-finish video editing that runs every installed video skill as one pipeline. Cuts silences and retakes, plans the edit from the transcript, then adds captions, motion graphics, face-tracked effects, transitions, camera moves, b-roll, sound effects and music, checks its own work and exports the final MP4. Routes each beat to the right tool (awa-video-reel, the 45-effect engine, Brand Nat codes, HyperFrames, Remotion, the Video Editor plugin, MultiCam shot) and follows the saved style (my-video-style). Also makes fully animated videos from a script with an AI voiceover (ElevenLabs, Google Gemini, HeyGen or free Kokoro). Use when someone types /vaibhav-video-editor, says "edit this video start to finish", "do the full edit", "make this a finished reel", "edit it in Nick style", "make an animated video with a voiceover", or asks for an edit combining cuts, motion graphics, effects, transitions and sound. For a single effect only, use /effects instead.

Vaibhav AI Video Editor

You are the director and the editor. The user hands over raw footage and a goal; you deliver a finished, checked video. You decide which tool does each job, show one plan, wait for a yes, then do every technical step yourself.

Most users are not technical. Keep messages short and visual, never ask them to run commands, and never install anything without asking first.

This skill does not replace the other video skills. It runs them in the right order and gives them one shared plan. Read the parts of their SKILL.md files that you need before you call their scripts, and follow their rules (flags, file formats, gotchas). Paths that start with references/ or scripts/ are inside this skill's folder, unless the sentence names another skill ("its scripts/render.sh" means that skill's folder). scripts/preflight.sh prints where every other skill lives. Use absolute paths in commands.

The pipeline at a glance

| # | Stage | Tools | Output | |---|---|---|---| | 0 | Preflight | scripts/preflight.sh | what's installed, what's missing | | 1 | Brief and style | my-video-style or references/house-style.md | the edit brief | | 2 | Prepare | transcribe, scripts/check_words.py, fix names, find faces | work/NAME-words.json, beat stills | | 3 | Clean cut | silences, fillers, retakes | work/NAME-cut.mp4 | | 4 | Website b-roll question | awa-video-reel step 2 | yes + link, or none | | 5 | Storyboard (approval gate) | references/beat-map.md, Brand Nat codes | plan table + style card | | 6 | Build | engine A, B or C (below) | picture with graphics | | 7 | Sound | awa mixer or scripts/sound_mix.py | final mix at -14 LUFS | | 8 | Quality check | references/quality-check.md | fixes, then a final render | | 9 | Deliver | | final MP4, no-music copy, credits, caption |

Never skip stage 5's approval, and never skip stage 8. No camera footage? Use Voiceover mode (near the end): script, AI voice, then a fully animated video.

Stage 0: Preflight

Run bash scripts/preflight.sh. It prints one line per tool and component (OK, MISSING or OPTIONAL) and the paths it found. Keep the paths for later stages.

  • Required: ffmpeg + ffprobe, Python 3, and at least one engine (awa-video-reel, the Video Editor plugin, or HyperFrames).
  • Missing a required tool: say what it is for in one line and offer to install it. Follow the installing skill's own setup (awa-video-reel/scripts/setup.sh, effects/scripts/setup.sh, /video-editor:start, or brand-nat-styles' one-time setup, which avoids Homebrew for non-technical users).
  • Missing an optional component: carry on without it and use the fallback in references/toolkit.md. Mention it once at the end ("Install X to get Y next time").
  • Skip preflight if it already passed in this session.

Stage 1: Brief and style

Load the style first. If ~/.claude/skills/my-video-style/SKILL.md exists, read it in full: it is the user's own taste and it wins over every default here. If it names a skill that isn't installed, use the nearest tool from this toolkit and say so once. If there is no saved style, use references/house-style.md and offer /video-editor:style at the end.

Who wins when rules disagree: what the user says in this chat > a style preset they picked for this video > my-video-style > the Brand Nat codes they picked > the engine skill's defaults > references/house-style.md. A preset sets the look; their saved style still decides anything the preset doesn't cover (spellings, handle, export settings).

Style presets live in references/styles/. Read the whole file when the user names one:

  • kinetic-promo.md: a clean, quick faceless reel from an AI voice: big kinetic type with a yellow key word, motion graphics that act out each line, zoom-through transitions, punch-ins, a drifting dot grid, a comment CTA card. The default look for voiceover mode when the user gives no other style. Worked example: examples/kinetic-promo/.
  • nick-saraev.md: Nick Saraev's fast AI-tool list reels (split card, full face and full-screen stat layouts, glowing browser cards, blue keyword captions, pause-free pace, comment-keyword CTA). Triggers: "Nick style", "Nick Saraev style", "edit like Nick". Has a classic 2025 variant.

Then ask only what you don't already know, in one short message:

  • Which video? (a path, or drag it in; several clips are joined in name order). No footage, or they want an animated video with an AI voice: switch to Voiceover mode below.
  • Where is it going and what shape? (default from the style: usually 9:16 for Reels, TikTok and Shorts)
  • In one line, what is it about, and what should the viewer do at the end?
  • Style: their saved style, a style preset (references/styles/, for example Nick style), Brand Nat codes (offer to open the guide: brand-nat-styles/guide/index.html), a vibe in words, or "you pick".
  • Look: clean or cinematic. Music: a mood or none. Handle for an end card, if any.
  • Anything to feature (logo, screenshots, their own screen recording) and names that must be spelled exactly.

If they're in a hurry, use the style and defaults and go.

Project folders. Work inside a project folder: originals in raw/ (never modified), assets in assets/, working files in work/, finished videos in exports/. Name every working file after the video (raw/beach-day.mov → NAME beach-day, work/beach-day-words.json). Create the folders if they're missing.

Stage 2: Prepare

  1. Several clips: join them first (Video Editor plugin join.py, or ffmpeg concat after matching size, fps and audio). Use the joined file from here on.
  2. Probe: size, shape, fps, duration, audio, whether a person is on camera. awa-video-reel's scripts/probe.py also finds the median face box.
  3. Transcribe with word timings. Use the best tool available, in this order: the user's style or memory (it may name a working whisper setup and flags, for example for mixed Hindi and English), the Video Editor plugin's transcribe.py --vocab "NAMES", the effects engine's words.py, then npx hyperframes transcribe audio.mp3 --json. Never run a tool that writes next to its input (the effects engine's words.py writes <video>.words.json and may install its own transcriber) on a file in raw/: copy it to work/ first, and ask before anything installs.
  4. Check the timings against the audio: python3 scripts/check_words.py <video> work/NAME-words.json. Whisper word times drift after music, applause or a stretch with no talking (turbo models by a second or more), and whisper.cpp without alignment gives coarse word times. For each flagged stretch, re-transcribe just that stretch cut on its speech gaps, or snap the first word after each gap to where the speech starts. Every visual is timed to these words, so fix them before planning.
  5. Read the whole transcript. Fix misheard names and brands (for example "cloud code" → "Claude Code") everywhere you'll use the words.
  6. Find the face in every shot. Make a still per planned beat with a 10-row grid (ffmpeg -ss <t> -i <video> -frames:v 1 -vf "scale=216:384,drawgrid=w=216:h=38.4:c=red@0.5", then tile them) and note where faces sit. In multi-scene or AI-generated videos the face moves between shots (top of frame in one, middle in the next, a row of faces on a stage), so each graphic is placed for its own shot, not for the whole video. Note bright or white areas too: white text over them needs a dark backing.
  7. No speech or no audio: no captions and no silence cuts. Pick moments by looking at frames, and build the edit from music, titles and motion.

Stage 3: Clean cut

The rough cut comes before any graphics, so every later time sits on the final timeline.

  1. Find silences and fillers: the Video Editor plugin's silences.py --words work/NAME-words.json --out work/NAME-keep.json, with the style's settings (--min-silence, --pad-before, --pad-after, --remove-fillers). Without the plugin, use ffmpeg silencedetect (about -35 dB, 0.35 s) plus the transcript gaps.
  2. Retakes: read the transcript for repeated or restarted lines. Keep the last complete take, drop the earlier ones and any "wait, let me redo that".
  3. Respect a rough cut. If the user already cut the video (or their style says they send rough cuts timed to screen recordings), only trim silences where it won't break a transition, a scroll or a screen recording. Ask when unsure.
  4. Render the cut: python3 scripts/apply_keep.py <video> work/NAME-keep.json work/NAME-cut.mp4. It cuts with short audio fades so the joins don't click. If nothing needs cutting, skip it and use the original: say so in the plan.
  5. Transcribe work/NAME-cut.mp4 again, or shift the word times with the -timemap.json that apply_keep.py writes next to the cut. Every time from here on is on the cut's timeline.
  6. Over 60 s and meant for a short: offer the strongest 60 s from the transcript, or /video-editor:clips to make several shorts.

Stage 4: Ask about websites

If the video names a website, app or online tool they show or tell people to use, ask before planning, exactly as awa-video-reel step 2 describes: offer recorded b-roll of using it start to finish, ask for the link, never guess a URL, and offer the Claude Code follow-through when the video says to paste a prompt somewhere. Their own screen recording is always an option. No website in the video: don't ask.

Stage 5: Storyboard (approval gate)

Plan the whole edit before rendering anything. Read references/beat-map.md (which visual fits which moment, and how every Brand Nat code is built) and references/transitions-sound.md.

  1. Edit thesis: one line on what this edit must do for the message.

  2. Sections: hook (first 1 to 3 s), setup, each point or proof, payoff, call to action.

  3. Choose the engine (more in references/toolkit.md):

    • A. Reel engine (awa-video-reel): clips up to 60 s, talking head or not. The default when it's installed. Effects, captions, cards, camera moves, website b-roll, Remotion intro and end cards, music and sound effects in one render. It renders at the source fps up to 30.
    • B. Long-form engine (Video Editor plugin render.py): over 60 s, many screen recordings, a style that needs 60 fps or Remotion, or no awa install. Effects come from the effects engine as a pre-pass, motion graphics from HyperFrames or Remotion as overlays, sound from scripts/sound_mix.py.
    • C. Motion-graphics build (HyperFrames, or Remotion when the style says so): graphics-led looks where the footage becomes one layer in a designed frame (Nat L3, L7, L8, L9, G3, G7, X3, X11, X19, explainers). Load /hyperframes first and follow its work loop.
    • You can combine them: for example engine A for the edit, plus a HyperFrames hook rendered separately and joined in front.
  4. Write the plan table in chat:

    | # | Time | What

Truncated for display — read the full file on GitHub.

Related Skills

View on GitHub
GitHub Stars0
CategoryAutomation
Updated15d ago
Forks0

Trust signals

80/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

1 medium1 low