SkillAgentSearch skills...

export-pipeline

Production export from Blender to FBX, GLTF, OBJ, USD, and Alembic with scale, pivot, rotation, normals, materials, animation, and collision verification via MCP.

Install / Use

npx skills add arjun988/blender-skills --skill export-pipeline

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

91/100

Category

Automation

Supported Platforms

Universal

Our assessment of export-pipeline

export-pipeline scores 91/100 on our quality scale, 963rd of 2,790 Automation skills we index (top 35%).

Its SKILL.md is 4.1 KB long, well organised into 22 sections with 6 code examples: a solid amount of guidance for an agent.

With 3,810 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
26/30
Structure
20/20
Description
15/15
Adoption
15/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated 10 days ago, so export-pipeline is actively maintained.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

export-pipeline compared with similar skills

All 4 of these similar skills score higher than export-pipeline; compare them before choosing.

SkillScoreStarsUpdatedFormat
export-pipeline (this skill)by arjun988913.8k10d agoSKILL.md
Agent-Reachby Panniantong100112.3k8d agoCLAUDE.md
rufloby ruvnet10081.9ktodayCLAUDE.md
headroomby headroomlabs-ai10079.8ktodayCLAUDE.md
CowAgentby zhayujie10048.0ktodayCLAUDE.md

Frequently asked questions

How do I install export-pipeline?
Run npx skills add arjun988/blender-skills --skill export-pipeline. The install tabs above show the steps for each supported agent.
Which AI agents does export-pipeline work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is export-pipeline safe to use?
It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is export-pipeline still maintained?
The repository was last updated 10 days ago, so export-pipeline is actively maintained.

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

## 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 |

Related Skills

View on GitHub
GitHub Stars3.8k
CategoryAutomation
Updated10d ago
Forks342

Languages

TypeScript

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions