Landscape Auto Material

What it does

When your agent uses it

• The user asks for an auto/procedural landscape material
• Slope/altitude/distance-based layer blending
• Runtime Virtual Textures
• Biome configuration via instances

Example prompts

• “/landscape-auto-material”

Requirements

• Python 3

Workflow steps

11 steps, taken from the step headings in SKILL.md.

1. 1Forgetting bUsedWithVirtualTexturing
2. 2No RVT Volume Actor
3. 3RVT MaterialType Mismatch
4. 4Not Saving Functions Before Referencing
5. 5Missing bExposeToLibrary
6. 6Compiling in Same Block as Creation
7. 7Wrong Bulk Parameter Types
8. 8Static Switch Parameters Need UpdateStaticPermutation
9. 9Auto Layer Has Zero Weights
10. 10Layer Info/Material Family Mismatch
11. 11RVT Volume Missing or Mis-sized

What it can do on your machine

Read from SKILL.md and the folder at commit dc051be. It shows what the files ask for, not the result of running them.

• Tool permissions

  Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

  From allowed-tools in the SKILL.md frontmatter.

• Runs code

  No scripts in the folder and no shell commands in SKILL.md (its code samples are python).

  From the folder's file list and the shell code blocks in SKILL.md.

• Network

  No URLs in SKILL.md.

  From URLs in SKILL.md, links to its own repository left out.

• Credentials

  Names no API keys, tokens, secrets or passwords.

  From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Landscape Auto Material loads about 2.4k tokens when it runs. Until then it costs about 107 tokens; SKILL.md has 749 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it

~107

When it runs · the whole SKILL.md, loaded when a task matches

~2.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from kevinpbuckley/VibeUE at commit dc051be, republished under its MIT licence (© kevinpbuckley). 749 words, ~2,448 tokens.

name

landscape-auto-material

description

Create production-quality landscape materials with the master-material + material-function + material-instance paradigm, RVT, and auto-layering. Use when the user asks for an auto/procedural landscape material, slope/altitude/distance-based layer blending, Runtime Virtual Textures, biome configuration via instances, or layer material functions. For basic layer-blend materials load landscape-materials.

display_name

Landscape Auto-Material System

vibeue_classes

MaterialService, MaterialNodeService, LandscapeMaterialService, RuntimeVirtualTextureService

unreal_classes

MaterialExpressionMaterialFunctionCall, MaterialExpressionRuntimeVirtualTextureOutput, MaterialExpressionRuntimeVirtualTextureSample, RuntimeVirtualTexture…

keywords

auto material, auto layer, master material, material function, material instance, runtime virtual texture, RVT, altitude blend, slope blend, distance blend…

Master Material (M_Landscape_Master)
 ├── Material Functions (reusable logic blocks)
 │   ├── MF_AutoLayer     ── auto-selects layers by altitude/slope
 │   ├── MF_Slope_Blend   ── slope mask (0=flat, 1=steep)
 │   ├── MF_Altitude_Blend ── height mask (0=below, 1=above)
 │   ├── MF_Layer_Grass    ── per-layer texture sampling
 │   ├── MF_Layer_Rock     ── per-layer texture sampling
 │   ├── MF_RVT            ── Runtime Virtual Texture output
 │   └── MF_Distance_Blend ── LOD transitions
 ├── Exposed Parameters (50+ scalar/vector/texture/switch)
 └── Material Outputs (BaseColor, Normal, Roughness, WPO, RVT)

Material Instance (MI_Landscape_Biome_01)
 ├── Inherits master material graph
 ├── Overrides parameters only (no graph editing)
 └── Different biomes = different instances of same master

import unreal, json

# For materials:
graph = json.loads(unreal.MaterialNodeService.export_material_graph("/Game/Materials/M_Landscape_Master"))
print(f"Expressions: {len(graph['expressions'])}, Connections: {len(graph['connections'])}")
for expr in graph['expressions']:
    name = expr.get('parameter_name') or expr.get('function_path') or expr.get('class')
    print(f"  [{expr['id']}] {expr['class']} - {name}")

# For material functions:
func_info = unreal.MaterialNodeService.get_function_info("/Game/Functions/MF_AutoLayer")
func_graph = json.loads(unreal.MaterialNodeService.export_function_graph("/Game/Functions/MF_AutoLayer"))

unreal.MaterialService.set_property(mat_path, "bUsedWithVirtualTexturing", "true")

unreal.EditorAssetLibrary.save_asset(func_path)

unreal.MaterialNodeService.add_function_input(func_path, "BaseColor", "Vector3", 0)
unreal.MaterialNodeService.add_function_input(func_path, "Normal", "Vector3", 1)
unreal.MaterialNodeService.add_function_input(func_path, "Roughness", "Scalar", 2)

© kevinpbuckley, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 7 other files in Content/Skills/landscape-auto-material of kevinpbuckley/VibeUE.

• SKILL.md
• architecture-details.md
• biomes-and-templates.md
• material-functions.md
• parameter-reference.md
• reference-example.md
• rvt-setup.md
• workflows.md

Open the folder on GitHubat commit dc051be