agentleFS
arjun988arjun988/blender-skills/.claude/skills/export-pipeline/SKILL.md

export-pipeline

Skill2.2k starsChanged 4 months agoMITView on GitHub

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

2 other projects use a version of this.

Adopted by

Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data

Week of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 0 new projectsWeek of Oct 25: 0 new projectsWeek of Nov 1: 0 new projectsWeek of Nov 8: 0 new projects
Sep 2026Oct 2026Nov 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 0 in all, so this is a hint, not a trend.

Most recently taken up by

Who's talking about arjun988/blender-skills

The biggest 5 of 12 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 12

Talked about on GitHub (12 times).

On GitHub · 12

7 more on GitHub

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Import normals and tangents

    line 85
  2. Distinctive:

    No unapplied scale on rig

    line 114
  3. Distinctive:

    Verify output file exists

    line 130
  4. Distinctive:

    Test import in target engine

    line 156
  5. Distinctive:

    Document scale and axis conventions

    line 157

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

FormatBest For
FBXUnreal, Unity (legacy), animation
GLTF/GLBWeb, Godot, modern Unity
OBJStatic mesh interchange (no rig)
USDPipelines, VFX, multi-asset
AlembicVFX 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

CheckMethod
ScaleMeasure known dimension in engine
PivotVerify floor contact / grip point
Forward axisCompare to engine convention
NormalsCheck shading in engine
MaterialsVerify slot count and textures
AnimationPlay action in engine
CollisionImport 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

TopicReferenceLoad When
Engine importreferences/engine-import.mdFirst import test
Validation../references/validation-checklist.mdPre-export gate

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.