94 Blender Skills That Turn Your Coding Agent Into a Technical Art Team

Coding agents can describe Blender workflows all day; they still cannot click a single vertex. arjun988/blender-skills (v1.3.0, MIT) closes that gap: 94 skills that plan the pipeline like a senior technical artist and then execute it inside Blender itself through the Blender MCP connection. One pack serves Cursor, Claude Code, Kiro, and Codex.

Why This Skill Matters

Most "Blender AI" content teaches you the UI. This pack takes the opposite stance — its philosophy section says skills think before acting and never narrate UI steps, because execution happens over MCP. The 94 skills (the README's category table sums to the same number the directory holds, with one shared references/ folder) cover an unusual breadth: modeling and production phases like sculpting, retopology, and UV work; a technical row with geometry nodes, lighting, rigging, and VFX; a pipeline row covering optimization, LOD, collision proxies, and per-engine export for Unity, Unreal, and Godot; 23 style skills from lowpoly to PSX horror; horror packs, world and mood packs, and game-genre direction.

The router is the design decision worth noticing: a blender-director skill reads your request and chains the specialists — the README's hero-prop example routes through hard-surface, UV workflow, materials, asset optimization, and export.

Installation

The marketplace listing is under review by Anthropic, so the README says to install from GitHub in the meantime. For Claude Code:

git clone https://github.com/arjun988/blender-skills.git
cp -r blender-skills/.claude/skills /path/to/your/project/.claude/skills/

Skills alone can plan, but execution needs the MCP bridge, and the README's setup is four steps: install uv, install the BlenderMCP addon in Blender, connect from the sidebar (press N, open the BlenderMCP panel, connect), then restart your agent — the repo ships .mcp.json for Claude Code and .cursor/mcp.json for Cursor.

Real Workflow: A Game-Ready Prop, Routed End to End

1. With Blender running and the MCP bridge connected, prompt the agent:

为 Unreal Engine 建一把可用于游戏的科幻步枪，3000 三角面，写实 PBR 材质

2. blender-director parses the constraints — engine, polycount budget, material style — and routes the README's documented chain: hard-surface modeling, then UV workflow, materials, asset optimization, and the export pipeline.

3. The skill validates before delivery: the philosophy section commits every skill to optimization and checklist gates on export, and production standards cover naming conventions and polycount budgets.

The same shape works for characters (sculpting through rigging and animation) and environments — the README prints five complete pipelines, including a horror-environment chain that routes through horror-style and lowpoly-style.

Real Workflow: Build From a Reference Photo

Attach a photo or concept art and name the target:

匹配这张参考图——工业风宇宙飞船，先分析再在 Blender 里建模

reference-image-match runs the README's documented loop: analyze the reference, match the camera, build geometry in tiers, apply materials and lighting, then screenshot-compare against the source and iterate — a feedback cycle that plays to the strengths of an agent that can both see and drive the scene.

Tips

• SKILLS_GUIDE.md is the real index: full skill list, subtype coverage map, decision trees, and workflow combinations. Start there before picking skills by name.
• The five pre-built pipeline chains in the README are templates — swap the style skill to reuse the same route for a different look.
• The shared references/ folder carries the pipeline standards (naming, MCP tools, checklists) for the pack.
• Version history lives in CHANGELOG.md; the current release is v1.3.0.

When Not to Use This

The pack is built around execution: its own philosophy says skills use Blender MCP tools when connected and never narrate UI steps. Without a running Blender and the BlenderMCP addon there is no execution path, and a written tutorial is exactly what this pack refuses to be — pair it with Blender's own docs if you want to learn the UI. The scope is Blender; the README draws no line beyond it, so teams on other DCC tools should look elsewhere. And since the marketplace listing is still under review, the GitHub install route is the supported one today.

See the leaderboard for more skills.