blender-impl-addons

Guide Blender addon and extension development, packaging, and CI/CD workflows.

30|4|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/OpenAEC-Foundation/Blender-Bonsai-ifcOpenshell-Sverchok-Claude-Skill-Package --skill blender-impl-addons
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: blender-impl-addons
Source: https://github.com/OpenAEC-Foundation/Blender-Bonsai-ifcOpenshell-Sverchok-Claude-Skill-Package/tree/main/skills/blender/impl/blender-impl-addons
Command: npx skills add https://github.com/OpenAEC-Foundation/Blender-Bonsai-ifcOpenshell-Sverchok-Claude-Skill-Package --skill blender-impl-addons

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides comprehensive guidance and best practices for developing, packaging, and distributing Blender addons and extensions, ensuring compatibility and adherence to Blender's evolving extension system.

Core Features & Use Cases

  • Extension vs. Legacy Addon: Decision trees to choose the right development path based on Blender version.
  • Project Structure: Templates for both single-file and multi-file addon/extension projects.
  • Manifest & Metadata: Detailed guidance on blender_manifest.toml for extensions.
  • Packaging & Distribution: Instructions for building .zip packages and publishing to extensions.blender.org.
  • Testing & CI/CD: Strategies for headless testing and setting up automated pipelines.
  • Use Case: You need to develop a new Blender addon for a client. This Skill will guide you through setting up the project structure, writing the code according to best practices, defining the manifest, and preparing it for distribution.

Quick Start

Follow the "Extension Project Structure (Blender 4.2+)" pattern to set up a new Blender extension.

Frequently Asked Questions about blender-impl-addons

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

FAQPage Schema
How do I package a Blender addon for extensions.blender.org?

To package a Blender addon for extensions.blender.org, you must build a `.zip` archive containing your project files and a valid `blender_manifest.toml` file. This Skill provides detailed instructions for preparing and publishing extensions.

What is the difference between a Blender extension and a legacy addon?

A Blender extension is the modern distribution format for Blender 4.2+, while a legacy addon refers to older packaging methods. This Skill provides decision trees to choose the correct development path based on your target Blender version.

How do I migrate a legacy Blender addon to the new extension API?

Migrating a legacy Blender addon to the new extension API involves updating your project structure and metadata to match the `blender_manifest.toml` requirements. This Skill guides version migration from legacy addons to extensions for Blender 3.x through 5.x.

Can I manage external Python dependencies via wheels for a Blender extension?

Yes, you can manage external Python dependencies via wheels when developing a Blender extension. This Skill covers dependency management via wheels to ensure your addon includes required external libraries correctly.

What is the correct project structure for a multi-file Blender extension?

The correct project structure for a multi-file Blender extension follows specific templates that organize bpy scripts and metadata appropriately. This Skill provides structural templates for both single-file and multi-file extension projects.