Scenario Maya Retopology Uv
Use when turning a dense sculpt, scan, ZBrush export or AI-generated mesh into...
Install
npx skills add scenario-labs/skills --skill scenario-maya-retopology-uv -g -a claude-code -y- Repository
- scenario-labs/skills1.4k
- Category
- Design
- Updated
- 3d ago
- License
- MIT
- Context cost
- Mediumabout 3,000 tokens
- Runs scripts
- Yes, review before use
What it does
Use when turning a dense sculpt, scan, ZBrush export or AI-generated mesh into animation-ready or game-ready topology in Maya without a mouse ("clean up this AI mesh", "retopo this character", Quad Draw, Retopologize), testing it deforms before rigging (bad elbow or wrist bend, lids popping through the eyes), or unwrapping UVs, cutting seams, setting texel density, mip-safe padding, UDIMs, lightmap UVs, stacking mirrored shells, or preparing a low poly and cage for baking. Keywords: edge flow, eye and mouth loops, Unfold3D, bake prep.
Maya retopology and UVs
Expert retopology is a loop plan with the fewest polygons that still deform: landmarks first, rings
around eyes and mouth, three loops per joint, poles where nothing moves, a bend test that says whose
fault a bad crease is. Expert UVs spend texels where the camera looks, at a density derived from the
closest shot, with padding that survives mips. Without a mouse the agent reuses approved topology,
builds from data, and measures then renders every stage. If a sibling skill named here is missing
from your available skills, load it with skill_get (Scenario MCP) or ask the user to install it
(https://github.com/scenario-labs/skills#install); unattended, proceed from tool schemas and flag
the gap.
REQUIRED BACKGROUND: scenario-maya-expert (execution channel, review loop, 2027 version traps).
Toolkit: scripts/mx_retopology_uv.py
(import mx_retopology_uv as RU), built on mx_audit, mx_review and mx_run.
Status (2026-09-24): every Maya call is not yet run in Maya (not installed); 99 pure and 40
fake-Maya checks pass offline. First run tests/code/maya-retopology-uv/run_all.sh, then fix what
job_probe_commands reports.
