runtime-triage

Classifies Godot/.NET failures into primary layer and top causes.

Updated Mar 19, 2026

Search Tags:#debugging #troubleshooting #runtime #godot #dotnet #triage #error-analysis

Ready to run

npx skills add https://github.com/LoogacyStudio/skills --skill runtime-triage

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: runtime-triage
Source: https://github.com/LoogacyStudio/skills/tree/main/plugins/godot-dotnet/skills/runtime-triage
Command: npx skills add https://github.com/LoogacyStudio/skills --skill runtime-triage

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps engineers quickly identify the primary failure layer when a Godot 4.x / .NET project experiences build, load, or runtime problems, reducing guesswork and guiding focused investigation.

Core Features & Use Cases

Classify symptoms into the correct failure layer (build/compile, restore/SDK, editor config, scene load, runtime, environment).
Extract high-signal evidence (exact error messages, stack traces, resource paths) for prioritization.
Propose 2–4 targeted next probes to isolate causes and verify fixes.
Suitable for troubleshooting Godot + .NET projects across editor and runtime contexts.

Quick Start

Provide a concise triage report for a Godot/.NET issue using the available symptoms and logs.

Frequently Asked Questions about runtime-triage

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

FAQPage Schema

How do I troubleshoot Godot .NET runtime exceptions and build failures?▼

Troubleshoot Godot .NET runtime exceptions by classifying the symptom into the correct failure layer—build, restore, editor config, scene load, runtime, or environment—and extracting high-signal evidence for a targeted triage plan.

What is the best way to debug Godot .NET startup problems and resource loading issues?▼

Debug Godot .NET startup problems by identifying the primary failure layer and applying top causes to the symptom. This guides the minimum evidence needed, like exact error signals and environment details, to isolate the root cause quickly.

Does Godot .NET error analysis require exact stack traces and environment details?▼

Yes, Godot .NET error analysis requires exact error signals, environment details, and symptom text. Generating a prioritized, testable triage plan depends on this evidence to identify the primary failure layer and top causes accurately.

How do I classify Godot .NET editor errors into the correct failure layer?▼

Classify Godot .NET editor errors by matching the symptom text against failure layers like build/compile, restore/SDK, editor config, scene load, runtime, or environment. This categorization prioritizes probes to isolate the root cause.

Can I triage Godot 4.x .NET project issues across both editor and runtime contexts?▼

Yes, you can triage Godot 4.x .NET project issues across editor and runtime contexts. The process applies to build failures, editor errors, runtime exceptions, startup problems, and resource loading issues by identifying the primary failure layer.