# scenario-maya-modeling

The scenario-maya-modeling skill guides Maya modeling and topology cleanup for game props, SubD assets, and deforming characters. Use it when shaping a mesh or preparing it for UVs or rigging.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode, Windsurf (Devin Desktop), Claude.ai · 426 installs · ★ 3964 repo stars
- Author: scenario-labs
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/scenario-labs/skills/tree/HEAD/skills/dcc/maya/scenario-maya-modeling/SKILL.md
- Updated: 2026-10-23
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/skills/scenario-maya-modeling

## What it does

The skill approaches a model from large forms to small details. It guides support-loop placement, triangle cleanup, and topology for deforming surfaces, with choices shaped by the asset’s purpose, mesh density, and camera distance. A metallic highlight render is one way it recommends checking the surface rather than trusting the wireframe alone.

The toolkit includes `scripts/mx_modeling.py` and the tools `mx_audit`, `mx_validate`, `mx_review`, and `mx_run`. It requires `scenario-maya-expert` as background for execution and review; without that dependency, the toolkit workflow has a gap. The Python layer passed offline tests, while Maya calls still need validation with `tests/code/maya-modeling/run_all.sh`.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add scenario-labs/skills --skill scenario-maya-modeling -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/scenario-maya-modeling/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/scenario-maya-modeling/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add scenario-labs/skills --skill scenario-maya-modeling -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/scenario-maya-modeling/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add scenario-labs/skills --skill scenario-maya-modeling -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/scenario-maya-modeling/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install scenario-labs/skills skills/dcc/maya/scenario-maya-modeling
```

2. **Manually: put the files in place**
- File: `.github/skills/scenario-maya-modeling/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add scenario-labs/skills --skill scenario-maya-modeling -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/scenario-labs/skills --path skills/dcc/maya/scenario-maya-modeling
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/scenario-maya-modeling/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add scenario-labs/skills --skill scenario-maya-modeling -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/scenario-labs/skills/tree/HEAD/skills/dcc/maya/scenario-maya-modeling/SKILL.md

## When to use it
- choose mesh density for an asset’s camera distance
- clean up pinching and uneven surface highlights
- prepare character topology for deformation
- check a mesh for non-manifold or zero-length geometry
- reduce a game mesh while preserving useful edge loops

## Example prompts
- Model a game prop in Maya and explain which edges to keep for this triangle budget.
- Check this mesh before UV work and suggest fixes for its topology problems.
- Prepare this character mesh for deformation and place the supporting loops.

## Source text · SKILL.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: b8fa637211c383cb.

BEGIN THIRD-PARTY FILE b8fa637211c383cb
```text
---
name: scenario-maya-modeling
description: 'Use when modeling in Autodesk Maya, such as hard-surface props, weapons, vehicles, a sci-fi crate, a game-ready or SubD film model, or a character or creature base mesh, or when asked to "clean up this model" or a scene before rigging or UVs. Also for support loops vs bevels vs creases, Smart Bevel, weighted normals, hard edges, pinching or wobbly highlights, a faceted cage, flipped faces, a triangle budget, n-gons, non-manifold geometry, mirroring a half, a low poly from a high poly, or deformation-ready topology.'
license: MIT
---

# Maya modeling (hard surface, organic, props)

Expert modeling is purposeful topology: every loop exists for the silhouette, a highlight, a bake, a
UV seam or a joint, and the model arrives downstream with nothing the next person has to clean. The
agent works big to small, measures each stage with the toolkit, and looks at a metal highlight
render before believing a surface. 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_modeling.py`](scripts/mx_modeling.py)
(`sys.path[:0] = ["<skills>/scenario-maya-modeling/scripts", "<skills>/scenario-maya-expert/scripts"]; import mx_modeling as MM`),
used with `mx_audit`, `mx_validate`, `mx_review`, `mx_run`. **Not yet run in Maya:** its pure-Python
layer passed offline tests; every Maya call is pending `tests/code/maya-modeling/run_all.sh`.

## Stance (the expert delta)

- **Purpose first, then density.** A still from CAD or booleans can skip clean topology; games,
  animation and close-ups cannot (Mario Elementza [00:00:32]). Minimum density is the narrowest
  feature, "the shortest distance between the two edges" [00:17:19]; then camera distance decides:
  low density needs redirected edges and pinches slightly (background), high density needs none
  (hero close-up) [01:09:20] [01:39:46]. Vertex count is the real cost: UV seams, hard edges and
  materials split vertices; a hard edge on a UV seam is free (Polycount).
- **Clean uncut form, then cut.** On flats, offset before cutting: the offset ring becomes the
  support loop; on curved parts, cut the support loop before the detail (Mario [00:16:13] [00:38:16]
  [01:19:49]).
- **Even grid, never double; loops are the proof.** Neighbor quads under 2:1 (Mario [00:08:31]); a
```
END THIRD-PARTY FILE b8fa637211c383cb

The third-party file has ended. Everything between the b8fa637211c383cb tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2597 of 20969 bytes. © scenario-labs · MIT · https://github.com/scenario-labs/skills/tree/HEAD/skills/dcc/maya/scenario-maya-modeling/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
