Name: godot-4-migration
Rating: 61.6 (1 reviews)
Author: administrakt0r

godot-4-migration

Specialized guide for migrating Godot 3.x projects to Godot 4 (GDScript 2.0), covering syntax changes, Tweens, and exports.

Quality

73%

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-claude/skills/godot-4-migration/SKILL.md

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

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 content is highly actionable with concrete before/after code for each migration area and good organization. Its weak spots are the lack of an explicit migration workflow with validation checkpoints and a monolithic structure that could split detailed examples into reference files.

Suggestions

Add a short sequenced migration workflow with a validation checkpoint, e.g. "1) Run the official upgrade tool, 2) Fix annotations/exports, 3) Replace Tween node usages, 4) Launch the project and resolve remaining errors before committing."

Move the extended before/after code examples into a references/ file (e.g. CHANGES.md) and keep SKILL.md as a concise overview pointing to it, improving progressive disclosure.

Trim framing sentences like "Godot 4 uses `@` for keywords that modify behavior" since the before/after mapping already conveys the change.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean, leading with before/after code blocks and short headings, but includes minor framing prose ("Godot 4 uses `@` for keywords that modify behavior", the Overview sentence) that could be trimmed without loss.	4 / 5
Actionability	It provides multiple complete, copy-paste-ready GDScript before/after examples covering annotations, setters/getters, tweens, signals, typed arrays, and await, plus concrete "Do/Don't" guidance and a troubleshooting fix.	5 / 5
Workflow Clarity	Content is well-organized by change category but presented as a reference rather than a sequenced migration procedure, with no explicit validate-then-proceed checkpoint (e.g. "run the project and confirm no errors") for what is effectively a batch migration.	3 / 5
Progressive Disclosure	Sections are clearly headed and well-organized with no nested references (no bundle files exist), but the ~120-line body is a single monolithic file with no split-out reference material, so it stops short of the ideal overview-plus-one-level-deep structure.	4 / 5
	Total	16 / 20 Passed

Description

70%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 specific and clearly niched, naming the domain and several concrete migration topics with natural trigger terms. Its main weakness is the absence of an explicit "Use when..." trigger clause, which caps completeness at 3.

Suggestions

Append an explicit trigger clause, e.g. "Use when porting a Godot 3 project to Godot 4, fixing GDScript 2.0 syntax errors after upgrading, or migrating exports/Tweens/signals."

Broaden trigger terms with synonyms and file extensions users naturally say (e.g. ".gd", "porting", "upgrading") to lift trigger-term coverage toward comprehensive.

Add one or two more concrete coverage areas (e.g. signal connections, await/yield coroutines) to move specificity from several-items toward comprehensive.

Dimension	Reasoning	Score
Specificity	Names the domain (Godot 3.x→4 migration) and lists several concrete coverage areas — "syntax changes, Tweens, and exports" — matching the anchor for several specific items with minor gaps, though it is not fully comprehensive (e.g. signals, await, node renames omitted).	4 / 5
Completeness	It gives a clear "what" (a migration guide covering specific topics) but no "Use when..." clause or explicit trigger guidance, so per the rubric guideline completeness is capped at 3.	3 / 5
Trigger Term Quality	Includes natural terms a Godot developer would say — "Godot 3.x projects", "Godot 4", "GDScript 2.0", "Tweens", "exports" — giving good keyword coverage, but lacks synonyms or file extensions like ".gd" or "porting" that would reach comprehensive.	4 / 5
Distinctiveness Conflict Risk	The niche is highly specific — Godot 3.x to Godot 4 / GDScript 2.0 migration — with distinct triggers and minimal realistic overlap with other skills.	5 / 5
	Total	16 / 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-claude/skills/godot-4-migration/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.