Name: godot-gdscript-patterns
Rating: 59.2 (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

69%

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/AI-Agents-Safe-Coding-Skills/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

51%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 commendably concise and well-structured, but the actual guidance is generic and abstract with no executable code or concrete steps, and the single referenced resource file is missing from the bundle. Strengthening the inline instructions and providing the referenced playbook would materially raise quality.

Suggestions

Replace abstract Instructions ('Apply relevant best practices', 'Provide actionable steps') with at least one concrete, copy-paste-ready GDScript example (e.g., a signal wiring snippet or a simple state-machine skeleton).

Add an explicit validation checkpoint to the workflow (e.g., 'Run the scene and confirm no errors in the Output dock before iterating').

Create the referenced `resources/implementation-playbook.md` (or correct the path) so the progressive-disclosure pointer resolves to a real file.

Dimension	Reasoning	Score
Conciseness	The body is lean with no concept padding or over-explanation, assuming Claude's competence; every section earns its place, matching the 'lean and efficient' anchor.	5 / 5
Actionability	Instructions like "Clarify goals…", "Apply relevant best practices…", and "Provide actionable steps and verification" are abstract and even meta (telling Claude to provide steps rather than giving them); there is no concrete code, commands, or specific guidance, only a pointer to an external file.	2 / 5
Workflow Clarity	A rough sequence exists (clarify → apply → provide → open playbook) but steps are poorly defined and "validate outcomes" is a vague instruction rather than a checkpoint; validation is effectively absent.	2 / 5
Progressive Disclosure	Structure is clean (overview, use/don't-use, instructions, resources) with a one-level reference to `resources/implementation-playbook.md`, but that file and directory do not exist in the bundle, so the signaled reference is broken and navigation fails.	3 / 5
	Total	12 / 20 Passed

Description

87%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.

The description is strong: it clearly states the domain and concrete capability areas, pairs an explicit 'what' with a concrete 'Use when' trigger clause, and occupies a distinct niche. Minor room to convert pattern topics into more discrete verb-led actions.

Dimension	Reasoning	Score
Specificity	"Master Godot 4 GDScript patterns including signals, scenes, state machines, and optimization" enumerates several concrete pattern areas, matching the 'lists several specific actions' anchor; not a 5 because these are topics rather than discrete verb-actions like the 5-anchor example.	4 / 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	"building Godot games, implementing game systems, learning GDScript best practices" plus "Godot 4" and "GDScript" give good natural keyword coverage; a 5 would require more synonyms/extensions, which Godot lacks.	4 / 5
Distinctiveness Conflict Risk	"Godot 4 GDScript" is a clear, narrow niche with distinct triggers and minimal overlap risk with other skills.	5 / 5
	Total	18 / 20 Passed

Validation

93%

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

Validation for skill structure

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

	Total	15 / 16 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills/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.