CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

55

Quality

63%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/godot-gdscript-patterns/SKILL.md

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

SKILL.md
Quality
Evals
Security

Quality

Content

43%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 lean and sectioned but largely generic: it provides no concrete GDScript guidance or examples, relies on boilerplate instructions, and points to a resources file that is absent from the bundle. It functions as a stub more than an actionable skill.

Suggestions

Add at least one concrete, copy-paste-ready GDScript example (e.g., a signal connection or a simple state-machine snippet) so the skill is actionable without requiring the missing playbook.

Replace the generic Instructions ('Apply relevant best practices and validate outcomes') with Godot-specific steps and a concrete validation checkpoint (e.g., 'run the scene in the editor and confirm no runtime errors').

Either create references/implementation-playbook.md with the promised detailed patterns or remove the dangling reference, so progressive disclosure resolves to a real file.

DimensionReasoningScore

Conciseness

The body is short and largely avoids explaining concepts Claude already knows, but the 'Do not use this skill when' section ('unrelated to godot gdscript patterns', 'different domain or tool outside this scope') and the generic Instructions ('Apply relevant best practices and validate outcomes') are padding that could be trimmed.

4 / 5

Actionability

There is no concrete GDScript code, commands, or examples — guidance is abstract ('Apply relevant best practices and validate outcomes', 'Provide actionable steps and verification') and only defers detail to a resources file, matching the minimal-guidance anchor.

2 / 5

Workflow Clarity

The Instructions give a rough generic sequence (clarify → apply/validate → provide steps) but it is not a Godot-specific workflow and validation is only vaguely implied ('validate outcomes'), with no concrete checkpoints.

2 / 5

Progressive Disclosure

Sections are well organized and the reference is one level deep and clearly signaled, but the referenced 'resources/implementation-playbook.md' does not exist in any bundle directory (references/, scripts/, assets/), so the disclosure is not actually navigable.

3 / 5

Total

11

/

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: it concisely states both the capability and explicit use-when triggers for a well-scoped Godot 4 GDScript niche. The main weakness is that it lists pattern topics rather than crisp action verbs, slightly limiting specificity.

DimensionReasoningScore

Specificity

Names the Godot 4 GDScript domain plus several concrete pattern topics ('signals, scenes, state machines, and optimization'), but these are topic categories rather than the multiple distinct action verbs (extract, fill, merge) seen in the top anchor; not quite the 'several specific actions' of a 4.

3 / 5

Completeness

Explicitly states 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, satisfying the top anchor.

5 / 5

Trigger Term Quality

Includes natural phrases users would say — 'building Godot games', 'implementing game systems', 'GDScript best practices' — but misses common variations like the '.gd' file extension or 'Godot 4', keeping it just below comprehensive.

4 / 5

Distinctiveness Conflict Risk

Godot 4 and GDScript form a clear, narrow niche with distinct triggers and minimal overlap risk against other skills.

5 / 5

Total

17

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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
Reviewed

Table of Contents

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.