Blender Video Editing logo

Blender Video Editing

Community
EL4CTEO
blender-video-editing

Video in Blender 5.2 - Video Sequencer edits from Python (clips, image sequences, crossfades, titles, music fades, proxies, color management, H.264/AAC output) and motion tracking (feature detection, camera solve, scene orientation, tripod and plane tracking, stabilization) for VFX shots. Use to cut renders/footage together or match-move a camera.

Overview

PublisherEL4CTEO
Repositoryblender-skills
Skill nameblender-video-editing
Stars
605
Forks
52
Bundled files
3
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.

  • 3 bundled files

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

  • Open source

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

Installation

Install the Blender Video Editing 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/EL4CTEO/blender-skills/tree/main/skills/blender-video-editing
  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/EL4CTEO/blender-skills.git /tmp/blender-skills
mkdir -p .claude/skills
cp -r /tmp/blender-skills/skills/blender-video-editing .claude/skills/blender-video-editing
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Blender Video Editing 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 Blender Video Editing 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 Blender Video Editing 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.

Video editing and tracking

The execution model is in blender-core. Rendering the 3D shots and the compositor (5.0 API) are in blender-rendering.

One call each

scripts/vse_edit.py -- --clips //renders/sh010/ //renders/sh020/ //logo.png --crossfade 12 --title "Project" --audio //music.wav --out //edit.mp4 --render
scripts/vse_edit.py -- --clips a.mp4 b.mp4 c.mp4 --crossfade 0 --fps 24 --out //review/f_#### --render   # hard cuts to PNG
python
import track_camera; print(track_camera.run(clip="C:/shots/sh010.mp4", focal=35, sensor=36))  # live/MCP only

vse_edit.py

  • Builds into its own Edit scene (--scene), so 3D scenes stay untouched. Clips go on alternating channels 1/2, crossfades (CROSS) on 3, the title on 4, clip audio on 6/7 (movies get their sound strip), and music on 8 (trimmed to the edit with a --audio-fade volume fade-out).
  • A clip may be a movie, a still (--still-seconds), a folder of frames, or a #### pattern. Each crossfade overlaps the previous clip by --crossfade frames, so the edit gets shorter by that much per cut. Re-running replaces the previous edit.
  • Sets view transform Standard: footage must pass through untouched (measured: AgX turned pure red into 0.86/0.23/0.13). Grade on purpose with strip modifiers instead.
  • Output: .mp4/.mov/.mkv = H.264 (CRF high, preset good) + AAC 192k stereo. Any other path = PNG frames. 5.0+ needs image_settings.media_type = "VIDEO" before file_format = "FFMPEG". It reports the file size, and the test decodes it back (frame count, size).

Editing rules pros follow

  • Match the frame rate first (--fps = the footage/render rate). Mixed rates drift audio. Re-render or retime (SPEED effect) instead.
  • Heavy footage: build proxies (strip.use_proxy = True, 25/50%, sequencer.rebuild_proxy). 5.2 builds only proxies (no .blen_tc timecode files anymore).
  • Per-strip color: strip.colorspace_settings.name (sRGB for 8-bit video, Linear Rec.709 for EXR renders). A dedicated edit scene keeps 3D color settings out of the edit.
  • 5.2 API: strips.new_movie(..., stream=N) / new_sound(stream=N) pick a stream from multi-track files. strip.connections lists connected strips. New effect type COMPOSITOR (a node-tree effect). Text strips have Subtitles / Main Title / Corner Title presets in the UI. Timing uses left_handle/right_handle/duration (5.1 names). Strip keyframes live on the scene's action.

Motion tracking (track_camera.py, live session)

  • The Clip Editor operators need a window, so this borrows the largest area, runs, and restores it. In -b it raises. It detects features at the first and last frame, tracks both ways, deletes tracks shorter than min_frames, solves (auto keyframes, refines focal only if unknown), deletes tracks above max_error px and re-solves, then runs setup_tracking_scene (camera + Camera Solver constraint, background footage, frame range).
  • Measured on a synthetic 40-frame dolly at 960×540: 56 tracks, 0.19 px solve error, 35 mm focal kept exactly. Quality bar: < 0.3 px great, < 0.5 good, > 1 px slides.
  • Give focal/sensor whenever known. The solver is far more stable than when refining the focal. Set the sensor before the focal (focal is stored in px).
  • Nodal pans (camera only rotates): tripod=True. A normal solve fails without parallax.
  • Orient the scene after solving (UI, Clip Editor context): select 3 floor tracks → clip.set_plane(plane="FLOOR"), 1 track → clip.set_origin(), 2 tracks a known distance apart → clip.set_scale(distance=…). Otherwise scale and up are arbitrary.
  • Other jobs: screen/sign replacement → clip.create_plane_track() on 4+ tracks of a planar surface. Shaky footage → 2D stabilization (tracking.stabilization.use_2d_stabilization, add tracks). Points for modeling → clip.bundles_to_mesh().

Shooting/footage tips that make solves work

Fast shutter (little motion blur), real parallax (move the camera, don't just pan), textured static surfaces at several depths, no rolling-shutter whip pans, and a lens grid shot to calibrate distortion when using wide lenses.

Gotchas

  • bpy.ops.render.render(animation=True) renders the sequencer only when scene.render.use_sequencer is on and the strips are in the scene being rendered. The script renders its own edit scene.
  • Removing a clip also removes its effect strips. Collect names before deleting in loops.
  • Image sequences must be contiguous. Missing frames show as black.

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 Blender Video Editing AI skill do?

Video in Blender 5.2 - Video Sequencer edits from Python (clips, image sequences, crossfades, titles, music fades, proxies, color management, H.264/AAC output) and motion tracking (feature detection, camera solve, scene orientation, tripod and plane tracking, stabilization) for VFX shots. Use to cut renders/footage together or match-move a camera.

Why use Blender Video Editing on TypingMind?

Because you install it once and use it with any model. Blender Video Editing 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 Blender Video Editing in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/EL4CTEO/blender-skills/tree/main/skills/blender-video-editing. 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 Blender Video Editing?

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 Blender Video Editing?

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

Is the Blender Video Editing AI skill free?

Yes. It is published on GitHub by EL4CTEO 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 👇