# Scenario Maya Pipeline Scripting

Use when writing or fixing Maya pipeline code in Python: mayapy batch jobs over many...

- Repository: https://github.com/scenario-labs/skills (1448 stars)
- Category: Design
- License: MIT
- Last updated: 2026-11-01
- Runs scripts: yes, review before use

## Install

Claude Code: `npx skills add scenario-labs/skills --skill scenario-maya-pipeline-scripting -g -a claude-code -y`
Codex: `npx skills add scenario-labs/skills --skill scenario-maya-pipeline-scripting -g -a codex -y`
Cursor: `npx skills add scenario-labs/skills --skill scenario-maya-pipeline-scripting -g -a cursor -y`
Gemini CLI: `npx skills add scenario-labs/skills --skill scenario-maya-pipeline-scripting -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add scenario-labs/skills`

## Description

Use when writing or fixing Maya pipeline code in Python: mayapy batch jobs over many scenes, validating and auto-fixing scenes, FBX export for Unreal or Unity (static, skeletal, animation clips, Game Exporter), Alembic or GPU caches, USD export, stages and layers, references and namespaces, PySide6 tool windows, OpenMaya 2.0 plug-ins, or slow playback. Also when an FBX lands with wrong scale, normals, tangents or extra takes, a USD export has one frame or smoothed meshes, or one bad file kills a batch.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Maya pipeline scripting (pipeline TD)

Expert pipeline work is contracts plus proof: every file that leaves Maya goes through generated
names, explicit export settings and a re-import check, and no batch trusts one Maya process with two
hundred files. The pipeline TD never types what can be generated, never trusts a default, and
verifies by reading the output back. 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).

**Status (2026-09-24):** every Maya call here is **not yet run in Maya** (not installed).
[`scripts/mx_pipeline.py`](scripts/mx_pipeline.py) ran offline, its Maya layer against fakes. First
action once Maya is installed: `tests/code/maya-pipeline-scripting/run_all.sh`.

## Stance (the expert delta)

The rest: https://github.com/scenario-labs/skills/blob/HEAD/skills/dcc/maya/scenario-maya-pipeline-scripting/SKILL.md