Video Editor logo

Video Editor

Community
timscheuerai
video-editor

Turn a raw talking-head or screen-demo recording, or a short, into a publish-ready edit in 1 run, in a clean caption style (off-white word-by-word captions, serif payoffs, interludes, hard reframes, no boxes), with overlays timed to the spoken word, -14 LUFS audio, an editable DaVinci Resolve timeline and a QA sheet. Use for "edit this video", "make it publish ready" or "add captions"; it uses talking-head-video-cut for the cut and its bundled Remotion overlay kit for graphics.

Overview

Publishertimscheuerai
Repositorylinkedin-funnel
Skill namevideo-editor
Stars
60
Forks
20
Bundled files
30
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 30 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by timscheuerai on GitHub. Read the source before you install it.

Installation

Install the Video Editor AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/timscheuerai/linkedin-funnel/tree/main/skills/video-editor
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/timscheuerai/linkedin-funnel.git /tmp/linkedin-funnel
mkdir -p .claude/skills
cp -r /tmp/linkedin-funnel/skills/video-editor .claude/skills/video-editor
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Video Editor in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Video Editor on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Video Editor is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Workspace: all context paths below (identity, audience, strategy, voice, brand, raw, output, index, log, workspace preferences and context scripts) resolve from context/ in the kit root. Read both the root AGENTS.md and context/AGENTS.md. Skill-local references/, scripts/, presets/ and overlays/ resolve from this skill directory.

Video editor

1 prompt in: where the footage is, a line of direction, optionally the music. Out: a finished MP4, a Resolve timeline the author can open and nudge, and a QA sheet. Keep going until QA passes (at most 3 passes), then report. Do not stop to ask between stages unless content selection is genuinely ambiguous.

Works for 16:9 long-form and 9:16 shorts (captions on, see the Shorts section of the style rules). The style lives in this folder, not in the model: style-rules.md is the rulebook, edit-schema.md the plan format, and the template menu is fixed. Read both before planning. For a designed intro followed by a clean tutorial, longform-edit decides the treatment; this skill is the engine that builds it.

Requirements

Python 3 with Pillow (and numpy for match_grade.py), ffmpeg and ffprobe, Node 18 or newer for the overlay kit (npm install in overlays/ on first use; the build runs it when node_modules is missing). uv is optional: the Resolve export fetches opentimelineio through it. A word-timed transcript of the source (see project-setup.md for the JSON shape). Read the Remotion licence note in the overlay kit README.

Make the look the author's before the first edit: the colours and fonts in overlays/src/theme.ts from brand/BRAND.md. With an empty brand, keep the neutral defaults and say so.

Pipeline

  1. Cut. Run talking-head-video-cut (word-timed transcript, take selection, render). Its project folder <source-dir>/edit/<slug>/ becomes this edit's project: transcripts/, edl.json, the cut MP4. Reuse an existing cut when the author points at one; for a clip cut elsewhere, follow project-setup.md.

  2. Map the words onto the finished cut:

    bash
    V=skills/video-editor/scripts
    python3 $V/transcript_out.py "$PROJECT"        # transcript_out.md + words_out.json
  3. Look at the picture. A labelled frame every 10 s (see the scan), then gridded full frames at every candidate moment. Measure the webcam box once and write it to layout.cam. Placement comes from pixels you have seen, never from guesses.

  4. Plan edit.json: chapters first, then the moments that earn a card, spotlight or punch-in. Card text is the speaker's own words, trimmed. Every event has a cue, the words it lands on. For a short talking-head clip, draft the plan automatically and then review it:

    bash
    python3 $V/plan.py "$PROJECT" --base "$PROJECT/<cut>.mp4" --name <slug>   # presets/clean.json

    It prints the hooks, the marked word, drops, reframes and any flat stretch. Check the opening payoff is the word that matters, the closing payoff is a real payoff on a free side of the frame, the marked words are the key terms, ASR errors and brand names are fixed in fixes, and every flat stretch gets a beat.

  5. Check and preview, fast, no video render:

    bash
    python3 $V/build_edit.py "$PROJECT/edit.json" check stills

    Read every qa/stills/stills-sheet-*.jpg. Fix wording, anchors and rects, rerun until the sheets are clean.

  6. Build everything:

    bash
    python3 $V/build_edit.py "$PROJECT/edit.json"      # check, assets, audio, master, export, qa
    python3 $V/build_edit.py "$PROJECT/edit.json" assets master qa   # after a visual fix

    Only changed overlays re-render (hashes in work/render-hashes.json).

  7. QA. Read qa/report.md and every qa/master-sheet-*.jpg. Pass means: 0 decode errors, duration equals the cut, loudness -14 ±1 LUFS, true peak at or under -1.5 dBFS, no black segments, every frame shows the card legible, off the face and matching the words. Fix and rebuild; stop after 3 passes and report what is left.

  8. Deliver. Copy out/<name>.mp4 into the upload folder the author uses (default output/<date>-<slug>/) and hand off to youtube-description (the Chapter cards are the chapter list). Give the author the .fcpxml path.

Optional audio and picture steps:

  • A quiet mic with room noise: scripts/voice_print.py <raw take> <edl.json> <out.wav> learns a noise print from the longest silence and cuts it to the EDL; swap it in as the cut's audio and set voice.clean to false.
  • One clip of a session graded by hand: scripts/match_grade.py learns that grade and bakes a .cube LUT for the other takes shot in the same light.

Resolve handoff

In DaVinci Resolve (the free version is enough): File > Import > Timeline, pick out/<name>.fcpxml (fallback out/<name>.otio). Tracks:

TrackContent
V1source clips, 1 per EDL range, every cut editable
V2zoom inserts; delete one to drop that zoom
V3+overlays, ProRes 4444 with straight alpha
A1source audio, raw (the master's voice clean-up is not applied here)
A2music stem, already ducked under the voice
A3+sound effects, 1 clip per hit

Markers carry each event id and cue. The flattened master stays the reference; Resolve is for the author's hand edits. If an import breaks, note what broke and fix scripts/export_timeline.py.

Hard rules

  • Clean style (see the style rules): light type on the picture, no boxes, pills, highlights or pop animations.
  • Graphics come only from the menu: Captions, Interlude, Lower, Stat, Keyword, List, Chapter, Media, Focus, Zoom. No improvised graphics.
  • Sound effects exist only as a field of a visual event, and only from files the author has the rights to. No event, no sound.
  • Show the real thing: Focus on the actual UI, Media with a real screenshot of the named repo, site or post. Never a stand-in.
  • Words are the speaker's. Numbers only when spoken or on screen (add source), or from identity/proof.md.
  • Never cover the webcam. A zoom keeps the webcam fully in or fully out.
  • 1 card on screen at a time, at least 1 s apart.
  • Never modify the source recordings. Synced folders (iCloud, Drive) may hold files offline; make sure the sources are local before a long render.

Files

  • scripts/transcript_out.py maps the transcript's words through edl.json.
  • scripts/plan.py drafts edit.json for a talking-head clip from presets/clean.json.
  • scripts/build_edit.py validates and builds; stages check stills assets audio master export qa.
  • scripts/export_timeline.py writes .fcpxml and .otio.
  • scripts/voice_print.py and scripts/match_grade.py: optional voice and grade helpers.
  • overlays/: the Remotion graphics kit (README).

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Video Editor AI skill do?

Turn a raw talking-head or screen-demo recording, or a short, into a publish-ready edit in 1 run, in a clean caption style (off-white word-by-word captions, serif payoffs, interludes, hard reframes, no boxes), with overlays timed to the spoken word, -14 LUFS audio, an editable DaVinci Resolve timeline and a QA sheet. Use for "edit this video", "make it publish ready" or "add captions"; it uses talking-head-video-cut for the cut and its bundled Remotion overlay kit for graphics.

Why use Video Editor on TypingMind?

Because you install it once and use it with any model. Video Editor is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Video Editor in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/timscheuerai/linkedin-funnel/tree/main/skills/video-editor. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Video Editor?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Video Editor?

As many as you like. As long as a model supports skills, you can use Video Editor with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Video Editor AI skill free?

Yes. It is published on GitHub by timscheuerai under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇