Godot Scene Management
CheckedAutomates Godot scene loading, saving, organization, and duplication tasks within your project.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add thedivergentai/game-dev-agentic-skills --skill godot-scene-management -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
thedivergentai
Taken from the source listing. We haven't verified who controls this account.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.
Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No undeclared network calls: passed
Makes no network calls.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned thedivergentai/gd-agentic-skills at 4c4d0ff5c4.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- 4c4d0ff5c4
- Scanned
- 3 files, 291 lines
About this skill
What it does
This skill enables AI agents to programmatically manage Godot game scenes, allowing for dynamic loading, saving, and switching of scene states within a project. It facilitates automated level transitions and runtime asset manipulation directly through code execution.
When to use it
- Automating the loading of new levels or maps during gameplay without manual intervention.
- Dynamically swapping UI overlays or character states based on game logic triggers.
- Saving specific scene configurations to disk for later restoration or debugging purposes.
- Orchestrating complex scene hierarchies by programmatically attaching and detaching nodes.
Key capabilities
- Load scenes from file paths at runtime.
- Save current scene state to persistent storage.
- Switch between different active scenes dynamically.
- Manage scene tree structures via script commands.
Example prompts
- "Load the 'level_2.tscn' scene and replace the current one."
- "Save the current game state to a file named 'checkpoint.dat'."
- "Switch the active scene to 'menu_ui.tscn' when the player quits."
Tips & gotchas
Ensure all referenced .tscn or .tres files exist in your project's res:// directory before attempting to load them, as missing assets will cause runtime errors. This skill is designed for Godot 4.x projects; compatibility with older versions may vary depending on the underlying engine API used by the agent.