← Search

blender-pbr-materials
Developer tools 📌 Pinned version: commit 71d031d
⚙ Needs: Before you start: read this whole install prompt…

blender-pbr-materials

Physically based materials in Blender 5.2 LTS+: metal/roughness rules, Principled BSDF inputs, sRGB vs Non-Color color spaces, measured albedo/F0 values from a reference table, texture-set auto-wiring with ORM packing and DirectX-to-OpenGL normal fixes, alpha and displacement rules, view transforms, and engine-ready export rules for glTF, Unreal, Unity and Roblox, with a builder script that creates the material inside Blender.

At a glance
What
Physically based materials in Blender 5.2 LTS+: metal/roughness rules, Principled BSDF inputs, sRGB vs Non-Color color spaces, measured albedo/F0 values from a reference table, texture-set auto-wiring with ORM packing and DirectX-to-OpenGL normal fixes, alpha and displacement rules, view transforms, and engine-ready export rules for glTF, Unreal, Unity and Roblox, with a builder script that creates the material inside Blender.
Cost
Free
Needs
Before you start: read this whole install prompt, tell me in a few lines what this skill does and what installing it involves, and wait for my go-ahead before you do anything else.
Install
Copy the installer prompt below into your Muse — your agent does the rest.

Version:

⌁

Install

Copy the install package below, then paste it into Muse📌 Pinned version: commit 71d031d
Wanna be extra careful?

The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?

How to check a build before installing →

🧭 What this touches
Based on the install prompt we scanned, this build does not run commands, make third-party network calls, install packages, write files, or ask for API keys.
Install prompt analysis · 2026-10-19
🔒 Security and provenance
📌 Pinned version: commit 71d031d · 2026-10-19
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify

Before you start: read this whole install prompt, tell me in a few lines what this skill does and what installing it involves, and wait for my go-ahead before you do anything else. Prerequisites: Blender 5.2 LTS or newer is required to use this skill (its Principled BSDF inputs, color-space rules and Python API notes are written and tested for Blender 5.2 LTS+; the README and SKILL.md both state this). Install Blender yourself first if you do not have it: do not install Blender, any add-on, any package or any other skill during this install. No account, no API key, no paid service and no telemetry are required for the install itself. Copying the skill folder itself does not run Blender or any of its scripts. Install "blender-pbr-materials" for me. It is a physically based materials skill for Blender: a SKILL.md playbook (metal/roughness rules, Principled BSDF inputs, sRGB vs Non-Color color spaces, measured albedo/F0 values, texture-set auto-wiring, ORM channel packing, DirectX vs OpenGL normals, alpha modes, displacement, view transforms and engine-ready material rules), a measured-values reference table, plus one Python builder script and its shared helper that run only inside Blender at use time. Repository: https://github.com/EL4CTEO/blender-skills (the skill is the whole skills/blender-pbr-materials/ folder at the pinned commit: SKILL.md, references/ and scripts/) Pinned version: install the code at commit 71d031dab8bc6729504d11a78cbe91945401045f exactly. Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Clone https://github.com/EL4CTEO/blender-skills into a temporary folder, check out commit 71d031dab8bc6729504d11a78cbe91945401045f, and copy the skills/blender-pbr-materials/ folder from that checkout. Then compare every file in the folder with the fingerprints recorded for this listing on 2026-10-19: [FINGERPRINTS] - SKILL.md: SHA-256 4ef5b352cca591ce68f9293dd5b805d1f7ded967d770862958a41ab3007c2644 - references/pbr-values.md: SHA-256 d92f53568ea1525c84d68fc7077abfa9cc64a517ac9472fdc18b873784b84d40 - scripts/_bpyx.py: SHA-256 a3339ba8a678469e8ed29510e32a7331e0235202191ca4edb977af4720819b4b - scripts/build_pbr_material.py: SHA-256 797b2fba1f384950feeb75e1681ee086abd493566d9a1794e650c0ebe851e296 If a file does not match, it changed since the listing was prepared: do not install it yet, tell me what you found and let me decide. 2. Read SKILL.md, references/pbr-values.md and both scripts in full and tell me in plain words: what the skill does when used, which services it connects to, whether it reads or sends any personal information or keys, and anything that seems unusual. Stop on any red flag and tell me before going further. Confirm these points from the files: - The skill folder holds four files only: SKILL.md (5,929 bytes), references/pbr-values.md (2,645 bytes), scripts/_bpyx.py (4,503 bytes) and scripts/build_pbr_material.py (11,905 bytes). SKILL.md is the playbook: metallic is binary (0 dielectric or 1 raw metal), base color is albedo with no baked lighting, roughness carries the realism and must be broken up, Base Color and Emission use sRGB while Roughness, Metallic, Normal, AO, Height, Opacity and ORM use Non-Color, leave IOR 1.5 and Specular IOR Level 0.5 for almost all dielectrics, Blender/glTF/Unity/Roblox normals are OpenGL (Y+) while Unreal/DirectX normals are Y- so flip G when converting, and AO ships in the ORM red channel for engines. It also maps the Principled BSDF (5.2) inputs, the engine export rules for glTF, Unreal, Unity and Roblox, the alpha modes (DITHERED or BLENDED), displacement, the view transforms (AgX, Khronos PBR Neutral, Standard, ACES) and the rule to bake procedural setups before engine export. references/pbr-values.md holds the measured values SKILL.md points to: linear and sRGB F0/albedo and roughness ranges for metals and dielectrics (sources: Unreal Engine physically-based materials docs, physicallybased.info, DONTNOD charts) plus sanity checks for a texture set. - Nothing is sent anywhere during installation itself; the only download at install time is the skill folder from GitHub at the pinned commit. The files name no account, no API key, no telemetry and no remote service, and neither script contains any network, HTTP, socket, subprocess or package-install code: build_pbr_material.py imports only Blender's bpy module and the Python standard library (os, re, sys), plus its sibling _bpyx.py; _bpyx.py imports only bpy and the standard library (argparse, json, sys). - At use time, everything runs locally inside Blender on files and objects I point you at, and only when I ask you to use the skill, which is a separate step from this install. scripts/build_pbr_material.py builds one Principled BSDF material: in texture mode it detects maps by filename (Poly Haven, ambientCG, Substance and Unreal-style suffixes), sets their color spaces (color maps to sRGB, data maps to Non-Color), splits an ORM map into roughness, metallic and an AO output wired to a "glTF Material Output" group, flips DirectX normals to OpenGL, and wires emission, opacity and height/displacement; in preset mode it applies one of 18 measured presets (gold, silver, copper, iron, aluminum, chrome, titanium, brass, plastic, rubber, wood, concrete, glass, water, skin, fabric, paint, ceramic) with an optional --color override, --tile, --alpha clip or blend and --displacement bump or both, then assigns the material to mesh objects I name and prints one compact JSON result line. scripts/_bpyx.py is its shared helper (arguments after --, JSON output, object selection, triangle counts). The texture files it loads at use time are local files at paths I give; nothing is uploaded and no external host is contacted at use time. The only file write at use time is a .blend save, and only when a --save path is explicitly passed at use time. - SKILL.md says the execution model lives in a separate skill, blender-core, and points to other separate skills for baking procedural setups (blender-texture-baking) and for draw-call budgets (blender-game-optimization). None of those skills is part of this listing and none is installed here; this install is the blender-pbr-materials folder only. The repository contains 22 skills in total and its upstream installer (install/install.sh, install/install.ps1, or the Claude Code plugin route in the README) would install all of them: do not use that installer for this listing. - Blender 5.2 LTS+ is a use-time prerequisite, not something to fetch now: do not download or install Blender, a Blender MCP server, or any other skill or package during this install. 3. When I say "yes, install", install it as a skill: copy the whole blender-pbr-materials folder into the agent's skills directory, in a folder named "blender-pbr-materials", keeping all four files and their references/ and scripts/ subfolders exactly as fingerprinted. 4. Verify with no network calls: frontmatter valid, files in place, fingerprints still matching after the copy. 5. Report what was installed, where, and what I still need to do myself (for example: have Blender 5.2 LTS or newer installed myself before any use, provide any .blend file, texture folder and object names myself, and decide myself on any --preset, --alpha, --displacement or --save use; using the skill is a separate step that only starts when I ask for it, and no use-time run happens during this install). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.

?

Questions

How do I install a build?

Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.

Where does my money go?

Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.

What does the ✓ next to a creator’s name mean?

It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.