SkillAgentSearch skills...

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…

Install / Use

npx skills add scenario-labs/skills --skill scenario-maya-pipeline-scripting

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

86/100

Category

Automation

Supported Platforms

Universal

Our assessment of scenario-maya-pipeline-scripting

scenario-maya-pipeline-scripting scores 86/100 on our quality scale, 1790th of 2,758 Automation skills we index.

Its SKILL.md is 18 KB long, well organised into 10 sections and no code examples: a thorough specification that gives an agent plenty to work with.

With 1,048 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
30/30
Structure
13/20
Description
15/15
Adoption
13/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated 35 days ago, so scenario-maya-pipeline-scripting is actively maintained.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands.

Automated pattern scan on 2026-11-20. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

scenario-maya-pipeline-scripting compared with similar skills

All 4 of these similar skills score higher than scenario-maya-pipeline-scripting; compare them before choosing.

SkillScoreStarsUpdatedFormat
scenario-maya-pipeline-scripting (this skill)by scenario-labs861.0k35d agoSKILL.md
Agent-Reachby Panniantong100114.0ktodayCLAUDE.md
rufloby ruvnet10082.3ktodayCLAUDE.md
headroomby headroomlabs-ai10080.5ktodayCLAUDE.md
Claude-Code-Game-Studiosby Donchitos10040.6k12d agoCLAUDE.md

Frequently asked questions

How do I install scenario-maya-pipeline-scripting?
Run npx skills add scenario-labs/skills --skill scenario-maya-pipeline-scripting. The install tabs above show the steps for each supported agent.
Which AI agents does scenario-maya-pipeline-scripting work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is scenario-maya-pipeline-scripting safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is scenario-maya-pipeline-scripting still maintained?
The repository was last updated 35 days ago, so scenario-maya-pipeline-scripting is actively maintained.

name: scenario-maya-pipeline-scripting 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." license: MIT

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 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)

  • Never type what can be generated (Guignolle, Borderlands, lfWkJrkhd2U [00:04:58]): names, namespaces, paths and clip ranges come from a manifest; validation sits at the point of action (approved-shot warning, scene breakdown, publish diff green, blue, red [00:22:11] to [00:24:57]).
  • Prove it by reading the output back (dcc-mcp's numbers-over-claims standard; the Maya Help's test: the FBX reimports with identical normals, scale, axis and length): re-import in a clean scene and compare meshes, triangles, joints, per-mesh bounds, normal directions, units and up axis; read takes with FBXRead; reopen USD with pxr; hash sources. One mayapy per file: FBX settings and optionVars survive file(new=True).
  • Never run blind (chadrik, maya-mcp-server: without stdout and stderr "the agent is blind"; FBX doc: in batch the log is the only feedback on problem files): keep FBXExportGenerateLog on and read each child's log; children run with MAYA_DISABLE_ADP=1 and Maya's stderr at warning (maya_log="all" to debug); read stdout, stderr and maya_messages after every bridge call.
  • FBX is global state (Maya 2027 Help, FBX MEL commands): push, reset, set every option, clear the take accumulator, query back and log next to the file, pop. Bake Start and End are never stored in presets. Tangents only export on all-triangle meshes; non-orthogonal matrices are dropped. Triangulate in Maya with controlled edges (Epic).
  • Export defaults are traps (maya-usd readme): frameRange [1, 1], defaultMeshScheme catmullClark (no normals), skeletons off, namespaces kept. Pass every flag, then reopen with pxr.
  • At scale, structure beats hardware (Markowski and Hübschmann, RISE, 8UIW-g1_heg): value clips instead of full-range caches [00:37:03]; mute your own layer and every stronger one [00:26:19]; pin versions, record them in assetInfo [00:23:01].
  • Reference edits replay by name and DAG path (Maya 2027 Help): never rename or restructure a published child file; check reference health (unloaded, missing, failed edits) before any fix, and after every version swap. Shots reference assets; engines get baked exports.
  • Profile before optimizing, correct before fast (Roselle, rhtERzmAoUM [00:04:14]; Using Parallel Maya 2027): DG, Serial and Parallel must agree first; headless numbers measure evaluation, not drawing. Python builds and exports; native nodes evaluate (Fragapane, _0mb4wIZi80 [00:55:10]).

Establish first

| Input | Changes | Default when the brief is silent | | ---------------- | ---------------------------------------- | ---------------------------------------------------------------------------------------------------- | | Target | preset, checks, file layout | Unreal 5, FBX 2020.2, one file per asset, one clip per file | | Asset kind | static, skeletal, anim, cache, USD layer | skeletal for rigged scenes, static otherwise | | Scene contract | units, up axis, naming regex | cm, Y-up, mx_validate defaults, _geo suffix (FlippedNormals) if the studio has none | | Frame rate | E27, clip lengths | the engine or project rate from the brief; else reported, never resampled | | Allowed fixes | what may change unasked | history, smooth_preview, unknown_dead, namespaces; nothing that moves weights, topology or normals | | Influence limit | cap or report | Unity 4 (Unity manual); Unreal: report the histogram | | Source of truth | names, versions, ranges | a JSON manifest next to the output | | Scale of the run | workers, isolation | 5-file trial, then workers=1 or 2, process isolation |

Workflow

  1. Preflight, inventory, fixtures. P.preflight(out, scenes): mayapy, localhost and host name resolution (macOS batch renders hang on it), disk, readable scenes. P.find_scenes(root). One tiny scene per rule, each breaking one thing (test_engine_checks.py); the full chain on 5 real files. GATE: preflight ok; every fixture caught; time per file known.
  2. Batch. P.batch(scenes, job, out, plugins=("fbx",), timeout=900): one mx_run child per scene, script nodes off, MX_PIPELINE_OUT/STEM/SOURCE and a per-child FBX log name in the env. Jobs return status, issues, fixes, exports (procedures.md P1). isolation="session" only for many small trusted files; crashed ones re-run isolated. GATE: one report per scene, summary["sources_untouched"] True, every non-pass record explained.
  3. Validate, read-only. Reference health first: P.reference_issues(P.references_report()) (R01 unloaded, R02 missing, R03 failed edits, R04 foster parents). Then mx_validate.validate(profile, roots) and P.check_engine_export(roots, engine, kind, rules={"fps": 30}) (E01 to E27: units, one root, names, namespaces, matrices, triangulation, UV and color sets, locked normals, influences, collision, pivot, joints, empty meshes, time unit). GATE: issue list per file; nothing changed yet.
  4. Safe fixes, then save a version. Only the allowed fixes; n-gons, non-manifold, facing, symmetry, units and joint orientation are reported, never fixed (FlippedNormals, ToWRH4IXF7A [00:11:50]). unlock_normals and influence caps are opt-in; caps refuse a weight move above 0.1 [added]. P.save_version() writes <out>/fixed/<stem>_fixed.ma. GATE: fix log per node; re-validation has no new failure.
  5. Export. P.fbx_export(path, roots, "unreal_skeletal") (presets unreal_/unity_ + static, skeletal, anim; P.fbx_commands(preset) shows the MEL). Animation: bake range explicit, one clip per file for Unreal, joints only. Caches: P.abc_export (-uvWrite -writeFaceSets, from the composed shot). USD: P.usd_export(path, roots, frame_range=...). GATE: <file>.settings.json shows every option queried back; the FBX log was found and read (rep["fbx_log"], X05).
  6. Verify in a clean scene. P.fbx_takes(path) (no import), P.reimport_stats(path), P.compare_stats(before, after); P.abc_verify; P.usd_verify. GATE: meshes, triangles, UV sets, joint names, per-mesh bounding boxes, normal directions (at most 2% moved), units and up axis match; takes = clips + Take001; USD default prim, time range, scheme none with normals, SkelRoot, metersPerUnit 0.01.
  7. Report and diff. summary.json/summary.csv, P.export_manifest(summary), P.publish_diff(previous, current). Look at a sample (sheets of fixed files, the engine import). GATE: the report lists what was not verified.

The builtin job does stages 3 to 6 per file: P.batch(scenes, P.BUILTIN_EXPORT, out, plugins=("fbx",), job_args=["--preset", "unreal_skeletal", "--profile", "rig", "--fps", "30"]) (procedures.md P2).

Other jobs, same discipline (procedures.md): USD shot layers, one edit target, own and stronger layers muted (P9); references from the manifest, a clashing namespace raises (P10); OM2 reads through mx_audit.mfn_mesh, plug-ins and PySide6 panels (P12, P13); P.perf_census then P.eval_timing (P14); GUI parts through mx_bridge after checking modified (P15).

Numbers

| Value | Relative to | Source | | --------------------------------------------------------------------------------- | --------------------------------------------------------- | --------------------- | | FBX 2020.2 (FBX202000 [verify token]) | Unreal import | Epic | | cm, scale factor 1.0; 1 Unreal unit = 1 cm | Maya working units | Maya 2027 Help, scale | | 4 influences per vertex | Unity default | Unity manual | | at least 15 bones, T-pose | Unity humanoid | Unity manual | | UCX_/UBX_/USP_/UCP_ + mesh name + _00 | Unreal custom collision | Epic | | SOCKET_<mesh>_##, one mesh per file | Unreal sockets | Epic | | Take001 always exists | FBX take count | Maya 2027 Help | | frameRange default [1, 1] | mayaUSDExport | maya-usd readme | | 2 GB per layer lost | USD saved into the Maya file | USD for Maya 2027 | | stdout none, stderr all (defaults); mx_run: stderr warning | MAYA_BATCH_*_LOGGING_LEVEL | devkit 2022; [added] | | 0.1 max weight change; 1e-3 of the bbox diagonal; 2% of normals (8 bins per axis) | auto influence cap; round-trip bounds; round-trip normals | [added] |

Quality gates

In code: preflight ok; batch totals account for every file, sources untouched, no crash stopped the batch; reference health clean before fixes; validation before fixes and a fix log after; engine check errors zero (E27 against the target rate); settings sidecar and FBX log per export; round trip ok per export, normals and axis included; fbx_takes count as intended; usd_verify ok; breakdown empty; eval_timing(...)["consistent"] before any speed cla

Truncated for display — read the full file on GitHub.

Related Skills

View on GitHub
GitHub Stars1.0k
CategoryAutomation
Updated1mo ago
Forks129

Languages

Python

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions
scenario-maya-pipeline-scripting — Universal Skill: Install & Safety Check | SkillAgent