Skip to content
SkillScript-led2,221 tokens in use

godot-nodes-scenes

Structures Godot 4.7 scenes, instances PackedScenes, sets up autoloads, and checks a project for broken res:// paths and uids with a Python script.

9,684 stars on the repository Apache License 2.0gamedev-skills/awesome-gamedev-agent-skills · skills/godot/godot-nodes-scenes
npx skills add gamedev-skills/awesome-gamedev-agent-skills
View source

Install command as written in the repository's README

Skill label

measured from its files

What installing godot-nodes-scenes costs

97tokens idle
2,221tokens in use
2,959tokens, up to

Idle is what sits in context while the skill is installed. In use is its instructions, loaded when it runs. Up to adds the files its instructions link. Counts are approximate, made offline with cl100k_base.

Model dependence Script-led

Script-ledMixedModel-led

Most of this skill is scripts, so it behaves much the same whichever model runs it.

This describes the skill's structure, how much of it is scripts. It does not say how well it works. Scripts: scripts/check_godot_project.py.

Touches

shelldetectedwrites filesdetected

Declared tags come from the skill's frontmatter; detected ones from its scripts, its code blocks and the commands it names in inline code. This is detected, not audited.

How it scores

Quality

How well the skill is written, counted from its own files: its frontmatter, its steps, examples, stated output and constraints, its size and whether every file it ships is one it names.How we score it →
Excellent
  • Frontmatter12/15
  • Structure25/25
  • Examples12/15
  • Output10/15
  • Size15/15
  • Resources15/15

Security

Starts at 100 and loses points for each thing in the skill's files that a reader should look at first.How we score it →
Excellent
  • Runs shell commands−5

    does this on the machine, and the frontmatter does not say so

    SKILL.md, line 60
  • Writes files−8

    does this on the machine, and the frontmatter does not say so

    SKILL.md, line 61

Repository health

Pre-computed score based on development activity, maintenance, community, maturity, and trend momentum.How we score it →
Good
  • Development activity92
  • Maintenance96
  • Community60
  • Maturity24
  • Momentum40

This skill helps an agent compose Godot 4.7 games from small reusable scenes, instance them at runtime and reach nodes without crashing on freed or missing ones. It starts by reading project.godot for the main scene and autoload list, and the .tscn files for the node tree.

It includes patterns for instancing a scene with correct local positions, safe node access with $, unique names and get_node_or_null, an autoload singleton, and changing the running scene. A bundled read-only Python checker reports missing or wrong-case res:// paths, undeclared resource ids, bad parent paths and stale uid sidecar files, and needs no Godot binary.

What You Get

  • A core workflow from reading project.godot and scenes to instancing, safe node access, autoloads and queue_free()
  • GDScript patterns for instancing a bullet, safe $ and % access, an autoload singleton and a scene change
  • A Python project checker that lists errors and warnings for broken references, with a JSON output mode
  • A gotcha list covering null paths, mid-frame free, add_child timing, autoload order, deferred scene changes and moved files

Common Use Cases

  • Spawning bullets, enemies or UI scenes at runtime
  • Debugging a $Path or get_node() call that returns null
  • Repairing references after files were moved or renamed outside the editor
  • Registering a game state singleton as an autoload

What Makes It Unique

The skill ships a read-only checker that understands Godot’s uid-first loading, so it separates real errors from stale paths Godot can still recover. It checks case differences that work on Windows and macOS but break on Linux and in exported packs. The other Godot skills in the repository call this checker after they add or move scenes.

Under The Hood

The agent loads the SKILL.md and, when needed, a reference on saving scenes built in code, scene inheritance and deferred tree changes. It then runs a local Python script that reads your project’s text files, such as scenes, resources, scripts and project.godot, and prints findings; its own description says it is read-only, never edits anything and needs no Godot binary. It uses only the Python standard library and no network. Optionally the agent also runs the Godot binary headless on a scene for a few hundred frames, with the log redirected to a file and searched with grep, which writes a log file in your project.

Join founders building with open source

Opinionated takes, migration guides, cost-saving tips, and insights from the open source ecosystem.

Subscribe on SubstackJoin 750+ subscribers