Skip to content
SkillModel-led2,010 tokens in use

godot-signals-groups

Helps an agent connect Godot 4.7 nodes with typed signals, Callables, groups and event bus autoloads, and debug handlers that fire twice or never.

9,684 stars on the repository Apache License 2.0gamedev-skills/awesome-gamedev-agent-skills · skills/godot/godot-signals-groups
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-signals-groups costs

88tokens idle
2,010tokens in use
3,175tokens, 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 Model-led

Script-ledMixedModel-led

Mostly instructions, so how well it works depends on the model that follows them.

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

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
  • Structure23/25
  • Examples12/15
  • Output10/15
  • Size13/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 55
  • Writes files−8

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

    SKILL.md, line 55

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 decouple Godot 4.7 nodes. A child emits a typed signal upward, the parent connects to it, and groups let one call reach every enemy or checkpoint without holding references.

It includes patterns for emitting from a reusable pickup, one-shot and bound connections, call_group broadcasts and a headless test that a signal has exactly one connection. A gotcha list covers duplicate connections from lambdas, argument mismatches, global group names and the Godot 3 connect syntax.

What You Get

  • A core workflow from choosing the signal direction to connecting, using groups and checking the wiring at runtime
  • GDScript patterns for emitting from a coin pickup, one-shot and bound connections, and call_group broadcasts
  • A headless test that checks a signal has exactly one connection, plus a smoke run that greps the log for errors
  • A gotcha list for duplicate lambda connections, lambdas that outlive their nodes, argument mismatches and groups shared across scenes

Common Use Cases

  • Letting a pickup or enemy announce events without references to the HUD
  • Debugging a handler that fires twice, never or logs already connected
  • Pausing or saving every node in a group with one call
  • Setting up an event bus autoload for cross-scene events

What Makes It Unique

The skill explains why a new lambda on every connect stacks silently and why call_group ignores nodes without the method, two causes of quiet bugs. It reads the connection lines in scene files, so an agent can wire editor connections as text, and it proves the result with a headless run.

Under The Hood

The agent loads the SKILL.md and, when needed, a reference on connection flags, awaiting signals and an event bus. It edits scene and script text files in your project, writes a small GDScript test, and runs the Godot binary headless, once for the test and once as a smoke run with output redirected to a log file that it searches with grep. If you edited scene connections it also runs the Python project checker from a sibling skill. It fetches no web pages and calls no APIs; without a Godot binary it asks you to run the command and paste the log.

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