Run the Godot project and capture any build or compile errors (GDScript parse errors, bad resource paths, missing scripts). Use when the user asks about compile failures, parse errors, or why the game won't build.
This listing is imported from SkillsMP metadata and should be treated as untrusted until upstream source review is completed.
Install skill "godot-debug-build" with this command: npx skills add RJAudas/skillsmp-rjaudas-rjaudas-godot-debug-build
This source entry does not include full markdown content beyond metadata.
This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.
Related by shared tags or category signals.
Run the Godot game with pause-on-error enabled and capture any GDScript runtime errors (null dereferences, invalid calls, missing nodes). Use when the user asks why the game crashes, why something throws at runtime, or to reproduce a runtime error.
Capture the running Godot game's scene tree in one call. Use when the user asks to inspect the scene, check the node hierarchy, list what is running in the game, or verify node presence at runtime.
Pin the most recent transient Godot harness run under a stable name so it survives the next automatic cleanup. Use when the user asks to preserve, save, or keep a run for later comparison.
List all pinned Godot harness runs for this project. Use when the user asks what runs are saved, what's pinned, or wants to see the pin inventory.