scenario-zbrush-expert
Installation
SKILL.md
ZBrush expert (router and agent protocol)
An agent does expert ZBrush work as a loop: deterministic palette operations, synthesized strokes
and canvas renders from fixed views, gated at every stage. One long script is not the method. This
skill is the protocol every ZBrush task follows, the shared toolkit in scripts/, and
the map to the team skills. Target: ZBrush 2026.2.1 on macOS, driven through the project's Python
bridge. If a sibling skill named here is missing from your available skills, ask the user to install
it (npx skills add scenario-labs/skills --skill <name>); unattended, proceed from tool schemas and
flag the gap.
1. Execution channel
| Channel | Use for | Rules |
|---|---|---|
Bridge into a running ZBrush (scripts/zb_launch.py, over the client scripts/zb_bridge.py) |
all interactive work: palette operations, strokes, renders, measurements | zb_launch.start() spawns ZBrush with ZBRUSH_PLUGIN_PATH=scripts/zb_plugins and ZB_BRIDGE_AUTOSERVE=1. It waits for "plugin loaded", the port and a ping, then quits the ZHomePage helper. Work with zb_launch.run(code) or zb_launch.call("zb_ops", "dynamesh", 256). End with zb_launch.stop(save_to=".../x.ztl"). |
-script batch launch |
unattended jobs on saved files (export every SubTool, reports) | ZBrush.app/Contents/MacOS/ZBrush -script /abs/job.py args /abs/scene.ZPR: the scene is the LAST argument, script args start at sys.argv.index("-script") + 2, report through files and sys.exit(code) (Maxon quickstart). Whether ZBrush quits on exit [verify]. |
Rules for the bridge: