export-pipeline — Claude Code skill: exporting 3D assets from Blender
export-pipeline — a skill that automates 3D asset exports from Blender to game engines. Validates mesh parameters to ensure engine-ready output.
MIT 664 installs ★ 4,589 updated 2026-11-06
npx skills add arjun988/blender-skills --skill export-pipeline -a claude-codeWhat export-pipeline does
This skill prepares assets for import into Unreal Engine, Unity, or Godot. It manages correct scaling, pivot orientation, and data exports for FBX, GLTF, GLB, OBJ, USD, and Alembic formats.
Before export, the skill mandates a validation pass using asset-optimization. It utilizes MCP to manage collections and configure export settings. Ensure all transforms are applied to objects in the scene before triggering the process.
The tool handles collision mesh separation and material mapping. It also generates documentation templates to communicate asset settings to team members.
What it helps with
- configure standardized 3D exports for game engines
- verify model scale and axes before engine import
- automate collision mesh exporting
- document technical asset parameters for delivery
Example prompts for the agent
- Apply
FBXexport settings usingexport-pipeline - Export the
modular_kitcollection forUnreal Engine - Validate
SM_Asset_01for export
How to install export-pipeline
1Skills CLI (Vercel)
npx skills add arjun988/blender-skills --skill export-pipeline -a claude-code2Manually: put the files in place
~/.claude/skills/export-pipeline/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/export-pipeline/
1Skills CLI (Vercel)
npx skills add arjun988/blender-skills --skill export-pipeline -a codex2Manually: put the files in place
.agents/skills/export-pipeline/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add arjun988/blender-skills --skill export-pipeline -a cursor2Manually: put the files in place
.cursor/skills/export-pipeline/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install arjun988/blender-skills .claude/skills/export-pipeline2Manually: put the files in place
.github/skills/export-pipeline/SKILL.md1Skills CLI (Vercel)
npx skills add arjun988/blender-skills --skill export-pipeline -a gemini-cli2Platform CLI
gemini skills install https://github.com/arjun988/blender-skills --path .claude/skills/export-pipelineManually: put the files in place
.devin/skills/export-pipeline/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add arjun988/blender-skills --skill export-pipeline -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about export-pipeline
How to install export-pipeline in Claude Code?
Run npx skills add arjun988/blender-skills --skill export-pipeline -a claude-code.
What does export-pipeline do?
It standardizes the Blender-to-engine pipeline, eliminating common issues with pivot points, scale, and material slots during asset delivery.
What is required to use export-pipeline?
The asset-optimization skill is required for pre-export validation, alongside an active connection for MCP operations.
Source text
SKILL.md · MIT
---
name: export-pipeline
description: Production export from Blender to FBX, GLTF, OBJ, USD, and Alembic with scale, pivot, rotation, normals, materials, animation, and collision verification via MCP.
license: MIT
metadata:
author: https://github.com/arjun988
version: "1.0.0"
domain: blender
role: specialist
triggers: export, FBX, GLTF, GLB, OBJ, USD, Alembic, Unity, Unreal, game engine import
related-skills: asset-optimization, blender-modeler, materials
---
# Export Pipeline
Verified, engine-ready exports. Correct scale, axis, pivots, and data.
## When to Use
- Final asset delivery
- Engine import preparation
- Animation/rig export
- Batch export of modular kits
## Pre-Export Gate
**Required:** asset-optimization validation PASS before export.
## Workflow
```
Validation PASS → Export Settings → Test Export → Engine Verify
→ Fix Issues → Final Export → Documentation
```
## Format Selection
| Format | Best For |
|--------|----------|
| FBX | Unreal, Unity (legacy), animation |
| GLTF/GLB | Web, Godot, modern Unity |
| OBJ | Static mesh interchange (no rig) |
| USD | Pipelines, VFX, multi-asset |
| Alembic | VFX caches, sculpt animation |
## FBX Settings (Game Default)
```
Scale: 1.0
Apply Scalings: FBX All
Forward: -Z Forward
Up: Y Up
Apply Unit: ON
Mesh: ON
Armature: ON (if rigged)
Bake Animation: ON (if animated)
Path Mode: Copy (embed textures)
```
## GLTF Settings
```
Format: GLB (single file) or GLTF Separate
Include: Selected Objects
Transform: +Y Up
Compression: Draco (if supported by engine)
```
## Export Verification Matrix
| Check | Method |
|-------|--------|
| Scale | Measure known dimension in engine |
| Pivot | Verify floor contact / grip point |
| Forward axis | Compare to engine convention |
| Normals | Check shading in engine |
| Materials | Verify slot count and textures |
| Animation | Play action in engine |
| Collision | Import COL_ mesh separately |
## Engine-Specific Notes
### Unreal Engine
- Scale 1.0 = 1cm in UE (confirm project; may need 0.01 export scale)
- Import normals and tangents
- Separate collision mesh import
- LOD naming for auto-LOD: `SM_Asset_LOD0`
### Unity
- Scale 1.0 typically correct
- GLTF preferred for modern pipelines
- Humanoid rig mapping for characters
### Godot
- GLTF/GLB preferred
- +Y up default
## Collision Export
```
1. Export render mesh separately from collision
2. Collision: simple convex or box
3. Name: SM_Asset_COL
4. No materials on collision mesh
5. Apply transforms before export
```
## Animation Export
- Single action per export file (or document action list)
- Sample rate: 30fps default
- Bake constraints before export
- Include armature + skinned mesh in same file
- No unapplied scale on rig
## Batch Export (Modular Kits)
```
1. Select COL_Export collection
2. Export each module OR combined atlas per project spec
3. Maintain consistent origin per module type
4. Document grid snap points in README
```
## MCP Integration
1. Select export collection via MCP
2. Configure export settings via MCP
3. Execute export via MCP
4. Verify output file exists
5. Log export settings in delivery documentation
## Delivery Documentation Template
```markdown
## Export Package: [Asset Name]
**Format:** FBX / GLTF
**Scale:** 1 Blender unit = 1 meter
**Forward:** -Y / +X (document actual)
**Files:**
- SM_Asset.fbx
- T_Asset_BC.png, T_Asset_N.png, ...
**Import Notes:**
- [Engine-specific steps]
**Validation:** PASS — [date]
```
## Constraints
### MUST DO
- Pass asset-optimization before export
- Apply transforms on export objects
- Test import in target engine
- Document scale and axis conventions
- Export collision separately for games
### MUST NOT DO
- Export with unapplied scale
- Export without validation
- Mix collision and render in same export without documentation
- Assume default FBX settings work for all engines
- Export all modifiers without testing engine result
## Reference Guide
| Topic | Reference | Load When |
|-------|-----------|-----------|
| Engine import | `references/engine-import.md` | First import test |
| Validation | `../references/validation-checklist.md` | Pre-export gate |
© https://github.com/arjun988 · MIT · arjun988/blender-skills