Guide · Agent skill

How to use the Godot Engine CLI agent skill (cli-anything-godot)

Updated 2026-10-29 · written with AI from the project's own documentation and checked against our catalogue data

This guide explains how to install and use the cli-anything-godot skill, which lets an AI agent drive the Godot 4 game engine through a command-line tool instead of the visual editor. It is written for readers who have not used agent skills before. By the end you will know what the skill lets the agent do, how to install it, how to ask for work in plain language, and what safety limits to keep in mind.

Godot Engine CLIHKUDS/CLI-Anything · Apache-2.0 Download the skill

Quick start

1Confirm Godot 4 is available. Install Godot 4.x and put it on your PATH, or set the GODOT_BIN environment variable to its location.
2Install the Python package. Run the pip install command for cli-anything-godot from the HKUDS CLI-Anything GitHub repository.
3Download and unzip the skill. Download the ZIP from this page and unzip it into ~/.claude/skills/ or a project's .claude/skills/ folder.
4Or upload it in the Claude apps. In the Claude apps, go to Settings → Capabilities → Skills and upload the ZIP.
5Check the engine. Run cli-anything-godot --json engine status to confirm the binary is found.
6Ask for a task in plain language. Describe the project, scene or export you want and name the Godot project path.

What an agent skill is and what this one does

An agent skill is a folder with a SKILL.md file that tells an AI agent how to perform a specific kind of task. This skill, named cli-anything-godot, teaches the agent to use a command-line interface for the Godot game engine.

Once installed, the agent can create Godot projects and scenes, add nodes to scenes, list scripts and resources, read scene structure, validate GDScript syntax, run GDScript files or inline code against a project, and list or build export presets. The source describes it as aimed at automating repetitive game-project tasks.

Install the skill (ZIP download or Claude apps)

Download the skill ZIP from this page and unzip it. Put the resulting folder in one of two places: ~/.claude/skills/ for your personal use across projects, or a project's .claude/skills/ folder if you want it limited to one project.

If you use the Claude apps instead, upload the ZIP under Settings → Capabilities → Skills.

The skill also depends on the command-line package itself. The source gives this install command for the cli-anything-godot package, which is pulled from the GitHub repository:

pip install git+https://github.com/HKUDS/CLI-Anything.git#subdirectory=godot/agent-harness

Check the requirements first

The commands depend on the Godot binary. You need Godot 4.x available on your PATH, or set the GODOT_BIN environment variable to point to it. You also need Python with pip to install the package.

Without Godot 4 installed, the agent will only get errors. Run the engine status check below to confirm the setup before asking for real work.

cli-anything-godot --json engine status

Trigger the skill with natural requests

You do not need to type the commands yourself. Describe the outcome in plain language, mentioning Godot and your project, and the agent should pick up the skill and use the matching commands. Be specific about the scene path, node names and preset names, since these map directly to command arguments.

Examples of requests that fit the skill:

Create a new Godot project called My Game in ./games and tell me its main scene.
List every scene and script in ./my-game as JSON.
Add a CharacterBody3D named Player under the root of scenes/Level1.tscn.
Check scripts/player.gd for GDScript syntax errors.
Export every preset in ./my-game and tell me where the files went.

Common commands the agent will use

These are the main commands from the source. The agent runs them for you, but reading them helps you check what it is about to do.

Project commands list and create projects. Scene commands create scenes and add nodes. Script commands run or validate GDScript. Export commands list presets and build them. Add --json to any command for structured output.

project info, project scenes, project scripts, project resources
scene create, scene read, scene add-node
script run, script inline, script validate
export presets, export build (optionally with --preset and --output)
engine status, engine version

cli-anything-godot -p ./my-game export build --preset "Windows Desktop" --output build/game.exe

Safety: scripts and network

This skill runs scripts and uses the network, so treat it with care. The script run and inline commands execute GDScript inside your project. That code can change files or run arbitrary logic, so only use them on projects you trust.

The install step downloads from GitHub, so it needs network access. Review the SKILL.md and the code of anything you install, and keep backups or version control in place before letting an agent make batch changes or exports.

Tips for reliable results

Ask for JSON output when you want the agent to reason over results, since the source describes it as suitable for agent consumption. Use the -p flag or name the project path explicitly so the agent targets the right folder.

For repeated work, the source also mentions an interactive session mode, which opens a REPL on a project for ongoing commands.

Confirm engine status before any batch work.
Use exact preset names such as "Windows Desktop" as they appear in export presets output.
Commit your project to version control before scripted changes.

cli-anything-godot -p ./my-game session

What people use it for

Scaffold a new Godot project and add a starting scene with a chosen root node type.
Audit a project by listing its scenes, scripts and resources as JSON.
Validate GDScript files for syntax errors before a build.
Build several export presets in one run for multiple platforms.
Run a GDScript tool file, such as one that builds a navigation mesh, against a project.

Frequently asked questions

How do I install the cli-anything-godot skill?

Download the skill ZIP from this page and unzip it into ~/.claude/skills/ or a project's .claude/skills/ folder. In the Claude apps, you can instead upload it under Settings → Capabilities → Skills. You also need the Python package, installed with pip from the HKUDS CLI-Anything GitHub repository.

What do I need to run the Godot CLI skill?

You need Godot 4.x available on your PATH or set through the GODOT_BIN environment variable, plus Python with pip to install the package. The commands depend on the Godot binary, so they will fail without it.

Is the Godot CLI agent skill free?

The source does not state pricing or licence terms beyond the listed licence for this item, which is Apache-2.0. Check the repository for the full licence text before using it.

What is the difference between script run and script inline?

script run executes a GDScript file that must extend SceneTree, while script inline runs a line of GDScript you pass directly. Both execute code inside your project, so only use them on projects you trust.

Why does the skill return errors when I use it?

The most likely cause is that Godot 4.x is not found. Run cli-anything-godot --json engine status to check the binary path, then confirm Godot is on PATH or GODOT_BIN points to it.

Can the agent export builds for several platforms?

Yes. Export build with no preset exports all configured presets, and you can name a single preset with --preset and set an output path with --output.

New agent skills, repos and AI tools — every week

The best new skills and open-source projects, the fastest-growing repos, and one free prompt. Five minutes to read. Unsubscribe anytime.

Our verdict

This skill suits Godot 4 developers and build engineers who want an agent to handle scene setup, JSON project queries and batch exports from the command line. It is a poor fit if you do not have Godot 4 installed, or if you work on projects you do not trust, because script commands execute GDScript that can change files.

Download the skill