Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

zbrush-scripting

Estrelas5

Forks1

Atualizado16 de julho de 2026 às 21:00

Thin-harness skill — controlled Python execution and session diagnostics inside ZBrush 2026.1+. Use when no typed ZBrush skill covers the task or you need version/subtool counts. Not for routine scene edits — prefer zbrush-scene or domain skills first.

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Executar no Manus

Fonte

dcc-mcp

dcc-mcp/dcc-mcp-zbrush

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Arquitetos (exceto paisagismo e naval)Arquitetura e Engenharia·SOC 17-1011

Explorador de arquivos

4 arquivos

SKILL.md

readonly

name	zbrush-scripting
description	Thin-harness skill — controlled Python execution and session diagnostics inside ZBrush 2026.1+. Use when no typed ZBrush skill covers the task or you need version/subtool counts. Not for routine scene edits — prefer zbrush-scene or domain skills first.
license	MIT
compatibility	dcc-mcp-zbrush 0.2+, ZBrush 2026.1+, dcc-mcp-core 0.19.45+
allowed-tools	Bash Read Write Edit
metadata	{"dcc-mcp":{"dcc":"zbrush","layer":"thin-harness","stage":"bootstrap","version":"1.0.0","tags":["zbrush","scripting","python","automation","bootstrap"],"search-hint":"execute python, run script, zbrush.commands, session info, version","tools":"tools.yaml"}}

zbrush-scripting

Bootstrap escape hatch. Call typed tools from zbrush-scene, zbrush-subtool, or zbrush-interchange before execute_python.

When to use

Verify MCP connectivity → get_session_info
One-off SDK experiment with no typed tool yet → execute_python

Safety

All tools use affinity: main because ZBrush APIs are host-bound.
execute_python is destructive and non-idempotent by default.

Mais deste repositório

mesmo repositório

zbrush-import-to-scene

dcc-mcp/dcc-mcp-zbrush

Pipeline skill — import OBJ or FBX asset files into ZBrush as subtools. Consumes the dcc-mcp-core asset_import contract (AssetDescriptor) and returns an ImportToSceneResult with the imported subtool names. Use when you need to bring geometry from disk into the active ZBrush scene.

2026-07-165

zbrush-interchange

dcc-mcp/dcc-mcp-zbrush

Domain skill — export meshes from ZBrush to interchange formats. Use when you need OBJ export from the active subtool. Not for in-scene sculpt edits — use zbrush-subtool first to pick the correct subtool.

2026-07-165

zbrush-scene

dcc-mcp/dcc-mcp-zbrush

Domain skill — read-only scene and tool introspection for ZBrush. Use when you need active tool path, subtool inventory, or selection index. Not for sculpting, export, or subtool mutation — use zbrush-subtool or zbrush-interchange.

2026-07-165

zbrush-subtool

dcc-mcp/dcc-mcp-zbrush

Domain skill — select, inspect, and apply bounded refinement to subtools on the active ZBrush tool. Use when you need to switch the active subtool, read visibility/lock flags, subdivide, polish, or inflate. Not for mesh export or arbitrary Python — use zbrush-interchange or zbrush-scripting.

2026-07-165

name	zbrush-scripting
description	Thin-harness skill — controlled Python execution and session diagnostics inside ZBrush 2026.1+. Use when no typed ZBrush skill covers the task or you need version/subtool counts. Not for routine scene edits — prefer zbrush-scene or domain skills first.
license	MIT
compatibility	dcc-mcp-zbrush 0.2+, ZBrush 2026.1+, dcc-mcp-core 0.19.45+
allowed-tools	Bash Read Write Edit
metadata	{"dcc-mcp":{"dcc":"zbrush","layer":"thin-harness","stage":"bootstrap","version":"1.0.0","tags":["zbrush","scripting","python","automation","bootstrap"],"search-hint":"execute python, run script, zbrush.commands, session info, version","tools":"tools.yaml"}}

zbrush-scripting

Bootstrap escape hatch. Call typed tools from zbrush-scene, zbrush-subtool, or zbrush-interchange before execute_python.

When to use

Verify MCP connectivity → get_session_info
One-off SDK experiment with no typed tool yet → execute_python

Safety

All tools use affinity: main because ZBrush APIs are host-bound.
execute_python is destructive and non-idempotent by default.