Skills

video-to-blender: Turn a reference video, image, or idea into an editable procedural Blender node system

This coding agent Skill is best when you want to generate an editable procedural Blender node system (geometry, shading, compositor nodes) from a reference video, image, or idea; before starting, you must have Blender 5.2+ ready and confirm the agent is installed, otherwise its build-and-validate workflow cannot be driven.

Official source · gokayfem/video-to-blender

Install

claude plugin marketplace add gokayfem/video-to-blender

Who This Is For

This Skill is for users who want to reproduce a reference video, an image, or an idea in Blender using procedural nodes (Geometry Nodes, Shader Nodes, the Compositor). It ships with a tested library of NK node groups and a nodekit Python builder, invoked by a coding agent that helps you find node groups, build them, and validate the results.

Prerequisites that must be met:

  • Blender 5.2 or later, available and usable: blender on PATH, the $BLENDER environment variable, or the macOS app.
  • A supported coding agent to drive the workflow.
  • Not suitable cases: the evidence does not state whether there is an offline usage mode that does not depend on Blender, does not state which input video formats are supported, and does not state the range of supported asset languages — all of these are unknown, so do not assume them. If your environment cannot provide Blender 5.2+, whether you can use it cannot be confirmed within the scope of the evidence.

First Attempt in 3 Minutes

Recommended main path: install via the official plugin marketplace in Claude Code.

  1. Prerequisites: Claude Code is installed, and Blender 5.2+ is available (blender on PATH, $BLENDER set, or the macOS app).
  2. Install location and command (official wording):
claude plugin marketplace add gokayfem/video-to-blender

Then install the plugin following the official process.

  1. Trigger a low-risk task: ask the agent to turn one of your reference videos or images into an editable procedural Blender node system. For a first attempt, start with building a single node group so you can observe the results easily.

  2. In the official core workflow, the agent uses nodes_tools.py search to find node groups in the library, uses try to build a group on test inputs, prints its node warnings and lint, and renders a still frame; afterwards validate.py reopens the saved .blend and checks warnings, counts, evaluation time, and camera gaps.

Success signals: try outputs node warnings and lint and renders a still frame; validate.py reopens the .blend and reports its checks (warnings, counts, evaluation time, camera gaps). These are observable outputs explicitly described in the evidence.

Note: the official documentation also lists other installation methods — for agents such as Codex, Cursor, Gemini CLI, and Copilot, the skills CLI is available (npx skills add gokayfem/video-to-blender), and Claude Code can also be installed manually (cp -R skills/procedural-blender-nodes ~/.claude/skills/). These are secondary alternatives, not the recommended main path. Building nodes and saving a .blend are file-writing actions; before your first attempt, confirm you accept producing .blend files and render output in Blender. Beyond that, whether the Skill executes other commands or accesses the network is not stated in the evidence and is unknown.

Use Cases

Case 1: Generate a node system from a reference video. Scenario: you have a video whose visual effect you want to reproduce. Start a task with the agent: "Using this reference video, build an editable procedural node system in Blender." Following the official workflow, the agent will use nodes_tools.py search to find suitable groups in the NK node group library, use try to build and render a still frame, then use validate.py to re-check the .blend's warnings, counts, evaluation time, and camera gaps. Expected result: an editable Geometry/Shader/Compositor node system plus a validation report. As for which video formats are specifically supported, the evidence does not say — rely on the agent's actual feedback.

Case 2: Build and validate a single node group from an image or an idea. Scenario: you just want to test a material or geometry effect. Ask the agent to "build a node group on test inputs based on this image (or this idea)." The agent will call try to build the group on test inputs, print node warnings and lint, and render a still frame, then use validate.py to reopen the saved .blend for checks. Expected result: the group's warning list, lint results, and a rendered still frame; if the validation report has warnings, you can have the agent adjust and retry accordingly.

Usage Boundaries

  • Files and side effects: the workflow builds nodes and saves a .blend, and validate.py reopens that .blend; rendering a still frame produces output. The explicit confirmation point before building is choosing the reference material (video/image/idea) and the target to build. The Skill produces a node system and validation information; whether it directly modifies your other files is not stated in the evidence.
  • Commands and network: the script invocations confirmed by the evidence are nodes_tools.py search, try, and validate.py; whether other commands are executed or the network is accessed is not stated and is unknown.
  • Runtime environment and clients: Blender 5.2+ must be available (blender on PATH, $BLENDER, or the macOS app). Claude Code installs via the plugin marketplace; agents such as Codex, Cursor, Gemini CLI, and Copilot install via the skills CLI; the evidence does not state whether the Skill only works with the listed clients, and whether other agents can use it is unknown.
  • Explicit official limitations and unconfirmed information: nothing was found about supported input formats, language coverage, offline usage, or operations beyond try/validate.py; do not infer these on your own.