Skip to content
TrustedSkillsbeta
Back to all skills

Godot Resource Data Patterns

Checked
thedivergentai·vlatest·other·LGPL-3.0

Helps with data, patterns as part of agent workflows workflows.

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 thedivergentai/game-dev-agentic-skills --skill godot-resource-data-patterns -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

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.

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 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
Manifest
skills/godot-resource-data-patterns/SKILL.md
Scanned
3 files, 272 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 a collection of Godot Engine scripts and patterns for creating reusable, inspector-friendly data structures using resources. It focuses on techniques like typed arrays, serialization, and resource sharing to manage game data efficiently, particularly for items, spells, stats, enemy configurations, and complex game state. The included scripts offer examples of common resource design challenges and best practices within the Godot environment.

When to use it

  • Creating configurable enemies with shared properties like health points (HP) or skins.
  • Managing item collections and inventory logic in a structured way.
  • Saving complex game state directly to .tres files for persistence.
  • Implementing reactive data containers that emit signals when values change.
  • Generating resources dynamically at runtime, such as loot drops or procedural content.

Key capabilities

  • Serialized Data Containers: Defining custom data structures for use in the Godot Inspector.
  • Flyweight Pattern Implementation: Efficiently sharing resource instances to minimize memory usage.
  • Local Resource Handling: Preventing cross-contamination of resources when duplicating them within scenes.
  • Reactive Data Signals: Creating resources that emit signals upon property modification.
  • Resource Preloading Strategies: Caching resources before gameplay to avoid frame drops.
  • Nested Resource Serialization: Building and saving complex data hierarchies using nested resource properties.

Example prompts

  • "Show me the script for creating a reactive stats container in Godot."
  • "How can I efficiently share enemy configurations using resources?"
  • "Give me an example of serializing game state to a .tres file."
  • “What is the best way to handle 'Local to Scene' resources?”

Tips & gotchas

  • Avoid Direct Modification: Always use .duplicate() when modifying resource instances to prevent unintended changes to saved files.
  • Use Typed Arrays: Employ Array[ResourceClass] for type safety instead of untyped arrays in your Resource definitions.
  • Don't Store Node References: Avoid storing references to Nodes within Resources, as these are scene-specific and cannot be reliably serialized. Use NodePaths or UIDs instead.