How do I install the Live Editor skill?

Run npx skillmds@latest add hashgraph-online/live-editor in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Live Editor safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: makes network calls, reads secrets. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Live Editor?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Live Editor free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Live Editor?

hashgraph-online (@hashgraph-online) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Live Editor by hashgraph-online — Agent Skill

Name: Live Editor
Rating: 4.666666666666667 (3 reviews)
Author: hashgraph-online

Live Editor

Use this skill whenever a request involves a Godot project's live editor or running game: inspect scene, node, or UI state; change scenes, nodes, properties, or signals; run a scene; or prove gameplay or UI behavior. Prefer the `hera` CLI over guessing from project files or stale editor state.

File contents

Hera live Godot workflow

Use Hera only with a running Godot editor that has the Hera Agent Godot addon enabled (verified on Godot 4.2–4.7; 4.7 recommended). CLI output is the source of truth for live editor and runtime state.

Start with the live editor

Run hera status. If no live editor is found, ask the user to enable the addon under Project Settings → Plugins; do not infer editor state from files.
If multiple editors are found, run hera instances. Pass hera --instance <pid> for any mutation.
Before UI work, run hera guidance ui and follow its returned mode.

Keep reads small and writes safe

Default output is compact. Prefer hera --ids scene tree, selected node get --prop/--props, scoped game ui tree, and game qa discover before full dumps.
Use node add/set/remove and signal connect/disconnect for normal editor changes; Godot records those as undoable steps. Prefer them to eval, whose expression can have side effects and is not undoable.
Scene, resource, script, import, and project-setting commands persist to disk. game node set/call, game click, and game input affect only the running game and disappear when it stops.
Keep one editor per project. After direct .tscn edits, stop the game, hera scene reload, then save through the editor.

Prove the result

After a change, read the changed property or node tree. After a run, check hera output --type error or hera diagnostics.
For visual/UI work, use game ui tree, semantic game click, and hera screenshot --runtime --analyze. For prompt requirements, prefer a game qa --file scenario with requirements and per-step covers.
After editing GDScript, run that project's headless --check-only gate when available, then re-check diagnostics.

Hera sends any configured HERA_AGENT_GODOT_TOKEN automatically. Never print or place that token in project files. For the complete command reference, see the Hera repository's docs/COMMANDS.md.

Source: hashgraph-online/awesome-codex-plugins → plugins/NotNull92/hera-agent-godot/skills/live-editor/SKILL.md

---name: live-editordescription: Use this skill whenever a request involves a Godot project's live editor or running game: inspect scene, node, or UI state; change scenes, nodes, properties, or signals; run a scene; or prove gameplay or UI behavior. Prefer the `hera` CLI over guessing from project files or stale editor state.--- # Hera live Godot workflow Use Hera only with a running Godot editor that has the Hera Agent Godot addon enabled (verified on Godot 4.2–4.7; 4.7 recommended). CLI output is the source of truth for live editor and runtime state. ## Start with the live editor 1. Run `hera status`. If no live editor is found, ask the user to enable the addon under **Project Settings → Plugins**; do not infer editor state from files. 2. If multiple editors are found, run `hera instances`. Pass `hera --instance <pid>` for any mutation. 3. Before UI work, run `hera guidance ui` and follow its returned mode. ## Keep reads small and writes safe - Default output is compact. Prefer `hera --ids scene tree`, selected `node get --prop/--props`, scoped `game ui tree`, and `game qa discover` before full dumps. - Use `node add/set/remove` and `signal connect/disconnect` for normal editor changes; Godot records those as undoable steps. Prefer them to `eval`, whose expression can have side effects and is not undoable. - Scene, resource, script, import, and project-setting commands persist to disk. `game node set/call`, `game click`, and `game input` affect only the running game and disappear when it stops. - Keep one editor per project. After direct `.tscn` edits, stop the game, `hera scene reload`, then save through the editor. ## Prove the result - After a change, read the changed property or node tree. After a run, check `hera output --type error` or `hera diagnostics`. - For visual/UI work, use `game ui tree`, semantic `game click`, and `hera screenshot --runtime --analyze`. For prompt requirements, prefer a `game qa --file` scenario with `requirements` and per-step `covers`. - After editing GDScript, run that project's headless `--check-only` gate when available, then re-check diagnostics. Hera sends any configured `HERA_AGENT_GODOT_TOKEN` automatically. Never print or place that token in project files. For the complete command reference, see the Hera repository's `docs/COMMANDS.md`. --- **Source:** [`hashgraph-online/awesome-codex-plugins`](https://github.com/hashgraph-online/awesome-codex-plugins) → `plugins/NotNull92/hera-agent-godot/skills/live-editor/SKILL.md`

Frequently asked questions