How do I install the Godot skill?

Run npx skillmds@latest add autonomous-ai/godot in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Godot safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Godot?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Godot free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

autonomous-ai (@autonomous-ai) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Godot by autonomous-ai — Agent Skill

Name: Godot
Author: autonomous-ai

File contents

Game source and proof

Project: project.godot; scene: scenes/Main.tscn; starter mechanics: scripts/main.gd. Lumen draws its own art and supports keyboard and pointer/touch destinations.

sh "$GODOT_SKILLS/godot/scripts/export-web.sh"

The helper copies source (excluding build/cache directories), imports, runs scripts/proof.gd, then exports the Web preset into fresh staging. GODOT_BIN selects an editor, and GODOT_WEB_TEMPLATE an optional matching single-threaded release template. Node 20+ bootstraps through the package helper.

Proof must instantiate real gameplay and assert meaningful state transitions. On success it writes {"passed":true,"checks":[...]} to HARNESS_BUILD_DIR/proof.json; on failure exit nonzero. A missing receipt is failure even if Godot exits zero. Keep assertions relevant when replacing the starter. A standalone proof can write to Godot's user data directory when that environment variable is unset.

Use _physics_process for movement and keep per-frame work bounded. Preserve keyboard, touch/click, pause and restart when useful for the requested game. The custom web/shell.html exposes actual game state through JavaScriptBridge, not a parallel simulated game.

The build verdict means native assertions and export passed. Verify the exported game in the actual shared viewer before claiming browser readiness. A browser playthrough must exercise game results, not just see a canvas.

The viewer requires a single-threaded export (Godot 4.3+), Compatibility renderer, no service worker or persistent browser storage. Keep the editor and templates version-matched. Only Godot 4.4's known optional PWA callback warning is downgraded in the opaque sandbox; other engine errors remain visible.

Optional interaction/performance probe:

HARNESS_WORKSPACE="$PWD" node "$GODOT_SKILLS/godot/scripts/perf.mjs" build/web/index.html

Uses shared Web Viewer + Playwright and the assertions in proof.json. It reports actual interaction frame timing; inspect the recorded renderer and do not extrapolate hardware performance to other devices.

---name: godotdescription: Build Godot games with GDScript, native gameplay assertions and sandboxed Web exports. Use for Godot Studio project and game-mechanic tasks.---# Game source and proofProject: `project.godot`; scene: `scenes/Main.tscn`; starter mechanics: `scripts/main.gd`. Lumen draws its own art and supports keyboard and pointer/touch destinations.```shsh "$GODOT_SKILLS/godot/scripts/export-web.sh"```The helper copies source (excluding build/cache directories), imports, runs `scripts/proof.gd`, then exports the Web preset into fresh staging. `GODOT_BIN` selects an editor, and `GODOT_WEB_TEMPLATE` an optional matching single-threaded release template. Node 20+ bootstraps through the package helper.Proof must instantiate real gameplay and assert meaningful state transitions. On success it writes `{"passed":true,"checks":[...]}` to `HARNESS_BUILD_DIR/proof.json`; on failure exit nonzero. A missing receipt is failure even if Godot exits zero. Keep assertions relevant when replacing the starter. A standalone proof can write to Godot's user data directory when that environment variable is unset.Use `_physics_process` for movement and keep per-frame work bounded. Preserve keyboard, touch/click, pause and restart when useful for the requested game. The custom `web/shell.html` exposes actual game state through JavaScriptBridge, not a parallel simulated game.The build verdict means native assertions and export passed. Verify the exported game in the actual shared viewer before claiming browser readiness. A browser playthrough must exercise game results, not just see a canvas.The viewer requires a single-threaded export (Godot 4.3+), Compatibility renderer, no service worker or persistent browser storage. Keep the editor and templates version-matched. Only Godot 4.4's known optional PWA callback warning is downgraded in the opaque sandbox; other engine errors remain visible.Optional interaction/performance probe:```shHARNESS_WORKSPACE="$PWD" node "$GODOT_SKILLS/godot/scripts/perf.mjs" build/web/index.html```Uses shared Web Viewer + Playwright and the assertions in `proof.json`. It reports actual interaction frame timing; inspect the recorded renderer and do not extrapolate hardware performance to other devices.

Frequently asked questions

Godot