More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    Godot Scene Corruption Recovery

    1

    Recover Godot scenes that fail to open, lose node references, or load with missing resources, without rebuilding them from scratch.

    $5

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Godot Scene Corruption Recovery

    Godot Scene Corruption Recovery

    Example session with this skill installed

    Apply the skill to this case: a project renamed its art folder from art/props to art/props_v2, and 14 scenes now show placeholder nodes with 61 broken references in total. Work through the protocol, decide between a bulk remap and per-scene repair, and report the checklist score.

    • Read your context and instructions
    • Compiled the godot scene corruption

    A 4.3 project had 14 scenes showing placeholder nodes after an art folder was renamed from art/props to art/props_v2. The recovery started by listing every ext_resource path in the affected scenes and confirming the new folder existed. A bulk remap replaced the old prefix in text scenes, and two binary scenes were rebuilt by re-instancing their node trees from the last good commit. Before the fix, 61 broken references were counted; after, zero remained, and a test level instancing all 14 scenes loaded without errors. The lasting fix was a rename checklist that requires a path search before any folder move is committed. This is a worked example produced by applying the skill's protocol: baseline counted first, decision table row selected on evidence, fix at the source, verification on the same conditions, and a prevention step recorded.

    Checker run on the worked example's completed checklist prints score 10.0, passed 7 of 7, failed [], ready true (exit 0).

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Recover Godot scenes that fail to open, lose node references, or load with missing resources, without rebuilding them from scratch. Use when a Godot scene file will not open, opens with broken node paths, reports missing or renamed resources, or shows nodes replaced by placeholder instances after a merge, rename, or engine version change.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Game Development.

    Thresholds are starting points and may need adjustment for different hardware or project sizes. The skill diagnoses and guides fixes; it does not replace engine, platform, or vendor tooling. Cases outside the stated scope should use a different workflow.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 23 days ago

    Software
    Git

    Permissions

    Terminal / Shell
    Write Files
    Listed23 days ago
    Updated21 days ago

    What's inside

    Frequently Asked Questions

    A clear symptom, the affected files or sessions, version details, and a backup of the originals. The skill lists the exact inputs in its contract section.

    By comparing before-and-after measurements on the same reproduction conditions, using the checklist and scoring rubric in the skill. A score of 7 or higher is required to close a case.

    Yes. The workflow scales down: fill the template, run the first checks, and verify. Small cases are where the habit of evidence-first work pays off fastest.

    New in Game Development