hastur-operation-plugin: Skill for Claude Code

Godot Remote Executor

This skill enables you to execute arbitrary GDScript code on a running Godot editor or game runtime instance through the Hastur broker-server. The broker-server acts as a bridge: you send HTTP requests to it, and it forwards the code to a connected Hastur Executor (editor plugin or game runtime) via TCP.

Executors have a type field: "editor" for the editor plugin, "game" for the GameExecutor autoload running in the game process. Use type: "game" to target the live game runtime — useful for inspecting runtime state, scene tree, physics, FPS, input, and variables during gameplay.

Prerequisites

Before you begin, you need two things from the user:

1. Auth token — The broker-server requires a Bearer token for authentication. Ask the user for it if not provided. It was printed to stdout when the broker-server started.
2. Base URL — Defaults to http://localhost:5302. The user may specify a different host/port.

Store these for the duration of the conversation:

• HASTUR_AUTH_TOKEN — the Bearer token
• HASTUR_BASE_URL — defaults to http://localhost:5302

Step 0: Read GDScript Syntax Reference (Critical)

Before writing any GDScript code, read the GDScript syntax reference to avoid compilation errors. GDScript has Python-like indentation-based syntax but significant differences in typing, built-in types, and conventions.

Read this file first:

• references/gdscript-syntax/gdscript_basics.rst.txt — The core language reference (~2900 lines). Covers syntax, types, control flow, functions, classes, signals, exports, and all language constructs.

This is the single most important thing you can do to reduce errors. GDScript has many subtle differences from Python:

• Uses := for type inference (not :)
• var x: int for typed variables
• func not def
• Indentation matters (tabs, not spaces)
• @onready, @export, @tool annotations
• Built-in types: Vector2, Vector3, Color, Dictionary, Array, etc.
• String formatting with % operator or format() method
• match instead of switch
• No list comprehensions (use Array.map() / Array.filter())
• for x in range(n) or for x in array
• Signals declared with signal keyword
• preload() and load() for resources