godot-greybox-to-asset

Migrate Godot greybox levels to sourced assets while preserving layout and navmesh.

8|3|Updated Jun 12, 2026
One-click install
npx skills add https://github.com/arthur0n/xenodot-forge --skill godot-greybox-to-asset
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: godot-greybox-to-asset
Source: https://github.com/arthur0n/xenodot-forge/tree/main/plugin/skills/godot-greybox-to-asset
Command: npx skills add https://github.com/arthur0n/xenodot-forge --skill godot-greybox-to-asset

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns a finished Godot greybox into production-ready art without breaking the level’s layout, collisions, or navigation. It prevents the common failure mode where placeholders are removed too early or assets are swapped in a way that shifts the scene.

Core Features & Use Cases

  • Inventory and classify greybox nodes: Distinguish BoxMesh props from large flat surfaces before migration.
  • Safe in-place replacement: Swap props for sourced .glb models and re-skin surfaces with tileable textures while preserving node name, position, and rotation.
  • Validation-first workflow: Verify the swapped scene, then delete placeholder geometry last and re-bake navmesh afterward.
  • Use case: A level is fully blockout-built and needs to look final; this Skill coordinates the transition from placeholder boxes to sourced assets without changing the arena’s spatial read.

Quick Start

Tell the AI to migrate the selected Godot level from greybox to final sourced assets while preserving placement, validation, and navmesh safety.

Frequently Asked Questions about godot-greybox-to-asset

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

FAQPage Schema
How do I swap greybox levels for final 3D assets in Godot without breaking spatial layout?▼

To swap greybox levels for final 3D assets in Godot without breaking spatial layout, replace BoxMesh placeholders with sourced .glb props using in-place swaps that preserve node name, position, and rotation. This prevents shifting the scene during the art pass.

When should I delete placeholder geometry during a Godot art pass?▼

Delete placeholder geometry during a Godot art pass only after verifying the swapped scene. This validation-first workflow ensures sourced .glb models are correct before removing BoxMesh props and re-baking the navmesh.

How does navmesh rebaking work after replacing greybox geometry with final assets?▼

Navmesh rebaking after replacing greybox geometry requires final .glb geometry to be installed first. The workflow validates the swapped scene, deletes placeholder geometry, and then re-bakes the navmesh to match the new collision surfaces.

What is the best way to migrate BoxMesh placeholders to .glb props in a Godot .tscn file?▼

The best way to migrate BoxMesh placeholders to .glb props in a Godot .tscn file is to inventory and classify greybox nodes, distinguishing props from large flat surfaces, then perform safe in-place replacements while preserving placement, collisions, and navigation.

Why does replacing greybox surfaces with tileable textures shift the Godot scene?▼

Replacing greybox surfaces with tileable textures shifts the Godot scene if placeholders are removed too early or assets are swapped without preserving node name, position, and rotation. Safe in-place re-skinning prevents this failure mode.

Can I use this greybox to asset migration workflow for both props and large flat surfaces?▼

Yes, this greybox to asset migration workflow handles both props and large flat surfaces. It swaps props for .glb models and re-skins large surfaces with tileable textures, preserving spatial layout, collisions, and navigation for both types.