Skip to content
TrustedSkillsbeta
Back to all skills

Godot Debugging

Checked
zate·vlatest·testing

Automates Godot Engine debugging tasks like breakpoint setting, variable inspection, and error reproduction.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add zate/cc-godot --skill godot-debugging -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

zate

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.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

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 zate/cc-godot at d9796f75c3.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
d9796f75c3
Manifest
plugins/gd/skills/godot-debugging/SKILL.md
Scanned
1 file, 559 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill provides expert assistance with debugging Godot Engine projects. It leverages a deep understanding of common Godot errors and offers solutions for parser/syntax issues, identifier declaration problems, invalid property access, runtime errors related to null references, and incorrect operand usage in calculations. The skill focuses on identifying the root cause of these errors and providing code examples demonstrating correct approaches.

When to use it

  • You're encountering "Parse Error: Expected..." messages and need help understanding syntax requirements like colons and indentation.
  • You receive "Identifier not declared" errors and are unsure why a variable isn’t recognized.
  • You get "Invalid get index" errors when trying to access properties of nodes in your scene tree.
  • Your game is crashing with runtime errors involving null instances or invalid operations.
  • You're new to Godot and need guidance on common pitfalls and best practices for error prevention.

Key capabilities

  • Identifies the root cause of common Godot Engine parser, syntax, identifier, and runtime errors.
  • Provides code examples demonstrating correct coding practices to avoid these errors.
  • Offers solutions for issues like missing colons, incorrect indentation, undeclared variables, null references, and invalid property access.
  • Includes guidance on checking for node existence before accessing properties.

Example prompts

  • "I'm getting a 'Parse Error: Expected ...' error in my Godot script. Can you help me fix it?"
  • "Why am I seeing an 'Identifier not declared' error when using my_variable? "
  • "My game is crashing with a 'null instance' error. What could be causing this?"

Tips & gotchas

  • The skill focuses on common errors; more complex or custom issues may require further investigation.
  • Pay close attention to the code examples provided, as they illustrate correct syntax and variable handling.
  • Ensure consistent use of tabs or spaces for indentation within your Godot scripts.