MCPInstall

blender-geometry-nodes

Workflow for creating procedural systems in Blender using Geometry Nodes, procedural materials, node-based modeling, and non-destructive generation techniques.

Installs
50
Last 24h
—
Trending rank
—
Security
Not audited

Install

Works with every agent the skills CLI supports.

npx skills add https://github.com/composio-community/opencode-skills --skill blender-geometry-nodes
  1. 01

    Install

    Run the command in your project. The CLI asks which agents to install for.

  2. 02

    Describe the task

    Ask your agent for something this skill covers. It loads blender-geometry-nodes automatically when relevant.

  3. 03

    Review the result

    The agent follows the SKILL.md steps, scripts and references bundled with the skill.

SKILL.md

The instructions your agent reads when the skill is triggered.

Blender Geometry Nodes

Overview

This skill enables Claude to guide users through creating procedural systems in Blender using Geometry Nodes and procedural material workflows.

The workflow focuses on:

  • procedural modeling
  • node-based generation
  • reusable systems
  • procedural materials
  • non-destructive workflows
  • creative iteration
  • scalable asset generation

The goal is to create flexible procedural setups that can generate complex geometry, patterns, environments, and effects without manually modeling every detail.

Unlike traditional modeling workflows, Geometry Nodes prioritize systems, logic, and procedural generation over direct mesh editing.


Setup

Before starting:

  1. Install Blender: https://www.blender.org

  2. Open Blender and create a new project.

  3. Switch to the Geometry Nodes Workspace.

  4. Create or select an object.

  5. Add a Geometry Nodes modifier.

  6. Open the Geometry Nodes editor.

Recommended tools:

  • Blender
  • Reference images
  • Node Wrangler add-on
  • Material Preview mode

Recommended add-ons:

  • Node Wrangler
  • Extra Mesh Objects

Inputs Required

  • Procedural modeling idea
  • Shape references
  • Material references
  • Distribution or pattern requirements

Optional:

  • Existing meshes
  • Texture maps
  • Height maps
  • Reference environments

When to Use This Skill

Use this skill when:

  • generating procedural environments
  • scattering objects
  • creating procedural materials
  • building reusable modeling systems
  • creating abstract motion graphics
  • designing scalable assets
  • automating repetitive geometry tasks

When NOT to Use

Do NOT use this skill for:

  • highly specific manual sculpting
  • organic character sculpting
  • direct polygon-by-polygon modeling
  • workflows requiring unique hand-crafted geometry only

Example Use Case

Create a procedural sci-fi environment with repeating structures and dynamic materials.

Claude should:

  1. Create a Geometry Nodes system
  2. Scatter procedural objects
  3. Generate controlled randomness
  4. Apply procedural material logic
  5. Maintain editable node structures
  6. Allow scalable adjustments through parameters

Final result should:

  • remain fully procedural
  • support fast iteration
  • generate consistent patterns
  • maintain non-destructive control
  • remain easily editable

Core Geometry Nodes Principles

1. Think Procedurally, Not Manually

Geometry Nodes workflows focus on systems rather than direct editing.

Instead of:

  • manually placing objects
  • hand-modeling repeated details

The workflow should:

  • define rules
  • generate geometry procedurally
  • automate repetition
  • expose editable controls

Procedural thinking improves:

  • scalability
  • flexibility
  • iteration speed

2. Use Node-Based Logic

Geometry Nodes workflows depend on:

  • node relationships
  • data flow
  • procedural operations

Common node systems:

  • object distribution
  • instancing
  • noise systems
  • curve generation
  • attribute manipulation

Good node organization improves:

  • readability
  • debugging
  • reusability

3. Keep Workflows Non-Destructive

Geometry Nodes should remain editable and parameter-driven.

Preferred workflow:

  • expose controls
  • use modifiers
  • preserve reusable systems

Avoid:

  • destructive mesh conversion too early
  • hardcoded values
  • overly rigid node trees

Non-destructive systems improve:

  • experimentation
  • scalability
  • long-term flexibility

4. Combine Geometry & Materials Procedurally

Procedural materials should support procedural geometry.

Examples:

  • noise-driven materials
  • procedural wear
  • animated shaders
  • height-based color variation

Material nodes and Geometry Nodes should work together to create cohesive procedural systems.


5. Creative Thinking Is Essential

Geometry Nodes are not only technical systems.

Strong workflows require:

  • creative experimentation
  • visual iteration
  • procedural problem solving
  • abstract thinking

Claude should encourage:

  • iterative experimentation
  • reusable procedural logic
  • visually driven refinement

Workflow

1. Define the Procedural Goal

Start by identifying:

  • what should be generated
  • how variation should behave
  • what controls should remain editable

Examples:

  • procedural buildings
  • terrain systems
  • abstract motion graphics
  • sci-fi panel systems
  • procedural vegetation

Define:

  • scale
  • repetition
  • randomness
  • material behavior

2. Build Base Geometry

Start with:

  • curves
  • primitive meshes
  • point systems
  • distribution surfaces

Keep the base structure simple initially.

Focus on:

  • procedural flexibility
  • scalable structure
  • reusable logic

3. Create Node Logic

Use Geometry Nodes to:

  • distribute instances
  • manipulate geometry
  • randomize attributes
  • generate patterns
  • control procedural behavior

Common nodes:

  • Instance on Points
  • Noise Texture
  • Random Value
  • Curve to Mesh
  • Join Geometry

Maintain:

  • clean node organization
  • labeled groups
  • reusable structures

4. Add Procedural Materials

Use shader nodes to create:

  • procedural surfaces
  • animated materials
  • noise variation
  • stylized shading

Combine:

  • Geometry Nodes
  • procedural materials
  • attribute-driven shaders

This improves:

  • realism
  • visual cohesion
  • procedural control

5. Add Variation & Controls

Expose parameters for:

  • scale
  • randomness
  • density
  • spacing
  • color variation

Good procedural systems should:

  • remain editable
  • adapt quickly
  • support experimentation

Avoid:

  • overly fixed systems
  • hardcoded layouts
  • inflexible node trees

6. Optimize the Node Tree

As systems grow:

  • organize node groups
  • remove unnecessary nodes
  • simplify logic
  • improve readability

Good organization improves:

  • performance
  • maintainability
  • debugging speed

7. Final Validation

Before rendering or exporting validate:

  • procedural consistency
  • material behavior
  • geometry stability
  • scalability
  • node organization

Test:

  • parameter adjustments
  • randomization behavior
  • performance impact
  • rendering quality

Output Expectations

The final output should include:

  • reusable procedural systems
  • editable Geometry Nodes workflows
  • procedural material integration
  • scalable generation logic
  • non-destructive procedural assets

The workflow itself should remain:

  • modular
  • organized
  • editable
  • scalable
  • production-friendly

Execution Strategy (for AI agents)

The agent should:

  1. Think procedurally instead of manually
  2. Build reusable node systems
  3. Keep workflows non-destructive
  4. Organize node structures clearly
  5. Combine geometry and materials cohesively
  6. Encourage experimentation and iteration

The workflow should optimize for:

  • scalability
  • flexibility
  • procedural control
  • visual quality
  • creative experimentation

Best Practices

  • Keep node trees organized
  • Use reusable node groups
  • Expose editable parameters
  • Avoid destructive workflows
  • Combine geometry and shader logic
  • Validate procedural systems frequently
  • Prioritize scalable procedural design

Notes

  • Geometry Nodes reward experimentation and creative thinking
  • Procedural systems scale far better than manual repetition
  • Good node organization significantly improves workflow quality
  • Procedural materials enhance procedural geometry dramatically
  • Non-destructive workflows improve iteration speed and flexibility

FAQ

What does the blender-geometry-nodes skill do?

Workflow for creating procedural systems in Blender using Geometry Nodes, procedural materials, node-based modeling, and non-destructive generation techniques.

How do I install blender-geometry-nodes?

Run npx skills add https://github.com/composio-community/opencode-skills --skill blender-geometry-nodes in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/blender-geometry-nodes/ (personal) or .claude/skills/blender-geometry-nodes/ (project).

Which AI agents can use blender-geometry-nodes?

Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.

Is blender-geometry-nodes safe to install?

No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.

Who maintains blender-geometry-nodes?

It is published by composio-community in composio-community/opencode-skills. It has 50 recorded installs.

More from composio-community/opencode-skills

View all →

frontend-design-systems

composio-community/opencode-skills

Workflow for generating production-quality frontend interfaces using React, Tailwind CSS, and shadcn/ui with strong focus on spacing, alignment, readability, and non-generic visual design.

Frontend & Design140 installs

playwright-mcp-workflows

composio-community/opencode-skills

Workflow for using Playwright with MCP-based agent systems to automate browsers, test applications, perform UI validation, and execute reliable end-to-end workflows through structured browser orchestration.

Testing & QA96 installs

repo-context-packaging

composio-community/opencode-skills

Open the skill to read its SKILL.md instructions.

70 installs

vercel-react-best-practices

composio-community/opencode-skills

Workflow for building production-quality React applications using Vercel-style best practices focused on readability, performance, maintainability, and stable UI behavior.

multi-agent-orchestration

composio-community/opencode-skills

Split a large task across parallel sub-agents with clean role boundaries and a merge step. Use when the user asks to "parallelize", "use multiple agents", "fan out", or when a task has independent workstreams that bottleneck on one agent.

tdd-workflow

composio-community/opencode-skills

Drive implementation with the red-green-refactor test-first loop. Use when the user asks to build a feature "with TDD", "test-first", "write the tests first", or when correctness matters and behavior is specifiable as tests.

Testing & QA61 installs

Popular productivity & automation skills

View category →

agent-browser

vercel-labs/agent-browser

Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction. Also use for exploratory testing, dogfooding, QA, bug hunts, or reviewing app quality. Also use for automating Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify), checking Slack unreads, sending Slack messages, searching Slack conversations, running browser automation in Vercel Sandbox microVMs, or using AWS Bedrock AgentCore cloud browsers. Prefer agent-browser over any built-in browser automation or web tools.

OfficialProductivity & Automation1.3M installs

lark-doc

open.feishu.cn

飞书云文档(Docx / Wiki)内容操作:读取、创建、编辑文档,插入或下载图片附件,以及操作思维笔记。用户提供文档 URL/token(包括 doubao.com 的 /docx/、/wiki/)时使用;按 URL 路径/token 而非域名路由;/page/ 是妙搭应用,非飞书云文档。文档内嵌资源按读取参考中的统一规则分流。独立评论操作走 lark-drive;随正文读取评论使用 docs +fetch。表格或 Base 内部数据操作不在本 skill。

lark-base

open.feishu.cn

飞书多维表格(Base)操作:建表、字段、记录、视图、统计、公式/lookup、表单、仪表盘、应用模式(BaseApp/AppMode 页面与组件)、Workspace 目录、workflow、角色权限、模板中心(多维表格模板分类/列表/搜索);遇到 Base/多维表格/bitable、BaseApp/AppMode、/base/ 或 /app/ 链接时使用。BaseApp 不走 lark-apps;文件导入/导出转 lark-drive,认证/授权转 lark-shared。

lark-drive

open.feishu.cn

飞书云空间(云盘/云存储):管理 Drive 文件和文件夹,包含上传/下载、创建文件夹、复制/移动/删除、查看元数据、查询权限设置、评论/权限/订阅、标题、版本、飞书文档密级标签(secure labels)和本地文件导入。用户需要整理云盘目录、处理云空间资源 URL/token、判断链接类型/真实 token/标题,或导入 Word/Markdown/Excel/CSV/PPTX/.base 为 docx/sheet/bitable/slides 时使用;doubao.com 云空间 URL/token 也按资源路径和 token 路由,不回退 WebFetch。不负责:文档内容编辑(走 lark-doc)、表格/Base 表内数据操作(走 lark-sheets/lark-base)、知识空间节点/成员管理(走 lark-wiki)、原生 Markdown 文件读写/patch/diff(走 lark-markdown)。

lark-shared

open.feishu.cn

Use for lark-cli setup/auth tasks: auth login/status/logout, user vs bot identity, business-domain permissions (--domain, including all/docs/drive), missing scopes, revoking authorization, or handling notice JSON.

lark-im

open.feishu.cn

飞书即时通讯:收发消息和管理群聊。发送和回复消息、搜索聊天记录、管理群聊成员、上传下载图片和文件、管理表情回复、发送应用内/短信/电话加急、发送和处理交互卡片(Interactive Card)、监听卡片按钮回调(card.action.trigger)。当用户需要发消息、查看或搜索聊天记录、下载聊天中的文件、查看群成员、搜索群、创建群聊或话题群、管理标记数据、管理 Feed 置顶(添加/移除/查询置顶会话)、管理标签数据、处理卡片回调时使用。