blockbench-use

name

blockbench-use

description

MANDATORY prerequisite — invoke BEFORE any mcp__blockbench__* tool call that creates, modifies, or exports Blockbench content. Orchestrates the other blockbench-* skills (modeling, texturing, animation, PBR, Hytale, MCP overview). Trigger on: 3D model/texture/animation creation or edits in Blockbench; calls to mcp__blockbench__* tools; phrases like 'build a Minecraft model', 'paint a texture', 'animate this rig', 'export the model'. Dispatches to the right sub-skill(s), enforces pre-flight checks (project open, format, outline), wraps risky work in checkpoints, and ensures exports close the loop.

Blockbench Use

Orchestrator for Blockbench MCP work. Load this before touching the 3D scene so the right sub-skills load and the right pre-flight checks run.

Rule

Any request that will call an mcp__blockbench__* tool to create or modify content must go through this skill first.

Steps, in order:

1. Classify the request → pick one or more sub-skills (table below).
2. Pre-flight → confirm a project is open and the format is correct (see "Pre-flight checks").
3. Load the sub-skill(s) via the Skill tool.
4. Checkpoint before risk → call save_checkpoint for multi-step edits that might need rollback.
5. Execute the sub-skill's workflow.
6. Close the loop → screenshot, validate (Hytale), or export if the user asked for a deliverable.

Skill routing table

Pick by primary intent. When the task spans domains, load all relevant skills before starting.

User intent	Primary skill	Also load when…
Build cubes, meshes, groups, hierarchy