skills.rest
Impertio-Studio
Impertio-StudioOFFICIAL
Explore all skills by this author →
WebsiteGitHub

blender-impl-addons

Structure, validate, and package Blender addons with blender_manifest.toml.

30|4|Updated Mar 5, 2026
Search Tags:#ci testing#extension packaging#extensions.blender.org#blender addon#blender_manifest.toml#headless validation#bundled wheels
One-click install
npx skills add https://github.com/Impertio-Studio/Blender-Bonsai-ifcOpenshell-Sverchok-Claude-Skill-Package --skill blender-impl-addons-impertio-studio
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: blender-impl-addons
Source: https://github.com/Impertio-Studio/Blender-Bonsai-ifcOpenshell-Sverchok-Claude-Skill-Package/tree/main/skills/blender/impl/blender-impl-addons
Command: npx skills add https://github.com/Impertio-Studio/Blender-Bonsai-ifcOpenshell-Sverchok-Claude-Skill-Package --skill blender-impl-addons-impertio-studio

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill prevents common Blender addon/extension failures by providing a production-ready checklist for correct project structure, manifest usage, dependency handling, testing, and publishing workflows.

Core Features & Use Cases

  • Extension vs. Legacy Decisioning: Choose Blender 4.2+ extension packaging (with blender_manifest.toml) or legacy bl_info based on the target Blender version.
  • Manifest-First Metadata Guidance: Avoid validation errors by following required/optional manifest fields and correct SPDX licensing format.
  • Safe, CI-Friendly Development Practices: Establish deterministic class registration/unregistration patterns, headless test execution, and dependency bundling via wheels rather than sys.path or runtime pip installs.
  • Distribution Workflows: Package with Blender’s extension build/validate/install-file commands and align with extensions.blender.org expectations.

Quick Start

Ask Claude to generate a complete Blender 4.2+ addon/extension skeleton (folders, blender_manifest.toml, init.py registration/unregistration, headless CI test script, and build commands) for your target id, version, and operator/panel names.

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 4.2 extension using blender_manifest.toml?▼

Package Blender 4.2 extensions by defining metadata in blender_manifest.toml, then execute Blender's extension build, validate, and install-file commands to ensure correct structure for extensions.blender.org distribution.

What is the difference between a Blender addon and a Blender 4.2 extension?▼

Blender 4.2+ extensions use blender_manifest.toml for standardized metadata and distribution via extensions.blender.org, whereas legacy addons rely on the older bl_info dictionary structure.

How do I bundle Python dependencies in a Blender addon without runtime pip installs?▼

Bundle Blender addon dependencies using wheels instead of runtime pip installs or sys.path modifications, ensuring deterministic and safe extension builds across Blender 3.x through 5.x environments.

How do I run headless CI testing for Blender addons and extensions?▼

Execute headless CI testing for Blender addons by running deterministic test scripts that validate class registration/unregistration ordering and manifest compliance without launching the Blender GUI.

Why does my Blender extension fail manifest validation on extensions.blender.org?▼

Manifest validation fails when required fields are missing or SPDX licensing formats are incorrect in blender_manifest.toml; following manifest-first metadata guidance ensures compliance and prevents extension validation errors.

Can I use the same addon structure for Blender 3.x and Blender 5.x?▼

Extension packaging with blender_manifest.toml targets Blender 4.2+ through 5.x, while legacy bl_info addons are required for Blender 3.x compatibility, dictating different project structures based on target version.

Related Skills

Explore More Software Engineering Skills→
OpenAEC-FoundationOpenAEC-Foundation
30

blender-core-versions

Document Blender Python API breaking changes and migration paths across versions.

Official
Intermediate
OpenAEC-FoundationOpenAEC-Foundation
30

blender-impl-addons

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

Official
Advanced
marcelocantosmarcelocantos

sync-globals

Enforce global CLAUDE.md directives across managed repositories and generate a compliance report.

Community
Intermediate
OpenAEC-FoundationOpenAEC-Foundation
30

blender-syntax-addons

Document Blender addon syntax and patterns for bl_info and blender_manifest.toml formats.

Official
Intermediate