Godot Skill

Control Godot Editor via OpenClaw Godot Plugin. Use for Godot game development tasks including scene management, node manipulation, input simulation, debugging, and editor control. Triggers on Godot-related requests like inspecting scenes, creating nodes, taking screenshots, testing gameplay, or controlling the editor.

This skill is internally consistent with its stated purpose: it installs a local gateway extension and exposes a set of Godot-focused tools to the OpenClaw agent. Before installing: 1) Back up any active Godot projects (the README already advises this). 2) Confirm you trust the skill source (it references a GitHub repo but the package metadata shows no official homepage). 3) Be aware the extension exposes local HTTP endpoints under /godot/ and sets CORS to '*'; ensure your OpenClaw gateway is bound to localhost or protected by your firewall so remote sites cannot call these endpoints. 4) If you do not want the AI to autonomously control your editor, set disableModelInvocation/auto-invoke to true or require explicit user approval for tool calls. 5) Review the extension code yourself (index.ts) for any network calls or logging to external hosts before use; the provided code appears to keep traffic local and queue commands through a session mechanism, but you should verify the gateway binding and runtime behavior in your environment.

Type: OpenClaw Skill Name: openclaw-godot-skill Version: 1.2.7 The skill is classified as suspicious due to its broad capabilities that could be abused, specifically the `godot_execute` tool in `extension/index.ts` which allows the AI agent to read script content (`script.read`), list resources (`resource.list`), and simulate input or modify the Godot project. While these actions align with the stated purpose of controlling the Godot Editor, they represent significant file access and system control risks if the AI agent is compromised via prompt injection. Additionally, the local HTTP server in `extension/index.ts` uses `Access-Control-Allow-Origin: *`, which is a permissive CORS policy that could be exploited by other local processes, although the primary intent is for local Godot Editor communication. There is no clear evidence of intentional malicious behavior like data exfiltration to external endpoints or persistence mechanisms.