Blender Rendering logo

Blender Rendering

Community
EL4CTEO
blender-rendering

Render with Blender 5.2 Cycles/EEVEE/Workbench - quality presets, GPU setup, adaptive sampling, denoising, light paths, color management (AgX, Khronos PBR Neutral, ACES), PNG/EXR/MP4 output, passes, the 5.0 compositor API, CLI and multi-camera batch rendering. Use for any still, animation or turntable render.

Overview

PublisherEL4CTEO
Repositoryblender-skills
Skill nameblender-rendering
Stars
426
Forks
39
Bundled files
2
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.

  • 2 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 Rendering 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-rendering
  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-rendering .claude/skills/blender-rendering
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Blender Rendering 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 Rendering 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 Rendering 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.

Rendering

The execution model is in blender-core. Scene lighting and cameras are in blender-lighting-lookdev.

One call

scripts/render_batch.py -- --engine CYCLES --preset final --res 1920 1080 --out //render/hero_#### --frames 1
scripts/render_batch.py -- --preset preview --frames 1-120 --format MP4 --out //render/turntable
scripts/render_batch.py -- --cameras CamA CamB CamC --format EXR_MULTI --out //render/shots/

Presets: preview (Cycles 64 spp, threshold 0.05, 50% res; EEVEE 16), final (512 spp, 0.01; EEVEE 128 + raytracing), product (1024 spp, transparent background). GPU is picked automatically (OptiX > CUDA > HIP > Metal > oneAPI), and the denoiser matches (OptiX or OpenImageDenoise).

Engine choice

EngineUseNotes
Cyclesfinal quality, product, archviz, glass/SSS/caustics, bakingpath tracer; set the GPU; adaptive sampling + denoise
EEVEE (5.x, ex-"Next")fast look-dev, stylized, motion graphics, previewsray-traced reflections/GI (use_raytracing), virtual shadow maps; needs a GPU even headless
Workbenchplayblasts, clay/matcap reviews, QA sheetsinstant, no lighting accuracy
Engine ids: CYCLES, BLENDER_EEVEE, BLENDER_WORKBENCH.

Cycles quality levers (ordered by impact)

  1. Adaptive sampling (adaptive_threshold 0.01 final / 0.05 preview) + denoise (OIDN with albedo+normal passes, denoising_input_passes="RGB_ALBEDO_NORMAL"). Raising samples alone is the least efficient fix.
  2. Light paths: interiors need diffuse bounces ≥ 4. Product shots: total 12, glossy 4, transmission 8–12 for glass. Clamp indirect 5–10 kills fireflies at a small energy cost.
  3. Light tree (use_light_tree, on) for many lights. Path guiding (CPU only) for difficult indirect light.
  4. Fewer, larger lights beat many small ones. Emissive meshes are noisier than area lights.
  5. Persistent data (render.use_persistent_data) speeds up animations and turntables. Use simplify (max subdivision, texture limit) for previews.
  6. 5.2: texture cache (render.use_texture_cache, use_auto_generate_texture_cache) cuts memory in texture-heavy scenes by generating .tx mip tiles.

Color management (decide once per project)

  • AgX (default): photographic, handles bright highlights. Looks: AgX - Punchy, - Base Contrast...
  • Khronos PBR Neutral: shows albedo faithfully. Use it for product/e-commerce and asset reviews, and to match three.js NeutralToneMapping.
  • Standard: graphics/UI/texture output that must match pixel values.
  • ACES 1.3 / 2.0: VFX pipelines (plates, other DCCs).
  • Use exposure (view_settings.exposure), not light power, for global brightness tweaks. Display device sRGB, or Display P3 / Rec.2100 for HDR delivery.

Output formats

  • Stills: PNG 8/16-bit (RGBA when the film is transparent) or JPEG for web previews.
  • Comp/VFX: EXR multilayer (EXR_MULTI, DWAA 16-bit) with passes (Denoising Data, Cryptomatte, AO, Mist, Z). 5.0 renamed passes: Diffuse Color, Depth, etc.
  • Video: render frames first (PNG/EXR), then encode (FFmpeg or the VSE), because a crash mid-MP4 loses everything. Direct MP4 is fine for previews. Set image_settings.media_type before file_format (5.0+).
  • Transparent: film_transparent=True + PNG/EXR. A glass-only alpha needs film_transparent_glass.

Compositor (5.0+ API)

python
ng = bpy.data.node_groups.new("Comp", "CompositorNodeTree"); scene.compositing_node_group = ng
ng.interface.new_socket("Image", in_out="OUTPUT", socket_type="NodeSocketColor")
rl, glare, out = ng.nodes.new("CompositorNodeRLayers"), ng.nodes.new("CompositorNodeGlare"), ng.nodes.new("NodeGroupOutput")
ng.links.new(rl.outputs["Image"], glare.inputs["Image"]); ng.links.new(glare.outputs["Image"], out.inputs[0])

There's no Composite node anymore: the group output is the final image. Many node options are now input sockets (Glare Type, Threshold, Strength), so --describe them with blender-geometry-nodes/scripts/gn_builder.py. File Output node: directory, file_name, file_output_items.

CLI rendering (render farms, CI)

  • blender -b scene.blend -E CYCLES -o //out/frame_#### -F PNG -s 1 -e 120 -a renders an animation. -f 10 renders a single frame. Python args go after --.
  • -- --cycles-device OPTIX (or CUDA/HIP/METAL/ONEAPI) selects the device without Python.
  • Split frames across machines with -s/-e, or with Placeholders + No Overwrite (render.use_placeholder, use_overwrite=False) on shared storage.

Gotchas

  • scene.render.engine enum under-reports (add-on engines). Assign in try/except (the script does).
  • EEVEE in background still needs a GPU context. In CI without a GPU, use Cycles CPU or Workbench.
  • bpy.ops.render.render(write_still=True) writes render.filepath. Without write_still, the result only lives in Render Result.
  • Noise in glass/caustics: enable caustics only if needed (caustics_refractive), raise transmission bounces, or fake it with Thin Wall (5.2) for windows.
  • Fireflies: clamp indirect, a filter glossy / blur glossy (blur_glossy 0.5–1), and bigger light sources.

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 Rendering AI skill do?

Render with Blender 5.2 Cycles/EEVEE/Workbench - quality presets, GPU setup, adaptive sampling, denoising, light paths, color management (AgX, Khronos PBR Neutral, ACES), PNG/EXR/MP4 output, passes, the 5.0 compositor API, CLI and multi-camera batch rendering. Use for any still, animation or turntable render.

Why use Blender Rendering on TypingMind?

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

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

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 Rendering?

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

Is the Blender Rendering 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 👇