
Cli Anything Godot
- 394 installs
- 46.6k repo stars
- Updated August 3, 2026
- hkuds/cli-anything
cli-anything-godot is an agent skill that exposes a Python CLI for Godot 4.x project management, scene exports, and headless tests for developers who automate game build steps or content pipelines from the terminal.
About
cli-anything-godot is an agent skill from hkuds/cli-anything packaging an agent-native CLI for Godot 4.x engines. Install via pip from the CLI-Anything godot agent-harness subdirectory, require Godot 4.x on PATH or GODOT_BIN, then run commands like `cli-anything-godot project create`, `project info`, scene management, exports, and GDScript execution with optional `--json` output. The skill targets automated export pipelines, headless test runs, and scene inspection when agents orchestrate game repos without opening the editor GUI. Use it when CI or coding agents must create Godot projects, query main scenes and features, or drive repeatable build and test steps from shell scripts.
- Godot headless export
- Scene and project CLI ops
- Game build automation
- cli-anything command recipes
- Engine workflow from terminal
Cli Anything Godot by the numbers
- 394 all-time installs (skills.sh)
- +19 installs in the week ending Aug 2, 2026 (Skillselion tracking)
- Ranked #59 of 247 Game Development skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/hkuds/cli-anything --skill cli-anything-godotAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 394 |
|---|---|
| repo stars | ★ 46.6k |
| Last updated | August 3, 2026 |
| Repository | hkuds/cli-anything ↗ |
How do you automate Godot builds from CLI?
Export Godot projects, run headless tests, and inspect scenes via CLI when agents automate game build steps or content pipelines.
Who is it for?
cli-anything-godot fits game developers and build engineers who need agent- or CI-driven Godot 4.x exports, scene queries, and headless tests without manual editor clicks.
Skip if: Skip cli-anything-godot for Unity or Unreal pipelines, Godot 3.x projects, or purely visual editor workflows with no automation requirement.
When should I use this skill?
Trigger cli-anything-godot when automating Godot project creation, exports, scene inspection, or headless test runs from agents or shell scripts.
What you get
Godot project scaffolding, JSON project metadata, exported game builds, scene inspection output, and headless test execution logs.
- Exported Godot builds
- JSON project info output
- Headless test logs
By the numbers
- Requires Godot 4.x engine
- Install path: CLI-Anything godot/agent-harness via pip
Files
Godot Engine CLI
Agent-native CLI for the Godot game engine. Manage projects, scenes, exports, and GDScript execution from the command line.
Installation
pip install git+https://github.com/HKUDS/CLI-Anything.git#subdirectory=godot/agent-harnessRequirements
- Godot 4.x on PATH (or set GODOT_BIN env var)
Commands
Project Management
# Create a new Godot project
cli-anything-godot project create <path> [--name "My Game"]
# Get project info (name, features, main scene)
cli-anything-godot --json -p <project> project info
# List all scenes
cli-anything-godot --json -p <project> project scenes
# List all scripts
cli-anything-godot --json -p <project> project scripts
# List all resources
cli-anything-godot --json -p <project> project resources
# Re-import project resources
cli-anything-godot -p <project> project reimportScene Operations
# Create a new scene with root node type
cli-anything-godot -p <project> scene create scenes/Level1.tscn --root-type Node3D
# Read scene structure (nodes, resources, connections)
cli-anything-godot --json -p <project> scene read scenes/Level1.tscn
# Add a child node to a scene
cli-anything-godot -p <project> scene add-node scenes/Level1.tscn --name Player --type CharacterBody3D --parent .GDScript Execution
# Run a GDScript file (must extend SceneTree)
cli-anything-godot -p <project> script run tools/build_navmesh.gd
# Run inline GDScript code
cli-anything-godot -p <project> script inline 'print(ProjectSettings.get_setting("application/config/name"))'
# Validate GDScript syntax
cli-anything-godot -p <project> script validate scripts/player.gdExport
# List configured export presets
cli-anything-godot --json -p <project> export presets
# Export all presets
cli-anything-godot -p <project> export build
# Export a specific preset
cli-anything-godot -p <project> export build --preset "Windows Desktop" --output build/game.exeEngine
# Check Godot availability and binary path
cli-anything-godot --json engine status
# Get engine version
cli-anything-godot engine versionJSON Mode
Add --json flag to any command for structured JSON output suitable for agent consumption:
cli-anything-godot --json -p ./my-game project infoInteractive REPL
cli-anything-godot -p ./my-game sessionRelated skills
How it compares
Pick cli-anything-godot over generic shell scripts when agents need structured JSON Godot project control through a dedicated harness CLI.
FAQ
What Godot version does cli-anything-godot require?
cli-anything-godot requires Godot 4.x available on PATH or referenced through the GODOT_BIN environment variable before running project, export, or script commands.
How is cli-anything-godot installed?
cli-anything-godot installs with pip from the HKUDS CLI-Anything repository godot agent-harness subdirectory, then exposes the cli-anything-godot command for project and export automation.