godot-4-migration

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

Quality

58%

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

Quality

Content

51%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 skill provides useful, concrete before/after code examples for the most common Godot 3→4 syntax changes, making it a decent quick-reference. However, it lacks a sequenced migration workflow with validation steps, which is critical for a destructive operation like project migration. The introductory sections add unnecessary verbosity, and the content could benefit from splitting detailed references into separate files.

Suggestions

Add a step-by-step migration workflow (e.g., 1. Back up project, 2. Run Godot 4's built-in converter, 3. Fix remaining errors by category, 4. Test scenes, 5. Validate) with explicit validation checkpoints.

Remove the 'Overview' and 'When to Use This Skill' sections—they explain things Claude can infer from context and waste tokens.

Consider referencing a separate file for a comprehensive rename/API change table (node renames, method renames, enum changes) to keep SKILL.md as a concise overview.

Add a verification step or checklist at the end to confirm migration completeness (e.g., 'Search for remaining `yield` calls, `setget` patterns, string-based signal connections').

Dimension	Reasoning	Score
Conciseness	The 'Overview' and 'When to Use This Skill' sections are unnecessary padding—Claude doesn't need to be told when to apply a migration guide. The 'Key Changes' section explaining that 'Godot 4 uses @ for keywords that modify behavior' is mildly redundant. However, the code examples themselves are reasonably tight and the before/after format is efficient.	3 / 5
Actionability	The skill provides concrete, executable before/after code examples for each major change (annotations, setters/getters, tweens, signals, yield→await). Minor gaps exist—e.g., no complete migration checklist or script to automate renames—but the examples are copy-paste ready and cover the most common migration scenarios.	4 / 5
Workflow Clarity	There is no sequenced migration workflow. The content is a reference of syntax changes but doesn't guide the user through a migration process step-by-step (e.g., run the converter first, then fix remaining issues, then validate). For a migration task that involves destructive changes to a codebase, the lack of any validation checkpoints or ordering is a significant gap.	2 / 5
Progressive Disclosure	The content is structured with clear headers and sections, which is good. However, at ~100 lines it's all inline with no references to external files for deeper topics (e.g., a full API rename table, node renames, or a comprehensive export annotation reference). For a migration guide that could cover many more changes, some content splitting would be beneficial.	3 / 5
	Total	12 / 20 Passed

Description

64%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 identifies a clear and distinctive niche (Godot 3.x to 4 migration) with relevant trigger terms, but it reads more as a topic summary than an actionable skill description. It lacks an explicit 'Use when...' clause and could benefit from listing concrete actions rather than just topic areas.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about migrating, upgrading, or porting a Godot 3.x project to Godot 4.'

Replace topic nouns with concrete actions, e.g., 'Converts GDScript 1.0 syntax to 2.0, updates Tween API calls, migrates @export annotations, and fixes signal connection syntax.'

Include additional trigger synonyms users might say, such as 'upgrade', 'porting', 'breaking changes', '@onready', or 'GDScript conversion'.

Dimension	Reasoning	Score
Specificity	Names the domain (Godot 3.x to 4 migration) and mentions a few concrete areas (syntax changes, Tweens, exports), but doesn't describe specific actions like 'converts GDScript 1.0 syntax to 2.0' or 'updates export annotations'. The listed items are topics rather than actions.	3 / 5
Completeness	Has a clear 'what' (guide for migrating Godot 3.x to 4 covering specific topics), but lacks an explicit 'when' clause. There is no 'Use when...' guidance to tell Claude when to select this skill.	3 / 5
Trigger Term Quality	Includes good natural keywords like 'Godot 3.x', 'Godot 4', 'GDScript 2.0', 'migrating', 'Tweens', and 'exports'. Missing some common variations users might say like 'upgrade', 'porting', 'breaking changes', 'onready', '@export', or 'signal syntax'.	4 / 5
Distinctiveness Conflict Risk	Very distinct niche — Godot 3.x to 4 migration is highly specific and unlikely to conflict with other skills. The combination of 'Godot', 'migrating', and 'GDScript 2.0' creates a clear, unique trigger profile.	5 / 5
	Total	15 / 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: skills/godot-4-migration/SKILL.md
Commit: fbdfd63

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