Name: godot-gdscript-patterns
Rating: 49.6 (1 reviews)
Author: administrakt0r

godot-gdscript-patterns

Master Godot 4 GDScript patterns including signals, scenes, state machines, and optimization. Use when building Godot games, implementing game systems, or learning GDScript best practices.

Quality

53%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/antigravity-bundle-indie-game-dev/skills/godot-gdscript-patterns/SKILL.md

The canonical home for this skill is godot-gdscript-patterns in administrakt0r/AI-Agents-Safe-Coding-Skills

Quality

Content

25%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill is essentially a stub that delegates all substantive content to a referenced file (`resources/implementation-playbook.md`) that is not provided in the bundle. The SKILL.md body contains no GDScript code, no concrete patterns, no specific examples, and only generic meta-instructions. It fails to deliver on its promise of covering signals, scenes, state machines, and optimization.

Suggestions

Add at least 2-3 concrete, executable GDScript code examples directly in SKILL.md covering core patterns (e.g., signal connection, scene instantiation, basic state machine).

Replace the generic instructions ('Clarify goals, constraints, and required inputs') with domain-specific guidance for Godot 4 development workflows.

Provide the referenced `resources/implementation-playbook.md` bundle file, or inline the essential patterns so the skill is functional standalone.

Remove the boilerplate 'Do not use this skill when' section and the generic 'Use this skill when' list, replacing them with a concise one-line scope statement.

Dimension	Reasoning	Score
Conciseness	The 'Use this skill when' and 'Do not use this skill when' sections are boilerplate padding that don't add value. The instructions section is generic ('Clarify goals, constraints, and required inputs') rather than domain-specific. However, it's not excessively verbose — it's short but wastes tokens on non-informative content.	3 / 5
Actionability	There is zero concrete, executable guidance — no GDScript code examples, no specific commands, no patterns demonstrated. The instructions are entirely vague ('Apply relevant best practices and validate outcomes') and delegate everything to a referenced file that isn't provided in the bundle.	1 / 5
Workflow Clarity	The instructions list a rough sequence of steps ('Clarify goals', 'Apply best practices', 'Provide actionable steps') but these are generic meta-instructions, not a concrete workflow. There are no validation checkpoints, no specific sequences for any of the claimed domains (signals, state machines, etc.).	2 / 5
Progressive Disclosure	The skill references `resources/implementation-playbook.md` for detailed patterns, which is a reasonable structure in principle. However, no bundle files are provided, meaning the reference is unverifiable and potentially broken. The SKILL.md itself contains no substantive content — it's an empty shell pointing to a file that may not exist.	2 / 5
	Total	8 / 20 Passed

Description

82%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description has strong completeness with explicit 'what' and 'when' clauses, and is highly distinctive in its Godot 4 niche. Its main weakness is that it lists topic areas (signals, scenes, state machines) rather than concrete actions the skill performs, making it read more like a course syllabus than a capability description. The word 'Master' at the start is also somewhat vague about what the skill actually does.

Suggestions

Replace topic-area listing with concrete actions, e.g., 'Generates GDScript code, debugs signal connections, designs scene hierarchies, implements state machines, and optimizes performance' instead of 'Master Godot 4 GDScript patterns including signals, scenes, state machines, and optimization'.

Add more trigger term variations such as 'Godot Engine', '.gd files', 'nodes', 'autoloads', or 'GDScript 2.0' to capture a wider range of user queries.

Dimension	Reasoning	Score
Specificity	Names the domain (Godot 4 GDScript) and lists several topic areas (signals, scenes, state machines, optimization), but these are patterns/concepts rather than concrete actions. It doesn't describe what the skill actually does (e.g., 'generates GDScript code', 'refactors scene trees', 'debugs signal connections').	3 / 5
Completeness	Clearly answers both 'what' (master Godot 4 GDScript patterns including signals, scenes, state machines, and optimization) and 'when' (use when building Godot games, implementing game systems, or learning GDScript best practices) with explicit trigger phrases.	5 / 5
Trigger Term Quality	Includes good natural keywords like 'Godot', 'GDScript', 'signals', 'scenes', 'state machines', 'Godot games', and 'best practices'. Missing some common variations like 'Godot Engine', '.gd files', 'nodes', 'exports', 'autoloads', or 'Godot 4.x'.	4 / 5
Distinctiveness Conflict Risk	Highly distinctive with a clear niche targeting Godot 4 and GDScript specifically. The combination of engine-specific terms (Godot, GDScript, signals, scenes) makes it very unlikely to conflict with other skills.	5 / 5
	Total	17 / 20 Passed

Validation

90%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/antigravity-bundle-indie-game-dev/skills/godot-gdscript-patterns/SKILL.md
Commit: 57c135b

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.