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

79%

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/game-development/skills/godot-gdscript-patterns/SKILL.md

Quality

Content

76%Weight 40%Scale 1-5

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

The body is well-structured with a fully executable worked example and a clear progressive-disclosure pointer to details.md. Weaknesses are the missing reference to advanced-patterns.md and the absence of an explicit usage workflow with checkpoints.

Suggestions

Add a brief reference to references/advanced-patterns.md in the Detailed patterns section so the bundled advanced material is discoverable, e.g. "For state machines and object pooling, see references/advanced-patterns.md."

Trim obvious comments like "# Exports (Inspector-editable)" and "# Private variables (convention: underscore prefix)" that restate GDScript knowledge Claude already has.

Add a short "How to use this skill" step sequence (e.g., identify the system → pick a matching pattern in details.md → adapt the worked example → test in a minimal scene) to make the workflow explicit.

Dimension	Reasoning	Score
Conciseness	The body is efficient with a single-sentence intro, a tight bullet list, and an ASCII architecture tree, but explanatory comments like "# Exports (Inspector-editable)", "# Onready (initialized when ready)", and the underscore-convention note are minor over-explanation Claude could do without.	4 / 5
Actionability	The Player class example is complete and copy-paste ready (signals, exports, _ready, _physics_process, take_damage), covering the common movement/health/damage cases a user would build.	5 / 5
Workflow Clarity	An implicit reading order exists (When to Use → Core Concepts → detailed references) with a navigation hint, but there is no sequenced multi-step workflow with checkpoints, which fits the patterns-reference nature yet leaves guidance implicit.	3 / 5
Progressive Disclosure	The overview is clear and references/details.md is well-signaled one level deep ("Read that file when the navigation tier above is insufficient"), but the bundled references/advanced-patterns.md is never surfaced in the body, leaving a navigation gap.	4 / 5
	Total	16 / 20 Passed

Description

82%Weight 40%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.

A strong description with an explicit Use-when clause and a clear, distinctive niche. The main weakness is generic action verbs and the absence of file-extension synonyms like .gd/.tscn.

Dimension	Reasoning	Score
Specificity	Names the Godot 4 GDScript domain and enumerates specific pattern areas (signals, scenes, state machines, optimization), but the verbs ("master", "building", "implementing", "learning") are generic rather than concrete actions like "extract" or "fill".	3 / 5
Completeness	Explicitly 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 concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes natural phrases users would say ("building Godot games", "implementing game systems", "learning GDScript best practices"), but omits file-extension synonyms like ".gd" and ".tscn" that would round out coverage.	4 / 5
Distinctiveness Conflict Risk	Godot 4 GDScript is a sharply defined niche with distinctive triggers (Godot, GDScript, game systems), making conflict with other skills minimal.	5 / 5
	Total	17 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: wshobson/agents
Path: plugins/game-development/skills/godot-gdscript-patterns/SKILL.md
Commit: d6837ae

Reviewed: about 12 hours 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.