blender
3D scenes, character acting and product shots from a shot spec, rendered in Blender, as a finished film, as clips for any other build (moviepy, a video job, an editor), or as elements of a Remotion video (transparent characters over a scene, a Remotion render on a 3D laptop, phone or floating card t…
Install / Use
npx skills add digitalsamba/claude-code-video-toolkit --skill blenderInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Development & EngineeringSupported Platforms
Tags
Our assessment of blender
blender scores 85/100 on our quality scale, 2566th of 4,702 Development & Engineering skills we index.
Its SKILL.md is 51 KB long, well organised into 14 sections with 11 code examples: long enough that it reads more like full documentation than a focused instruction file, which agents can find harder to follow.
With 2,544 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated 5 days ago, so blender is actively maintained.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
blender compared with similar skills
All 4 of these similar skills score higher than blender; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| blender (this skill)by digitalsamba | 85 | 2.5k | 5d ago | SKILL.md |
| taste-skillby Leonxlnx | 100 | 117.6k | 9d ago | CLAUDE.md |
| ai-job-searchby ai-job-search-dev | 100 | 72.3k | today | CLAUDE.md |
| claude-howtoby luongnv89 | 100 | 47.4k | 3d ago | CLAUDE.md |
| lobehubby lobehub | 100 | 85.7k | today | MCP Server |
Frequently asked questions
- How do I install blender?
- Run
npx skills add digitalsamba/claude-code-video-toolkit --skill blender. The install tabs above show the steps for each supported agent. - Which AI agents does blender work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is blender safe to use?
- It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is blender still maintained?
- The repository was last updated 5 days ago, so blender is actively maintained.
Skill content
View source on GitHubname: blender description: 3D scenes, character acting and product shots from a shot spec, rendered in Blender, as a finished film, as clips for any other build (moviepy, a video job, an editor), or as elements of a Remotion video (transparent characters over a scene, a Remotion render on a 3D laptop, phone or floating card that the camera pulls back from, an imported 3D model on a studio stage), or a brand's opening and closing ident built from its SVG logo. A rigged cartoon cast described in JSON (build, face, hair, clothes, a seed), sets, shots by type, acting beats in seconds or on narration words, every camera checked by geometry, sound placed on the motion. Use when a video needs a consistent directable character (parody, explainer gag, reaction shot), a 3D reveal or element in a Remotion video, a device or product shot of an app or a model, or exact acting timing that AI video clips can't hold. Triggers include Blender, 3D, character animation, rigged character, cast, shot spec, acting, camera angles, transparent clip, alpha, pull out from the screen, phone mockup, device mockup, product shot, turntable, orbit, glTF, GLB, BlenderClip, logo animation, ident, logo reveal, sting, SVG in 3D.
Blender shot specs
tools/blender_render.py turns a JSON shot spec into 3D footage: a whole film, one clip per shot for another
build, or both from the same spec. The spec says what happens; lib/blender/
decides where things go: cameras are placed by shot type round their subject and checked (in frame, nothing in
the way) before they are kept; acting is verbs (expression, pose, shake_head) rather than keyframes; every
moment worth a sound is exported with its time, so the sound is on the motion by construction.
Four worked examples:
examples/blender-product-shot/spec.json: a studio stage with no character: a picture on a floating card and on a phone, and an imported model, withreveal,orbitandproductshots.examples/blender-disk-panic/spec.json: a film from one spec (22.5 s, 8 shots, 37 beats).examples/blender-in-remotion/: Blender clips inside a Remotion video. A terminal scene cuts to itself on a 3D laptop and the camera pulls back; then a transparent character acts beside the list of beats it is acting.examples/blender-kitchen/: a fitted character (experimental). Mara, a generated model seated on the rig withfit, walks in with a mug, sits, puts it down, opens the laptop and drinks. Its README says what the spec works round.
uv run tools/blender_render.py doctor # Blender found? s/frame on this machine
uv run tools/blender_render.py check examples/blender-disk-panic/spec.json # ~5 s: checks + stills + contact sheet
uv run tools/blender_render.py render examples/blender-disk-panic/spec.json # ~15 min (M4, EEVEE, 1080p)
uv run tools/blender_render.py render spec.json --res 640x360 # a draft to judge motion, 0.35 s/frame
uv run tools/blender_render.py render spec.json --engine cycles # physical light; ~10x slower (17 s/frame)
uv run tools/blender_render.py render spec.json --clips --alpha --to projects/my-video/public/blender
uv run tools/blender_render.py open spec.json # the built scene in Blender
Tell the person how long it will take before you start. A fitted character acting in a room renders at about
2.2 s a frame at 1080p (45 s of film is close to an hour, and is rendered more than once), so a film of this kind
is two to three hours of unattended work a session, and takes a few sessions with the person's notes between
them. End each session with the film, its checks, a decisions file and a prompt for the next session that leaves
a gap for their notes: docs/blender.md, "A film over several sessions".
Output in <spec dir>/out/ (out/<name>/ for a spec not called spec.json): checks.json, contact_sheet.png, stills/, events.json, scene.blend (open it
in Blender and scrub), and after render the .mp4 named after the spec's folder, or clips/ with --clips.
Requires Blender 4.2 or later. It has been run on 5.3 (macOS) and 4.2 LTS (Linux, in a container); Windows is
supported by the code and not yet run. Optional component: nothing else in the toolkit needs it.
Install, timings and troubleshooting: docs/blender.md.
What the render is for
These are uses of one spec format, not separate modes: the same spec renders as a film and as clips, and a video can mix them (a product shot between two Remotion scenes, a character film with a Remotion title card).
| The video is | Do | Then |
|---|---|---|
| A 3D short on its own (a gag, a parody shot) | render spec.json | qc.py --render, add music with addmusic.py |
| A Remotion video with a 3D character in some scenes | render --clips --alpha --to <project>/public/blender, set kind desk | <BlenderClip> over the scene's field |
| A Remotion video that turns out to be on a screen in a room | render the scene with Remotion, name it in set.screen.video, a pull_out shot, render --clips | hard cut from the flat scene to the clip |
| An app, a UI or a product shown as an object | set kind studio with a phone, card or model prop; reveal, orbit, product shots | a clip between scenes, or --alpha over the scene's field |
| A moviepy build, a video job or an edit in another tool that wants a 3D shot | render --clips (a picture-only .mp4 per shot, its effects as a .wav; --prores for editors) | VideoFileClip, a file scene in video_job.py, cutdown.py for 9:16 |
| Narrated, with acting on the words | a voice block and "at": "cue:..." | the spec follows the voice when it is re-timed |
For Remotion, set the spec's "fps": 30 (the composition's): a clip plays frame for frame.
When to suggest it. While planning any video, if blender_render.py doctor --no-bench exits 0, offer a
Blender shot where one fits: a character reacting, a reveal, a product or device shot. If Blender isn't
installed, don't propose it unless the user asks for 3D; then say what it needs (docs/blender.md).
The loop (do this, in this order)
- Write the spec from the brief or narration (below: From a brief to beats).
checkand read the report. Every shot prints PASS/FAIL, its exposure, and any camera fix the solver made ("swung +24 deg: nominal had view blocked by dev_hood"). Exit 1 on a failure, 2 on a spec error.- Look at
contact_sheet.png(read the PNG). Geometry can't judge everything: a hand over the key text, an expression that reads wrong, a beat landing in the wrong shot. Green bar = passed checks, red = failed. You wrote the spec, so you will see what you meant: for a film with a brief or a storyboard, also start a subagent with only a path to the stills inout/stills/copied to numbered names (no brief, board, spec or shot names; not the sheet, which prints each shot's name), have it retell what happens in time order and where the camera is, and mark each storyboard row seen, partly seen or not seen against that retelling. A row it did not name is a fault or a question. Do it again on the finished film, tiled withcontact_sheet.py --count.docs/blender.md, "A second reader who has not seen the brief". - Fix in the spec, not in Blender: change a shot's
type,az,dist,dur, or a beat'sat. If the solver had to move a camera, consider writing its fix into the spec ("az": ...) so the intent is explicit. - Repeat 2–4 until it passes and reads right, then
render. Check the result withuv run tools/contact_sheet.py out/<name>.mp4(cuts are detected), anduv run tools/qc.pyfor loudness.
check builds at the film's own shape (the spec's resolution scaled down), so a 9:16 spec is solved and judged
in 9:16. Never hand-edit scene.blend as the source of truth; it is rebuilt from the spec every run.
Spec format
{
"title": "Disk Panic", "fps": 24, "resolution": "1920x1080", "engine": "eevee",
"look": {"exposure": -0.9, "look": "AgX - Punchy"},
"set": {"kind": "desk_room", "palette": {...}, "screen": {...}},
"cast": [{"id": "dev", "kind": "clay_person", "colors": {"top": "#F26B1F"}}],
"shots": [{"id": "S1_wide", "dur": 3.0, "type": "wide"}, ...],
"beats": [{"at": "S1_wide+1.6", "do": "blink"}, ...],
"score": [{"from": 0, "to": "S2_alert+0.5", "mood": "calm"}, ...]
}
Also at the top level: "transparent": true (the same as --alpha) and "voice" (below), and "clock" (seconds): where
this spec starts on a longer film's timeline, so clips made from several specs breathe in step and join without a
jump. Start and end each such clip in the same pose, looking at the same thing.
Acting takes the same time at any fps. A blink, a typing rhythm and a head shake are written in seconds
inside the rig, so a 24 fps film and a 30 fps clip for Remotion act alike.
A mistake in a spec is named, with the choices. An unknown face, pose, shot type, subject or cast member is a spec error (exit 2) that lists what there is, before anything is rendered.
Times are seconds: a number (absolute), or relative to a shot: "S3" (its start), "S3+0.4",
"S3.end-0.2", "end". Write beats relative to the shot they play in, so changing one shot's dur keeps the
acting in step. Beats are applied in time order; a beat's length is dur (seconds) or until (a time).
Times from the narration. List the caption files tools/captions.py wrote, each with where its audio starts,
and a time can be the moment a word is said:
"voice": [{"captions": "../public/audio/scenes/02_alert.captions.json", "at": "S2_alert+0.3"}],
"beats": [{"at": "cue:disk is full", "do": "alert"},
{"at": "cue:full#2-0.1", "do": "expression", "face": "shocked"}]
cue: takes a word or a phrase (case and punctuation ignored), #2 for its second occurrence, and an offset. A
phrase that isn't in the narration is a spec error that prints what the narration does say, as cue() does in
Remotion. Paths are relative to the spec.
Cast
A cast member is a description, and every field is a named choice or a hex colour, so an agent can write one from a sentence ("a woman in her forties with a grey bob, glasses and a green shirt") or from a photo:
{"id": "maya", "kind": "clay_person", "seed": 12,
"body": {"build": "slim", "skin": "brown"},
"face": {"shape": "oval", "eyes": "brown", "brows": "thin", "nose": "small", "beard": "none"},
"hair": {"style": "bob", "color": "grey"},
"clothes": {"top": "shirt", "top_color": "#2E7D5B", "pants": "#252B45", "shoes": "#F0F0EC"},
"accessories": ["glasses"]}
| Field | Choices |
|---|---|
| body.build | average, slim, broad |
| body.skin | pale, light, tan, brown, dark, deep, or a hex colour |
| face.shape | round, oval, square |
| face.eyes | brown, hazel, green, blue, grey, or a hex colour |
| face.brows, face.nose | medium, thin, thick; round, small, long |
| face.beard | none, moustache, full |
| hair.style | tufts, short, bob, long, bun, curly, bald |
| hair.color | black, dark, brown, chestnut, red, blonde, grey, white, or a hex colour |
| clothes.top | hoodie, tee, shirt; top_color, pants, shoes are hex colours |
| accessories | any of glasses, headphones, earrings |
- Left out with no
seed: the defaults, which is the character the examples use. - Left out with a
seed: drawn from the seed.{"id": "extra", "seed": 41}is a whole person, the same one on every machine, and another seed is someone else. - A standing cast. Keep a character in its own file and name it:
{"id": "lead", "from": "../../kits/acme/cast/maya.json", "clothes": {"top_color": "#B23A48"}}. Fields besidefromoverride the fil
Truncated for display — read the full file on GitHub.
Related Skills
taste-skill
117.6kAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
ai-job-search
72.3kThe job search that runs on your machine. AI job application framework built on Claude Code: evaluate postings, tailor CVs, write cover letters, prep interviews. Fork it and own it.
claude-howto
47.4kA visual, example-driven guide to Claude Code — from basic concepts to advanced agents, with copy-paste templates that bring immediate value.
lobehub
85.7k🤯 LobeHub - Super-Agents on Your Team. Add super-agents to the chats your team already uses.They take on work by themselves and get better every week.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
