Individual skill
scenario-zbrush-automation
Use when automating ZBrush 2026: batch processing a folder of OBJ or ZTL files, a ZBrush Python script or ZScript, recording a macro to learn a palette path, the ZBrush -script command line, scripting UV Master, Decimation Master or Multi Map Exporter, exporting every SubTool, GoZ or GoB round trips with Maya or Blender, renaming SubTools, or batch reports. Also when a plugin press never returns, a dialog stalls a batch, one file kills the whole run, or GoZ updates the wrong SubTool.
skills/dcc/zbrush/scenario-zbrush-automation/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,658
- Repository last updated
- Nov 9, 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
- engineering 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 · 19,030 bytesSKILL.mdcore · 19,030 bytesSKILL.mdcore · 19,030 bytesreferences/critique.mddoc · 8,812 bytesreferences/expert-notes.mddoc · 23,496 bytesreferences/gui-paths.mddoc · 12,569 bytesreferences/procedures.mddoc · 24,325 bytesreferences/sources.mddoc · 10,916 bytesscripts/zb_batch.pyruns · 53,865 bytesscripts/zb_batch_job.pyruns · 6,002 bytesscripts/zb_goz.pyruns · 18,844 bytesscripts/zb_plugin_ops.pyruns · 30,311 bytes
Read excerpt
# ZBrush automation (tools and pipeline TD)
An expert ZBrush TD automates with contracts and proof: every file is its own tool, every step is a
separate call with a time limit, every output is read back from disk, and a hung plugin costs one
file, never the batch. ZBrush has no timeout, no undo control from Python and dialogs that code
cannot answer, so the safety lives on the agent side: the runner, the checkpoints, the report. 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-zbrush-expert (bridge, zb_launch, zb_ops, zb_audit, review loop,
2026 traps).
**Status (2026-09-24, refactor pass 2):** every ZBrush call here is **not yet run in ZBrush** (no