from Better Godot MCP18
Guided, category-based decision trees to diagnose Godot problems in physics, signals, rendering, navigation, and input.
A compact troubleshooting skill that provides step-by-step decision trees for common Godot engine problems. It helps an agent map a user's symptom (e.g., "no collision", "signal not firing", "invisible") to a diagnosis path and suggests targeted checks and fixes. Concrete checks include collision layer/mask verification, signal connection validation, visibility and z-index checks, navigation mesh baking, and input map verification.
Use this skill when a user reports runtime or editor issues in Godot — especially physics collisions, missing signals, rendering/visibility problems, navigation/pathfinding errors, or input not responding. The skill works best for developers who can provide scene paths, node names, or example error outputs.
Best used with agents that can read project files and run editor/project inspections (Claude Code, Cursor-style agents, or any agent with file access and Godot knowledge).
This skill has not been reviewed by our automated audit pipeline yet.
