agentleFS
arjun988arjun988/blender-skills/.claude/skills/materials/SKILL.md

materials

Skill2.2k starsChanged 4 months agoMITView on GitHub

Blender PBR and stylized material creation for metal, wood, concrete, fabric, glass, dirt, rust, and procedural shaders. Use for look development, material reuse, and production shading in Blender via MCP.

3 other projects use a version of this.

Adopted by

Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data

Week of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 0 new projectsWeek of Oct 25: 0 new projectsWeek of Nov 1: 0 new projectsWeek of Nov 8: 0 new projects
Sep 2026Oct 2026Nov 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 0 in all, so this is a hint, not a trend.

Most recently taken up by

Who's talking about arjun988/blender-skills

The biggest 5 of 12 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 12

Talked about on GitHub (12 times).

On GitHub · 12

7 more on GitHub

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 6 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Look development after UVs

    line 20
  2. Very specific:

    Create reusable masters in MAT_ prefix:

    line 35
  3. Distinctive:

    Document channel usage in material notes

    line 84
  4. Distinctive:

    Create material slots via MCP

    line 96
  5. Distinctive:

    Verify material names follow convention

    line 100
  6. Distinctive:

    Test materials in target lighting setup

    line 109
  7. Distinctive:

    Leave default material names

    line 115

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Materials

Production shading with material reuse. PBR-accurate or intentionally stylized. Minimal unique materials.

When to Use

  • Look development after UVs
  • Procedural material creation
  • Master material library setup
  • Material variation from shared masters
  • Engine export material preparation

Workflow

Master Materials → Instance Variations → Object Assignment
    → Vertex Color/Mask Setup → Validation → Export Prep

Master Material Library

Create reusable masters in MAT_ prefix:

MasterBase Setup
MAT_Metal_BasePrincipled: Metallic 1, adjustable Roughness
MAT_Plastic_BasePrincipled: Metallic 0, Specular 0.5
MAT_Fabric_BasePrincipled + Sheen
MAT_Glass_BasePrincipled: Transmission 1, IOR 1.45
MAT_Emissive_BasePrincipled: Emission strength variable
MAT_Organic_BaseSubsurface scattering enabled

Instance variations: duplicate master, adjust parameters only.

PBR Value Ranges

MaterialMetallicRoughnessNotes
Polished metal1.00.1–0.3
Brushed metal1.00.4–0.6Anisotropic if available
Painted metal0.00.3–0.5Base color = paint
Plastic0.00.3–0.6
Rubber0.00.7–0.9
Concrete0.00.8–0.95
Wood (raw)0.00.5–0.7
Glass0.00.0Transmission 1
Skin0.00.4–0.6Subsurface 0.1–0.3
Fabric0.00.7–0.9Sheen

Procedural Material Patterns

Wear mask: Noise → ColorRamp → Lerp between clean/worn Edge wear: Bevel node → Pointiness or Ambient Occlusion Dirt accumulation: AO inverted → multiply with dirt color Rust: Noise mask on metal → orange/brown color override

Material Count Budget

Asset TypeMax Materials
Hero prop3–5
Standard prop1–2
Modular piece1 (atlas)
Character3–8 (body, cloth, eyes, hair)
Environment module1–2

Vertex Color Usage

  • RGB: variation masks (wear, moss, color variation)
  • R: wear amount, G: dirt, B: wetness
  • Document channel usage in material notes

Stylized Materials

See stylized-style skill. Key differences:

  • Flatten roughness range
  • Hand-painted base color priority
  • Rim light via Fresnel mix
  • NPR toon shaders if project requires

MCP Integration

  1. Create material slots via MCP
  2. Assign materials to objects via MCP
  3. Set principled BSDF parameters via MCP
  4. Query material count per scene
  5. Verify material names follow convention

Constraints

MUST DO

  • Reuse master materials; instance variations
  • Name materials MAT_[Surface]_[Descriptor]
  • Match PBR values to style skill direction
  • Limit material count per asset budget
  • Test materials in target lighting setup

MUST NOT DO

  • Unique material per object (unless hero)
  • PBR values outside physically plausible range (realistic style)
  • Skip vertex color masks for variation
  • Leave default material names
  • Finalize materials before UVs complete

Reference Guide

TopicReferenceLoad When
Surface recipesreferences/surface-recipes.mdSpecific materials
Procedural nodesreferences/procedural-patterns.mdWear, dirt, variation

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.