Individual skill
scenario-maya-pipeline-scripting
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.
skills/dcc/maya/scenario-maya-pipeline-scripting/SKILL.md
Source commit f29bf06ab89088695ed3431ac99d20a090441a2f
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 9, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 3,670
- Repository last updated
- Nov 10, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent-skills Repository topic
- blender Repository topic
- claude-code Repository topic
- claude-skills Repository topic
- codex Repository topic
- game-assets Repository topic
- game-development Repository topic
- generative-ai Repository topic
- image-generation Repository topic
- mcp Repository topic
- writing Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 18,822 bytesSKILL.mdcore · 18,822 bytesSKILL.mdcore · 18,822 bytesSKILL.mdcore · 18,822 bytesreferences/critique.mddoc · 31,079 bytesreferences/expert-notes.mddoc · 31,040 bytesreferences/gui-paths.mddoc · 22,859 bytesreferences/procedures.mddoc · 46,197 bytesreferences/sources.mddoc · 16,395 bytesscripts/mx_pipeline.pyruns · 118,323 bytes
Read excerpt
# 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