One-click install
npx skills add https://github.com/Impertio-Studio/Blender-Bonsai-ifcOpenshell-Sverchok-Claude-Skill-Package --skill blender-impl-nodes-impertio-studio
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: blender-impl-nodes
Source: https://github.com/Impertio-Studio/Blender-Bonsai-ifcOpenshell-Sverchok-Claude-Skill-Package/tree/main/skills/blender/impl/blender-impl-nodes
Command: npx skills add https://github.com/Impertio-Studio/Blender-Bonsai-ifcOpenshell-Sverchok-Claude-Skill-Package --skill blender-impl-nodes-impertio-studio

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill prevents fragile, editor-context-dependent Geometry/SShader/Compositor node scripts and the most common production-breaking mistakes (especially missing node group interface sockets and unreadable/invalid node graphs).

Core Features & Use Cases

  • Node tree construction workflow for Geometry Nodes, Shader Nodes, and Compositor pipelines built programmatically.
  • Interface-first, version-aware socket creation (notably Blender 4.0+ with node_tree.interface and modifier inputs).
  • Reliable scripting patterns that avoid bpy.ops.node.*, enforce explicit location for readability, and set modifier inputs by interface identifiers rather than socket names.
  • AEC-focused node group authoring: parametric components, reusable node groups, nested groups, and batch AEC material workflows.
  • Common error prevention via documented anti-patterns (wrong link order, missing NodeGroupInput/Output, duplicate groups, etc.).

Quick Start

Use blender-impl-nodes to generate a Geometry Nodes node group for an AEC wall, then assign it to a selected object and set the modifier inputs safely by interface identifiers.

Frequently Asked Questions about blender-impl-nodes

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I script Blender Geometry Nodes without using bpy.ops?▼

To script Blender Geometry Nodes reliably, use deterministic API calls like `tree.nodes.new()` and `tree.links.new()` instead of `bpy.ops.node.*`, which depends on editor context and breaks production pipelines.

How do I set modifier inputs for Geometry Nodes in Blender 4.0+?▼

Set modifier inputs in Blender 4.0+ by using interface identifiers via `interface.items_tree` rather than socket names, ensuring version-aware socket creation and stable parametric AEC workflows.

Why does my programmatically generated node tree fail or show missing sockets?▼

Programmatic node trees fail due to missing node group interface sockets, wrong link order, or duplicate groups; designing interface-first and enforcing explicit node positioning prevents these invalid node graphs.

Can I build nested node groups for AEC workflows across Blender 3.x and 4.x?▼

Yes, you can build nested node groups for AEC workflows with version-aware handling across Blender 3.x, 4.x, and 5.x, allowing reusable parametric components and batch material assignments.

What is the best way to create readable Compositor or Shader node trees via bpy scripting?▼

The best way to create readable Compositor or Shader node trees via bpy scripting is to enforce explicit `location` values for each node and design interface-first node groups to avoid anti-patterns.