Guides
Claude skills for Blender: teach Claude your scene rules once
Claude skills for Blender explained: what a SKILL.md holds, how it pairs with Blender MCP, where to install it, and example skills for 3D work.
7 min read

Quick answer
What are Claude skills for Blender?
They are folders of instructions, each with a SKILL.md file, that Claude loads when a Blender task matches their description. A Blender skill can hold your naming rules, scale and export settings, or tested bpy snippets, so Claude follows them every time it builds or fixes a scene through Blender MCP.
What a skill is, in Blender terms
A Claude skill is a folder with a SKILL.md file in it. The file starts with two lines of metadata, a name and a description, and then holds plain-language instructions. The folder can also carry reference notes and scripts.
Anthropic's docs describe skills as loading in three levels, and that design is why they suit Blender work:
- Metadata, always loaded. About 100 tokens per skill: the name and description. This is how Claude knows the skill exists.
- Instructions, loaded on demand. The body of
SKILL.md, under about 5,000 tokens, enters the conversation only when your request matches the description. - Resources, loaded only when read. Extra files such as a
naming.mdor aexport_fbx.pystay on disk until Claude opens them. Scripts run, and only their output enters the context.
For a Blender user, that means you can keep a long "how we do things" document next to Claude without paying for it in every message. Ask about a car rig, and the rigging skill loads. Ask about a recipe and nothing does.
The source for all of this is the Agent Skills overview and the Claude Code skills docs.
A skill does not connect Claude to Blender
This is the most common mix-up. A skill is knowledge. It can't open a .blend file, move a vertex or press render. For that Claude needs tools, and in Blender the tools come from an MCP server:
- the official Blender Lab MCP server, which Claude's Blender connector is built on, or
- the community MCP for Blender add-on.
Both let Claude run Python inside Blender, read a summary of the scene and take viewport screenshots. Setup is covered step by step in How to connect Claude to Blender with MCP, and the background is in Blender MCP explained.
Once the tools are in place, a skill is what makes Claude's use of them consistent. Without one, Claude improvises: it guesses your units, names objects Cube.004, and exports with whatever FBX settings it picked last time. With one, it follows your house rules. The difference is laid out in Claude skills vs MCP for 3D work.

What belongs in a Blender skill
Good Blender skills hold the things you'd otherwise retype in every chat, or the things Claude keeps getting wrong. In practice, that's four kinds of content.
Project rules
- Units and scale: "1 Blender unit is 1 metre. Characters are 1.7–1.9 m tall."
- Naming: "Meshes are
SM_<Asset>_<Part>, materialsM_<Asset>, collections match the asset name." - Pivot and orientation: "Origin at bottom centre. Front faces -Y."
Export settings
Blender is Y forward and Z up, and most engines are not, so this is where a skill pays for itself. Write down the exact FBX or glTF settings your engine needs: Apply Scalings, Forward and Up axes, Apply Transform, Smoothing, Add Leaf Bones, and Path Mode with Embed Textures. Claude then uses the same settings on every export.
Tested snippets
Short bpy snippets you've verified on your Blender version: "apply scale to selected", "set origin to bottom centre", "export each selected object to its own GLB". Claude can adapt them, and it is far less likely to invent an API call that doesn't exist.
Check steps
A list Claude runs before it says it's done. Is every scale applied? Are there any n-gons? Is any texture missing from disk? Is the polycount under budget? This turns a chatty assistant into one that inspects its own work.
A minimal Blender skill
Here is the shape of a small skill for a game project. The folder is .claude/skills/blender-game-export/, and SKILL.md reads:
---name: blender-game-exportdescription: Use when preparing, cleaning or exporting Blender models for the game. Applies the project's scale, naming and FBX rules.---## Before exporting1. Apply scale and rotation on every selected mesh.2. Set each origin to the bottom centre of its bounds.3. Rename meshes to SM_<Asset>_<Part>; ask if the asset name is unclear.## ExportUse FBX with Apply Scalings: FBX All, Forward -Z, Up Y, Apply Transform on, Add Leaf Bones off.## ReportList each exported file with its triangle count. Stop and ask if any mesh is over 20,000 triangles.
That is the whole thing. The description is the most important line, because it is what Claude reads to decide whether the skill applies. Write it in the words you'd actually use when asking: "export", "clean up", "for the game". A full walkthrough is in How to write a SKILL.md for Blender.
Where to install it
Where the skill goes depends on which Claude you use. Custom skills don't sync between surfaces, so a skill uploaded to claude.ai is not automatically in Claude Code, and the other way round.
- Claude Code, one project:
.claude/skills/<name>/SKILL.mdin the project folder. Commit it, and everyone who clones the repo gets the same rules. - Claude Code, every project:
~/.claude/skills/<name>/SKILL.md. - claude.ai and Claude Desktop: upload it as a custom skill. That needs a Pro, Max, Ultra, Team or Enterprise plan with code execution turned on.
In Claude Code you can call a skill directly with /blender-game-export. You can also let Claude load it automatically when your request matches the description. If you only want it to run when you ask, add disable-model-invocation: true to the frontmatter. The trade-offs between surfaces are covered in Claude skills in claude.ai vs Claude Code.
Prompts that work once a skill is installed
With Blender MCP connected and a project skill installed, short prompts start doing a lot more work:
- "Clean up the selected props for export." The skill supplies what "clean up" means.
- "Export everything in the Props collection." The skill supplies the format, axes and naming.
- "Check this scene against our rules and list what fails." The skill's check steps become the checklist.
- "Build a 6 m wooden fence along X with posts every 1.5 m, using our naming." Claude writes the Python, and the skill keeps the names and units right.
If Claude does something your skill says not to, don't just correct it in chat. Edit the skill, so the fix sticks for the next session.
What a skill can't do
Be clear-eyed about this before you invest an afternoon in one:
- It can't add abilities Claude doesn't have. A skill doesn't let Claude see your viewport without screenshot tools, or sculpt by hand. It only shapes how Claude uses the tools it already has.
- It isn't a guarantee. Claude reads the instructions and usually follows them, but a check step is still worth more than a "never do X" line. Ask for a report you can verify.
- It won't make organic modelling easy. Claude in Blender builds well from code and primitives: fences, shelves, modular kits. A detailed creature or a carved prop is still faster to generate than to script.
- It carries risk if you didn't write it. Skills can include scripts. Anthropic's advice is to use skills only from trusted sources and to read every bundled file before installing.
Where generated models fit
Most Blender scenes need props that no one wants to script, so a common split is:
- Generate the detailed objects from a prompt, image or sketch.
- Let Claude, guided by your skill, import, scale, name, arrange and export them.
Vi3W covers the first half. It makes the mesh from text, an image or a sketch, and Clean shape brings the face count down. New paint job changes the textures, and Add bones and Make it move rig and animate characters. Download GLB or FBX and hand it to Claude in Blender. The Vi3W MCP server, live from today, lets Claude call the same tools from the chat. Claude skills for 3D AI shows how a skill can drive that whole loop, and Best Claude skills for 3D artists lists more skills worth writing.
Frequently asked questions
claude skills for blender
A Claude skill for Blender is a SKILL.md file (plus optional scripts) that tells Claude how you want Blender work done. It does not connect Claude to Blender by itself; pair it with Blender MCP so Claude can act on the scene.
claude skills for blender mcp
Use both. Blender MCP gives Claude the tools (run Python, read the scene, take screenshots); the skill tells Claude which tools to use, in what order, and which of your rules to check before it reports done.
claude code skills for blender
In Claude Code, put the skill in .claude/skills/<name>/SKILL.md inside your project, or in ~/.claude/skills/ for every project. Call it with /<name> or let Claude load it when your request matches its description.
Last reviewed

