Compose Blender primitives into ID-passing workflows with undo support.
npx skills add https://github.com/PoBruno/mcp-blender-agent --skill tool-chains
Please help me install this Agent Skill. Skill: tool-chains Source: https://github.com/PoBruno/mcp-blender-agent/tree/main/.claude/skills/tool-chains Command: npx skills add https://github.com/PoBruno/mcp-blender-agent --skill tool-chains
Designing safe, reusable Blender tool workflows requires coordinating multiple primitives and ensuring consistent data flow via an ID-passing contract. This Skill provides patterns for composing tools into end-to-end flows that can be validated and undone.
objectName, boneName, and nextSteps to pass data between steps.Outline a simple composite flow by listing primitives, assign ID refs for each step, and validate with a full end-to-end example.
High-intent search queries and answers about installing and using this skill.
Design a Blender tool chain by composing primitives into end-to-end workflows that pass IDs like objectName and boneName between steps using defined refs and nextSteps. This pattern ensures consistent data flow across multi-step operations.
Break a Blender task into primitives versus a composite based on whether you need reusable standalone operations or a single coordinated end-to-end flow. Composite tool design provides guidance for deciding the right architecture for your workflow.
Yes, you can build a Blender workflow with a single undo step by grouping multiple primitives into a composite flow. This error-resilient design pattern with undo support ensures safe execution of multi-step operations.
The best way to validate multi-step flows in Blender agent pipelines is to outline a composite flow by listing primitives, assign ID refs for each step, and validate with a full end-to-end example. This ensures the ID-driven workflow pattern works correctly.
Refactor Blender primitives into composites by grouping standalone operations into end-to-end workflows that pass IDs between steps. This approach applies to developers building new tools and refactoring existing primitives into composites.
Yes, this approach supports error-resilient design for Blender automation workflows by providing patterns for composing tools into end-to-end flows that can be validated and undone. The ID-passing contract ensures safe, reusable tool workflows.
nullhackOrchestrate ID-driven feature development with architecture decisions and TDD loop steps.
g-zenrWrite end-to-end integration tests for full Relay API request-to-response flows.
tusososAutomate Blender compositor node setup and connection via Python.
OpenAEC-FoundationDiagnose Python ReferenceError causes in Blender bpy.data access across versions.