Scenario Zbrush Automation
Use when automating ZBrush 2026: batch processing a folder of OBJ or ZTL files, a...
Install
npx skills add scenario-labs/skills --skill scenario-zbrush-automation -g -a claude-code -y- Repository
- scenario-labs/skills1.4k
- Category
- Engineering
- Updated
- 3d ago
- License
- MIT
- Context cost
- Mediumabout 3,000 tokens
- Runs scripts
- Yes, review before use
What it does
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.
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
session assigned; the README's startup stall is still open). Offline: 56 tests pass
(tests/code/zbrush-automation/run_offline.py), including a GoZ reader and writer matching ZBrush's
own ZResources/DXFStar.GoZ byte for byte. Live suite: tests/code/zbrush-automation/run_live.sh.
