Gecs

What it does

When your agent uses it

• The task involves ECS architecture: creating entities with components
• Defining component data classes (C prefix)
• Writing game logic systems
• Querying entities by component composition

Example prompts

• “/gecs”

Workflow steps

12 steps, taken from the first numbered list in SKILL.md.

1. 1All @export properties MUST have default values — Godot errors on Resource export without defaults
2. 2get_component() takes the CLASS, not an instance — entity.get_component(C_Health) not entity.get_component(health_instance)
3. 3Never put logic in Components — all behavior belongs in Systems
4. 4Use cmd for structural changes during iteration — direct add/remove during process() causes entity skipping
5. 5Avoid with_group() in queries — ~50x slower than with_all([C_Tag]) due to SceneTree traversal. Use tag components instead
6. 6define_components() must return fresh .new() instances — returning cached/shared instances causes state leakage between entities
7. 7Entity extends Node, NOT Node2D — entity.position does NOT work. Store position in a C_Position component. See gotchas.md G1
8. 8Component _init() must have default params — func _init(v: float = 0.0) so Component.new() works for duplication
9. 9Components are inaccessible before add_entity() — get_component() returns null until entity enters scene tree. See gotchas.md G2
10. 10Never call system.process() directly in tests — causes Array[Entity] type error + CommandBuffer not flushed. Never write…
11. 11add_system() second param is bool, not group name — set system.group before add_system(). See G15
12. 12world.process(delta) without group skips grouped systems — must pass group name. See G16

What it can do on your machine

Read from SKILL.md and the folder at commit 1d4702c. It shows what the files ask for, not the result of running them.

• Tool permissions

  Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

  From allowed-tools in the SKILL.md frontmatter.

• Runs code

  No scripts in the folder and no shell commands in SKILL.md (its code samples are gdscript).

  From the folder's file list and the shell code blocks in SKILL.md.

• Network

  No URLs in SKILL.md.

  From URLs in SKILL.md, links to its own repository left out.

• Credentials

  Names no API keys, tokens, secrets or passwords.

  From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Gecs loads about 2.7k tokens when it runs, and up to ~20k if it reads all its reference files. Until then it costs about 248 tokens; SKILL.md has 561 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it

~248

When it runs · the whole SKILL.md, loaded when a task matches

~2.7k

With references · SKILL.md plus every file in references/, read only if the agent opens them

~20k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 561 words (~2,749 tokens).

name

gecs

Read the full SKILL.md on GitHub

Files

SKILL.md and 10 other files (references) in skills/core/gecs of RandallLiuXin/GodotMaker.

• SKILL.md
• evals/evals.json
• gotchas-examples.md
• gotchas.md
• references/component.md
• references/debug.md
• references/entity.md
• references/patterns.md
• references/query.md
• references/system.md
• references/world.md

Open the folder on GitHubat commit 1d4702c