agentsclimarketplace

Asset optimization

Skill arjun988/blender-skills/.claude/skills/asset-optimization

Validates and optimizes Blender assets for polycount, topology, UV efficiency, material count, naming, collections, and game-ready performance. Use before export on all production assets via MCP.From its SKILL.md

Install
npx -y skills add arjun988/blender-skills --skill asset-optimization

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

What its file declares

Copied from the file, not written here

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

3.7 KB, 774 tokens by cl100k_base, as published. Nobody here has run it

Asset Optimization

Enforce budgets. Clean geometry. Game-ready validation gate before export.

When to Use

  • Before every export
  • After modeling complete
  • LOD generation
  • Scene-wide performance audit
  • Pre-delivery validation

Workflow

Audit → Identify Issues → Fix → Re-Audit → LOD Generation → Validation Report

Audit Checklist

Run via MCP scene queries where possible:

Geometry

  • Triangle count vs budget (../references/polycount-budgets.md)
  • Duplicate vertices merged
  • Loose geometry removed
  • Non-manifold fixed
  • Interior faces deleted
  • Applied transforms (scale 1,1,1)

UVs

  • Pack efficiency > 75%
  • Texel density consistent
  • No unintended overlaps

Materials

  • Count within budget
  • No unused slots
  • Names follow MAT_ convention

Organization

  • All objects named SM_ prefix
  • Collections organized per convention
  • Collision meshes in COL_Collision

Optimization Techniques

IssueFix
Over budgetRemove unseen geo, decimate, bake detail
High triangle count on flat surfacesReduce subdiv/bevel segments
Many draw callsMerge materials; atlas textures
Repeated geometryConvert to instances
Heavy modifiersApply and merge strategically

LOD Generation

LOD0: Full detail (hero)
LOD1: 50% tris — remove micro-bevels, small greebles
LOD2: 25% tris — decimate modifier; preserve silhouette
LOD3: 10% tris — impostor/card or simple proxy

Naming: SM_Asset_LOD0, SM_Asset_LOD1, etc.

Use Decimate modifier:

  • Planar mode for hard surface
  • Collapse mode for organic
  • Always verify silhouette after decimate

Modifier Cleanup

Before export:

  1. Apply stack OR export with modifiers per engine support
  2. Remove unused modifiers
  3. Collapse mirror/array if instances not needed
  4. Document which modifiers remain live

Scene Audit Report Template

## Optimization Report: [Asset/Scene]

**Total Triangles:** [count] (budget: [target])
**Draw Calls (materials):** [count]
**Objects:** [count]
**Issues Fixed:** [list]

### Per-Object Breakdown
| Object | Tris | Materials | Status |
|--------|------|-----------|--------|
| SM_... | ... | ... | PASS/FAIL |

MCP Integration

  1. Query polycount per object via MCP
  2. Query material count via MCP
  3. Run cleanup operations via MCP
  4. Generate LOD duplicates via MCP
  5. Validate naming conventions via MCP scene tree

Constraints

MUST DO

  • Run full validation before export
  • Document polycount in production brief
  • Create LODs for hero assets in games
  • Fix all non-manifold before export
  • Output validation report

MUST NOT DO

  • Export without budget check
  • Decimate deforming meshes without testing
  • Remove collision proxies
  • Skip naming convention validation
  • Optimize hero face/hands below animation needs

Reference Guide

TopicReferenceLoad When
Full validation../references/validation-checklist.mdFinal gate
Polycount budgets../references/polycount-budgets.mdBudget setting
LOD strategiesreferences/lod-strategies.mdLOD creation

What ships with it: 1 file

514 B alongside SKILL.md

references/

Gives 0 of the 12 instructions most performance cost skills give in 774 tokens

Counted across 797 of the 1,117 authors here whose files we hold, read 2026-09-06

  • Check for product marketing context firstin 46 of 797, across 20 files
  • Measure before optimizingin 31 of 797, across 25 files
  • Profile first to identify the actual bottleneckin 23 of 797, across 22 files
  • Verify your robots.txt allows AI crawlersin 21 of 797, across 12 files
  • Import directly and avoid barrel filesin 19 of 797, across 15 files
  • Spawn all runs in the same turnin 18 of 797, across 11 files
  • Write a draft of the skillin 17 of 797, across 10 files
  • Understand the user's intentin 17 of 797, across 10 files
  • Use React.cache for per-request deduplicationin 16 of 797, across 11 files
  • Profile before optimizingin 16 of 797, across 14 files
  • Include specific numbers with sourcesin 15 of 797, across 8 files
  • Add lazy loading to below-fold imagesin 15 of 797, across 10 files

Said here and by no other author read

  • Run full validation before export
  • Document polycount in production brief
  • Create LODs for hero assets in games
  • Fix all non-manifold before export
  • Output validation report
  • Merge duplicate vertices

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.