5 Free AI Skills for Video Editing
shared by seminlee2794 · imported Nov 21, 2026
This video introduces five free AI skills available on GitHub that streamline various video editing tasks. These skills cover generating captions, cutting filler words, creating videos from prompts, coding videos, and performing local edits, compatible with tools like Claude Code, Codex, and Cursor.
What's inside (5)
New to skills? How to add one in Claude, with screenshots →
- 01
Hyperframes
SkillIn LibraryBuilds a whole video from one brief: story, motion, voice, music and captions. Its embedded-captions skill captions a talking-head video in 35 styles, including text placed behind you.
How to add it in Claude
- 1
Open Customize → Skills. Left sidebar → Customize. Ready-made skills: Discover tab → +.
- 2
Add → Upload skill. Drop the SKILL.md (or a .zip with it), check the preview, Upload.
- 3
Just ask. Claude picks the skill when your request matches it.
Try this
Try saying: "Add cinematic captions behind me in interview.mp4
Library page →Show the skill file
Codemd**Running the CLI:** every `npx hyperframes <command>` here, the beacon included, means `node <SKILLS>/hyperframes/scripts/plugin-cli.mjs <command>` run in the project, where `<SKILLS>` holds this skill's folder ([rules](references/plugin-installation.md)). **Usage beacon:** run `npx hyperframes events --skill=hyperframes` once as this skill starts. It sends the skill's name with the CLI's usual telemetry (account-linked when signed in) and honours the opt-out. # HyperFrames HyperFrames renders HTML to video by seeking a paused timeline frame by frame, so every render is identical; the person edits the same files in the Studio preview. Use it unless another framework or a plain browser recording is asked for. Run the CLI as `npx hyperframes <command>` (`/hyperframes-cli`); at the start of a new video, `npx hyperframes usage --json` reports the person's remaining plan usage (say "unknown" when it is). `index.html` is the root composition: it declares the video's variables and mounts one scene per sub-composition from `compositions/`. Media and fonts live in `assets/`. A new project: `npx hyperframes init <dir> --skip-skills --skill=hyperframes`. A website as the subject: `npx hyperframes capture <url> --json`. Build what was asked: no voiceover or captions and no new aspect ratio unless the request or the source calls for them; a film over ~15 s that tells something gets music and sound on its visible actions unless the person asked for silence (`references/sound.md`). A new video is 1920×1080 at 30 fps. A question, a hold or a loose idea gets an answer or a proposal, not an edit. Before hand-writing a named effect, transition, caption style, chart or card, search the registry (`/hyperframes-registry`). Any media (a presenter or avatar, footage, voice, music): `/media-use`, which says when HeyGen is needed and what is free. Show real things from their source (the product's screens, the brand's logo, a real place's imagery); draw only what has none. ## Contract `npx hyperframes check --json` reports most violations with a `Fix:` line. 1. Every timed element has `class="clip"`, `data-start` and `data-duration` in seconds, and shows over `[start, start + duration)`: land an end state just before its end. `data-track-index` is only a Studio lane (clips that never overlap share one: `references/format.md`); paint order is `z-index`. 2. The video's length is the root's `data-duration`: overrun is cut, an early end holds the last frame. 3. Each composition builds one paused timeline and registers it after its tweens: `window.__timelines["<data-composition-id>"] = tl`. 4. No `Date.now()`, unseeded `Math.random()`, network fetches, timers or `repeat: -1`. Everything visible is a function of timeline time. 5. Never tween `display`, `visibility` or `autoAlpha` on a `.clip`; animate a child. 6. No CSS `transform` on an element GSAP transforms; animate transforms, not `left`/`top`/`width`/`height`. 7. Never `play()`, `pause()` or seek media. A `<video>` keeps its sound with `data-has-audio="true"`, else it is `muted`; music, voice, replacement sound and J/L cuts are a separate `<audio>`. 8. Every `<audio>` has an `id` or it is left out of the mix. No `crossorigin` on media. Time the `<video>`, never its wrapper. 9. Only the bundled fonts (`references/format.md`) resolve by name; any other family needs `@font-face` to a file in `assets/fonts/`. 10. Asset paths: `assets/...` (no leading `/`), in sub-compositions too. 11. Grades, grain, blur and vignettes on footage go through `npx hyperframes media-treatment` (`/media-use`), never CSS filters. 12. A scene file puts its styles, markup and scripts inside `<template>` and styles its root as `#root`. Intended overflow or overlap: `data-layout-allow-overflow`, `data-layout-allow-overlap`. ## Keep it editable Studio edits the tags you write. - One scene per sub-composition, short readable ids; the root holds only scene hosts, media and audio. - Timed elements are written in the HTML, not made by script, each with a stable `id`. - Copy, brand colours and swappable media are variables (`data-var-text`, `data-var-src`, `var(--id)`). - One kind per track: `data-track-kind="graphics"` on scene and overlay hosts, `captions` on the one host that holds every caption group. - Content stays inside the 90% action-safe box, captions and key text inside 80% title-safe; Studio draws the guides, never add them. ## Work loop - An existing project: `npx hyperframes timeline --json` shows what plays when; before any change, `npx hyperframes history --since mine --who <you>` shows what the person changed since your last turn: build on it (`/hyperframes-cli`). - A new film over ~15 s that tells something: its type's file (below), then `references/story.md`: three storylines that are three different films, in words only; the person picks unless they asked for the file or no stops. Then `SPEC.md` (`references/spec.md`): every adjective as a number, the defaults banned by name, the shots by frame. - After your last edit: `npx hyperframes check --json`; fix every error, weigh every warning. A film: `npx hyperframes snapshot --review` and `references/review.md`, ending in `REVIEW.md`. A small edit: snapshot what you changed (`--at`, `--range`, `--composition`) and look before you reply. - Render when the person approves the Studio preview, asks for the file or asks for no stops, after your check and review pass; otherwise stop at the preview and wait. ## The HyperFrames desktop app Call it "the HyperFrames desktop app", never "Studio"; offer it as the better way to keep editing, not the only one. - Before the delivery render of a new video, open the Studio preview, even in no-questions mode, and say they can edit there. If `preview` printed "Keep editing by chatting with Framey", add that the **Edit with Framey** button opens the app. - After the delivery render, pass on its Framey line in your own words: offer to run the `hyperframes open` it names or give its download link; else say nothing (autonomous: the delivery note). - When any command says to run `catch-up`, run `npx hyperframes catch-up [dir]` before your next change; what it lists is their work, not a new request. ## What to read | The request | Read | | --- | --- | | A video to copy or remake | `/reverse-any-video` | | An episode in a proven style | `/style-sampling` | | Another film's style on a new topic | `references/look.md` | | Launch, promo, feature | `references/types/launch.md` | | Explainer, tutorial | `references/types/explainer.md` | | Music video | `references/types/music.md` | | Chart, numbers | `references/types/data.md` | | Vertical or social clip | `references/types/vertical.md` | | 3D, simulation, generative | `references/types/3d.md` | | Character, mascot, story short | `references/types/character.md` | | A real place or map; a website, PR or script; kinetic type | `references/film.md` | | Captions; cards over a talking head | `references/captions.md`; `references/overlays.md` | | Motion: eases, titles, cuts, punch-ins, speed, holds | `references/motion.md` | | Scenes, attributes, media, lint; GSAP, Lottie, 3D, canvas | `references/format.md`; `references/runtimes.md` | Decks: `/slideshow`. Remotion source: `/remotion-to-hyperframes`. Figma: `/figma`. Skills and the pinned CLI: `references/skill-lifecycle.md`.
- 1
- 02
video-use
SkillWorks from a timed transcript instead of raw frames, which keeps it fast and cheap. Cuts filler words and dead air, grades color and burns in subtitles. Shows you a plain-English plan and waits for your OK before it cuts anything.
How to add it in Claude
- 1
Open Customize → Skills. Left sidebar → Customize. Ready-made skills: Discover tab → +.
- 2
Add → Upload skill. Drop the SKILL.md (or a .zip with it), check the preview, Upload.
- 3
Just ask. Claude picks the skill when your request matches it.
Try this
Try saying: "Edit these into a launch video
- 1
- 03
openfilm
SkillTurns Claude Code or Codex into a video agent. Finds footage, music and voices, writes each shot and cuts them together. Comes with an editor so you can change anything it makes.
How to add it in Claude
- 1
Open Customize → Skills. Left sidebar → Customize. Ready-made skills: Discover tab → +.
- 2
Add → Upload skill. Drop the SKILL.md (or a .zip with it), check the preview, Upload.
- 3
Just ask. Claude picks the skill when your request matches it.
Try this
Try saying: "Make a 20-second launch video for my CLI, with music.
- 1
- 04
remotion
SkillTeaches your agent Remotion, where videos are written as React code (animation, timing, media). Includes captions, transcribed locally with Whisper.
How to add it in Claude
- 1
Open Customize → Skills. Left sidebar → Customize. Ready-made skills: Discover tab → +.
- 2
Add → Upload skill. Drop the SKILL.md (or a .zip with it), check the preview, Upload.
- 3
Just ask. Claude picks the skill when your request matches it.
Try this
Try saying: "Make a 10-second animated intro for my channel
- 1
- 05
ffmpeg-skill
SkillTrims, cuts silences and filler, reframes to 9:16 and adds subtitles. Export presets for Reels, TikTok, Shorts and YouTube. It can batch-edit whole folders and checks its own output. Runs entirely on your computer: no cloud, no API keys.
How to add it in Claude
- 1
Open Customize → Skills. Left sidebar → Customize. Ready-made skills: Discover tab → +.
- 2
Add → Upload skill. Drop the SKILL.md (or a .zip with it), check the preview, Upload.
- 3
Just ask. Claude picks the skill when your request matches it.
Try this
Try saying: "Cut the silences and export this as a 9:16 Reel
- 1
Review commands before running them. Promptu never runs code on your machine.

