godot-docs

Verify Godot 4.x API signatures, renamed properties, and deprecated usage.

8|3|Updated Jun 12, 2026
One-click install
npx skills add https://github.com/arthur0n/xenodot-forge --skill godot-docs-arthur0n
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: godot-docs
Source: https://github.com/arthur0n/xenodot-forge/tree/main/plugin/skills/godot-docs
Command: npx skills add https://github.com/arthur0n/xenodot-forge --skill godot-docs-arthur0n

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents silent Godot API mistakes by checking the official docs before you rely on a class, method, signal, property, or enum. It is especially useful when you are dealing with version mismatches, renamed properties, or uncertain signatures that can break builds without obvious clues.

Core Features & Use Cases

  • API Verification: Confirm the exact Godot 4.x signature for classes, methods, signals, properties, and enums.
  • Deprecation Checks: Look up recommended patterns and replacement APIs when something may be outdated or renamed.
  • Targeted Research: Search for the right class or page when you only know part of the engine concept you need.
  • Use Case: Before writing a gameplay script that uses a physics or character controller API, verify the documentation first so you do not introduce a Godot 3-to-4 mismatch.

Quick Start

Ask the assistant to verify the official Godot API for the class or property you want to use before writing code.

Frequently Asked Questions about godot-docs

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify Godot 4.x API signatures to prevent scripting mistakes?

You can verify Godot engine APIs by checking official documentation to confirm exact signatures for classes, methods, signals, properties, and enums before writing code. This prevents silent build errors caused by incorrect usage, version mismatches, or renamed properties.

Why does my Godot script break due to Godot 3 to 4 migration issues?

Godot scripts often break during 3 to 4 migration due to renamed properties and deprecated usage. Checking the official Godot 4.x documentation to look up recommended patterns and replacement APIs helps identify and resolve these version mismatch issues.

How do I check for deprecated properties and replacement APIs in Godot?

You can check for deprecated properties in Godot by looking up the official docs to find recommended patterns and replacement APIs. This ensures you are using current engine scripting standards and prevents relying on outdated classes or methods.

Do I need a specific MCP tool to look up Godot engine classes and methods?

Yes, looking up Godot engine classes and methods requires access to the Godot docs MCP tools. These tools confirm the exact signatures, signals, properties, and enums to verify the official API before you implement your code.

What is the best way to find the right Godot class when I only know part of the engine concept?

The best way to find the right Godot class is to perform targeted research within the documentation. You can search for specific pages and concepts to verify the correct API class, method, or enum needed for your implementation.