Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

zbrush-scripting

Sterne5

Forks1

Aktualisiert16. Juli 2026 um 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.

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

In Manus ausführen

Quelle

dcc-mcp

dcc-mcp/dcc-mcp-zbrush

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

In Manus ausführen

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

Architekten (außer Landschafts- und Schiffbauarchitekten)Architektur- und Ingenieurberufe·SOC 17-1011

Datei-Explorer

4 Dateien

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.

Mehr aus diesem Repository

gleiches Repository

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.