Individual skill
scenario-godot-expert
Use when an agent drives Godot 4.7 on macOS or Windows for any task: headless --script jobs, --import, --check-only, command-line exports, GUT tests, windowed screenshots, the headless editor (-e) or an MCP server into a running editor; when a run hangs or fails silently, a capture is black, Godot 3 code breaks in 4.x, 'Identifier not found', export templates are missing; or when a Godot brief (2D, 3D, shaders, VFX, UI, multiplayer, export) must go to the right scenario-godot-* specialist.
skills/game-engines/godot/scenario-godot-expert/SKILL.md
Source commit f29bf06ab89088695ed3431ac99d20a090441a2f
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 9, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 3,658
- Repository last updated
- Nov 9, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent-skills Repository topic
- blender Repository topic
- claude-code Repository topic
- claude-skills Repository topic
- codex Repository topic
- game-assets Repository topic
- game-development Repository topic
- generative-ai Repository topic
- image-generation Repository topic
- mcp Repository topic
- design Derived category
- design-interface Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 23,944 bytesSKILL.mdcore · 23,944 bytesSKILL.mdcore · 23,944 bytesreferences/critique.mddoc · 7,063 bytesreferences/expert-notes.mddoc · 20,782 bytesreferences/gui-paths.mddoc · 8,737 bytesreferences/procedures.mddoc · 45,381 bytesreferences/sources.mddoc · 12,534 bytesreferences/traps.mddoc · 5,473 bytesscripts/agentkit/agent_audit.gdasset · 14,409 bytesscripts/agentkit/agent_build.gdasset · 8,762 bytesscripts/agentkit/agent_capture.gdasset · 16,882 bytesscripts/agentkit/agent_job.gdasset · 13,715 bytesscripts/agentkit/agent_profile.gdasset · 7,241 bytesscripts/gd_env.pyruns · 22,478 bytesscripts/gd_live.pyruns · 9,439 bytesscripts/gd_review.pyruns · 13,825 bytesscripts/gd_run.pyruns · 38,977 bytesscripts/gd_stat.pyruns · 12,622 bytes
Read excerpt
# Godot expert (technical director and agent protocol)
Target: Godot 4.7.2.stable (standard build, no C#), macOS Apple Silicon with Metal by default, or
Windows with D3D12.
Expert Godot work is a loop run against evidence: set the budget, build one stage, measure it, look
at it, fix it, advance. An agent without a mouse gets there by picking the right channel, passing
only on a machine-readable result, and never trusting one signal alone. This skill is that protocol,
the shared toolkit every scenario-godot-* skill calls ([`scripts/`](scripts/)), and the map of the
team. If a sibling skill named here is missing from your available skills, load it with `skill_get`
(Scenario MCP) or ask the user to install it (https://github.com/scenario-labs/skills#install);
unattended, proceed from tool schemas and flag the gap.
**Status (2026-10-02):** every toolkit function below ran in Godot 4.7.2 here (23 live tests, 17