Individual skill
blender-film
Make a short, realistic cinematic shot in Blender with Claude, start to finish - storyboard, city layout, a physics-driven flight path, a chase camera, a hero that moves like the real thing, a realism pass, night lighting that actually reads as night, handheld camera shake, sound designed from the 3D motion, an overnight render with automatic checks, and a "white clay build-up" reveal that proves it's real 3D. Use when someone wants a cinematic Blender shot / short film / drone or superhero flythrough made with Claude, asks to "do the whole workflow from the video", or wants any single step of it (physics path, night lighting, sound from motion, clay build-up).
skills/blender-film/SKILL.md
Source commit 567116bf3514ce0e469c2cb5cb04fa974fca217a
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 11, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 74
- Repository last updated
- Oct 25, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- 3d-animation Repository topic
- blender Repository topic
- blender-python Repository topic
- claude Repository topic
- claude-code Repository topic
- claude-skills Repository topic
- cycles Repository topic
- operations Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 8,058 bytesSKILL.mdcore · 8,058 bytesnotes/BUILD_LOG.mddoc · 5,404 bytesnotes/PLAN.mddoc · 5,380 bytesnotes/reference-tutorial-notes.mddoc · 9,631 bytesnotes/storyboard-image-prompt.mddoc · 3,881 bytesscripts/01_swing_sim.pyruns · 7,994 bytesscripts/02_path_empty.pyruns · 6,238 bytesscripts/03_camera.pyruns · 5,830 bytesscripts/03b_camera_noise.pyruns · 1,254 bytesscripts/04_drone_attitude.pyruns · 7,433 bytesscripts/05_realism.pyruns · 9,086 bytesscripts/06_night.pyruns · 14,187 bytesscripts/07_shakify_cams.pyruns · 2,818 bytesscripts/08_lens_look.pyruns · 1,499 bytesscripts/09_render_opt.pyruns · 2,669 bytesscripts/10_render_edit.pyruns · 2,284 bytesscripts/11_motion_data.pyruns · 2,880 bytesscripts/12_build_sfx.pyruns · 19,270 bytesscripts/13_aerial_cam.pyruns · 1,533 bytesscripts/14_clay_build.pyruns · 5,766 bytestools/bridge.pyruns · 1,057 bytestools/clay_assemble.shruns · 824 bytestools/lib.pyruns · 2,721 bytestools/render_window.ps1runs · 3,536 bytestools/send.pyruns · 432 bytes
Read excerpt
# Blender film with Claude
The workflow behind a 10-second night FPV drone shot through a city: one storyboard, a real physics path, one pivot (the first hero
didn't work), night lighting, sound from the motion, a 3.5-hour render, and a clay build-up reveal. Every step below is a script in
`scripts/` that was actually run for that shot; names in them (`Drone Empty`, `Street Asphalt`, `Building_1`...) come from that
scene - rename them for yours.
## 0. Setup
- Blender 4.4+ (made on 5.2), a GPU for Cycles, Python 3 + `ffmpeg` on PATH (+ `numpy`, `scipy` for the sound step).
- **Live bridge** (Claude drives the open Blender, you watch): in Blender's Text Editor run `tools/bridge.py` (listens on
127.0.0.1:9876). Then from a terminal: `python tools/send.py scripts/06_night.py` or `python tools/send.py -c "print(bpy.data.filepath)"`.
- Set `FILM_ROOT` to your project folder (default `~/blender-film`): `scene/`, `render/`, `audio/`, `research/` live there.
`tools/lib.py` is loaded by every script (helpers: `coll()`, `save()`, `snap()`...).