blender-vselisted

Use when a named .blend Video Sequence Editor project is the source of truth or the required editable deliverable. Safely inspect or edit the project, resume earlier work, render the timeline, attach externally generated proxies, and verify persistence with four bounded, revision-safe local MCP tools while preserving human changes. For end-to-end production, pair this execution Skill with an available director or production-orchestration Skill that owns creative planning, storyboards, and source-media work. Do not use for generic video creation, proxy encoding, one-off FFmpeg work, Blender 3D work, or arbitrary bpy.
Aoike123/blender-vse-control · ★ 4 · AI & Automation · score 72

Install: claude install-skill Aoike123/blender-vse-control

[Chinese version](SKILL_zh-CN.md) # Blender VSE Treat the named `.blend` file as the editable source of truth. Use only `blender_read`, `blender_patch`, `blender_acknowledge`, and `blender_verify`. Never substitute raw `bpy`, shell-driven Blender scripts, or a hidden headless editor for these tools. ## Establish the boundary - Do not treat a fresh installation as ready until the user has confirmed an absolute project directory in `BLENDER_VSE_PROJECTS_DIR`. If the variable is not configured, ask where editable `.blend` projects should live before creating one. Never choose a plugin cache, marketplace checkout, or temporary clone. - Prefer `<workspace>/blender-vse-projects` for projects and referenced media. If no workspace is available, recommend opening one first. If the user picks a directory outside it, explain the sandbox/portability trade-off and obtain explicit confirmation; never relocate existing files implicitly. - Require an explicit `.blend` path. Do not scan the filesystem for projects. - If the four tools are unavailable, stop and explain that the local MCP server must be installed and configured. Do not imitate it with arbitrary Python. - A path outside configured roots is an authorization/configuration issue. Do not move or copy the project to evade it. - Proxy encoding and rebuilding are external. `attach_proxy` only validates and attaches an already-generated manifest; attachment does not change source media, and final rendering still