blender-skilllisted
Inspect, convert, optimize, render, bake and validate 3D assets with local, headless Blender: glb/gltf, fbx, obj, stl, usd/usdz, ply, abc, .blend. Cut triangle count, cap texture resolution, bake AO/normal/roughness/diffuse/combined maps, render a thumbnail/turntable/4-view sheet, check a file against three.js/Unity/Unreal/Godot/iOS-AR/Android-AR/WebXR/3D-print/Sketchfab budgets, assemble a multi-asset scene. Use this skill whenever the user mentions a 3D model or asset file (glb, gltf, fbx, obj, stl, usd, usdz, ply, blend), a mesh, polycount/triangle count, UV, texture baking, decimation, a turntable render, an AR/game-engine import, or asks to check/optimize/convert/render something "for Unity", "for Unreal", "for the web", "for AR" -- even when they do not say "Blender". Headless only (`blender -b`); this is not a replacement for interactive modeling or the official Blender MCP add-on, and complements rather than competes with it. Requires Blender 4.2+ on the machine; no API keys, no cloud, no pip dependen
zobaerio/zobvia · ★ 1 · AI & Automation · score 77
Install: claude install-skill zobaerio/zobvia
> **Bundled with Zobvia** (extras/blender-skill/) — see the sub-skill parts of Zobvia's SKILL.md. Source: [kajisho5/blender-skill](https://github.com/kajisho5/blender-skill) v0.31.0 (main @ fad904d), MIT License (LICENSE in this folder). Bundled: SKILL.md, `scripts/`, `references/`. Not bundled: docs, tests (8 MB of fixtures), brand, MCP/npm packaging. Requires Blender 4.2+ on the machine (headless `blender -b`); the host CLIs are Python stdlib only. NOTE: Blender is not installed on every machine — run a tool's doctor/check first and report honestly if the binary is missing.
# blender-skill
Scripts live in `scripts/` next to this file; run them with `python3 <skill-dir>/scripts/<name>.py`.
Each is a thin host-side CLI (stdlib only) that launches Blender headless
(`blender -b --factory-startup --python scripts/bpy/<name>.py -- args.json result.json`) and
reads back a JSON result written to disk -- never by parsing Blender's own log output. `--help`
on the script you are about to run is the cheapest full flag list; `references/pitfalls.md` is
the long form of real gotchas hit building this (GPU-offscreen limits under `-b`, format
roundtrip quirks, an Eevee engine-name rename between Blender versions) -- read it when
something behaves unexpectedly rather than guessing.
Shared flags, on every script: `--json` (structured result instead of a one-line summary --
prefer it for anything you'll act on programmatically); `--blender PATH` (override Blender
discovery: `--blender` >