菜单
Pipeline stage — production pipeline integration: project workspace setup, asset publishing, metadata tagging. Use when moving assets through a versioned pipeline. Not for primitive creation (maya-primitives), mesh editing (maya-mesh-ops), or rendering (maya-render).
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Synthetic async skill for gateway integration tests. Sleeps for N seconds and reports progress every 500 ms. No actual Maya installation required — uses MayaStandaloneDispatcher.
Set up dcc-mcp-maya for an agent or operator: install Maya Python dependencies with mayapy, generate MCP host configuration, guide the user through loading the Maya plugin, and run a first live-tool smoke prompt.
Pipeline stage — asset discovery and resolution. Search local asset libraries, resolve paths to structured AssetDescriptor records, and surface candidate assets for downstream import. Use before maya-import-to-scene to locate what to import.
Pipeline stage — structured asset import. Consume an AssetDescriptor produced by maya-asset-source and import the asset (FBX, OBJ, USD) into the current Maya scene via cmds.file(). Handles axis/unit conversion, MaterialMode, PlacementHint, and optional target collection grouping. Returns an ImportToSceneResult with the new node list.
Authoring stage - typed Bifrost procedural modeling and graph construction in Maya. Use to create graph shapes or boards, add Bifrost nodes, set input defaults, and connect ports. Not for ordinary Maya DG nodes (maya-node-graph), polygon edits (maya-mesh-ops), or arbitrary Python/MEL (maya-scripting).
Authoring stage — create, assign, query, and manage Lambert / Blinn / surface shader networks. Use for ad-hoc material assignment. For reusable presets and library workflows use maya-material-library; for final rendering use maya-render.
| name | maya-pipeline |
| description | Pipeline stage — production pipeline integration: project workspace setup, asset publishing, metadata tagging. Use when moving assets through a versioned pipeline. Not for primitive creation (maya-primitives), mesh editing (maya-mesh-ops), or rendering (maya-render). |
| license | MIT |
| allowed-tools | Bash Read |
| metadata | {"dcc-mcp":{"dcc":"maya","layer":"domain","stage":"pipeline","version":"1.1.0","tags":["maya","pipeline","asset","publish","project","metadata"],"search-hint":"asset publish, production pipeline, metadata tagging, project workspace,\nversioned publish, set project, tag asset, get asset metadata","depends":["maya-geometry"],"tools":"tools.yaml","groups":"groups.yaml"}} |
Project workspace, asset publishing, metadata tagging. Sits on top of
maya-geometry (declared in depends): publishing an asset involves
writing the geometry through Interchange tools and recording metadata
into the scene.
set_project — Set the Maya project workspace directorypublish_asset — Export selected geometry to a versioned publish path (FBX or MA)tag_asset_metadata — Store pipeline metadata (asset_name, variant, version, step) on a nodeget_asset_metadata — Retrieve pipeline metadata attributes from a node