[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MD134147X6YV4Q4MFWPQA3":3,"skill-same:01M6MD134147X6YV4Q4MFWPQA3":70},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":41,"linkOnly":42,"markdownContent":43,"markdownBody":44,"frontMatter":45,"refName":46,"commitSha":47,"skillDirectory":48,"forksCount":49,"repositoryHtmlUrl":50,"repositoryHomepageUrl":51,"ownerHtmlUrl":52,"ownerBlogUrl":53,"ownerDescription":54,"updatedAt":55,"install":56,"resources":69},"01M6MD134147X6YV4Q4MFWPQA3","live-editor",null,"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-godot` CLI over guessing from project files or stale editor state.","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1575,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FNotNull92\u002Fhera-agent-godot\u002Fskills\u002Flive-editor\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40],"editor","live editor","live","running","cli","prove","request","inspect","inspect scene","project","signals","scenes","files","Nodes","gameplay","use","node","game","ui","state","run","change","2026-11-10 10:12:30",false,"---\nname: live-editor\ndescription: \"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-godot` CLI over guessing from project files or stale editor state.\"\n---\n\n# Hera live Godot workflow\n\nUse Hera only with a running Godot editor that has the Hera Agent Godot addon\nenabled (verified on Godot 4.2–4.7; 4.7 recommended). CLI output is the source\nof truth for live editor and runtime state.\n\n## Start with the live editor\n\n1. Run `hera-godot status`. If no live editor is found, ask the user to enable the\n   addon under **Project Settings → Plugins**; do not infer editor state from\n   files.\n2. Reads select the first live editor. Mutations reject multiple editors with\n   their PID list; use `instances` only to choose a PID, then pass `--instance \u003Cpid>`.\n3. Before UI work, read `game_feel_ui_mode` from `status`; use `guidance ui`\n   when the checklist text is needed.\n\nEditor and game PIDs are separate. Use global `--instance \u003Ceditor-pid>` for the\neditor, then `game --pid \u003Cgame-pid> ...` to select a fresh entry from\n`game instances`, including externally launched games. Keep the game PID on QA\ncommands and scenarios. Never fall back to a different runtime when it expires.\n`--instance`\u002F`--pid` do not isolate `user:\u002F\u002F`; if `shared_user_data` is set,\nsplit user data directories before parallel QA. Runtime screenshot sizes are\nthe live viewport; do not assume the project resolution or upscale. If `hera-godot\ninstances` shows `stale`, the editor process may still be running with an\nexpired heartbeat — that is not the same as no editor.\n\nThe 2.1 CLI shape omits redundant counts\u002Fnames, false `truncated`, and status\nsession\u002Fpath fields. Missing log `source` means file. Pretty\u002Fbatch share these rules;\nexplicit `--fields` stay. See `docs\u002FMIGRATING_TO_V2_1.md`.\n\nValue flags accept `--flag=value`; `--flag=` equals `--flag \"\"`, subject to\nthe same validation.\n\n## Keep reads small and writes safe\n\n- Default output is compact. Prefer `hera-godot --ids scene tree`, selected\n  `node get --prop\u002F--props\u002F--changed`, `scene tree [path] --depth N --type Class\n  --props a,b`, `signal list \u003Cpath> --connected`, scoped `game ui tree`, and `game qa discover`\n  before full dumps.\n- Use `node add\u002Fset\u002Fremove` and `signal connect\u002Fdisconnect` for normal editor\n  changes; Godot records those as undoable steps. Prefer them to `eval`, whose\n  expression can have side effects and is not undoable.\n- Scene, resource, script, import, and project-setting commands persist to\n  disk. `game node set\u002Fcall`, `game click`, and `game input` affect only the\n  running game and disappear when it stops.\n- Keep one editor per project. After direct `.tscn` edits, stop the game,\n  `hera-godot scene reload`, then save through the editor.\n- The Hera runtime autoload is excluded from exports and restored afterward;\n  do not persist a separate production autoload for the inspector.\n\n## Choose the script language\n\nUse `.gd` for GDScript or `.cs` for C#; optional `--lang gdscript|csharp` on\n`script create` must match the extension. Do not infer a default from the\nproject. Before C# create\u002Fopen\u002Fattach, check `status.csharp_supported`; it reports\nGodot .NET capability, not SDK installation. C# templates use a filename-matching\npartial class. Build and reload the assembly before attachment; Hera does not\nbuild or generate solution files. C# inspect\u002Fcurrent reads loaded-assembly\nmetadata, which can be unavailable or stale. `script current` cannot observe\nexternal IDE focus. `eval` defaults to C# through the helper host; use\n`--lang gdscript` for a GDScript expression.\n\nRuntime QA discovery accepts `qa_*` and `Qa` followed by an uppercase letter,\nsuch as `QaReady`; preserve exact case when calling C# methods. See the Hera\nrepository's `docs\u002FCSHARP_SUPPORT.md` for setup and limitations.\n\n## Prove the result\n\n- After `node set`, check the response's re-read `value`; use `node get` for\n  other properties. Use repeatable `--set prop=value` on `node add` or\n  `node instance`; check returned `values`. Creation and properties share one\n  undo action. Without `--set`, confirm with `hera-godot --ids scene tree`.\n  After a run, check `diagnostics` first; use `output --type error` for raw lines.\n- For eventual runtime state, use `game assert ... --within-ms N` (1–30,000).\n  QA assertion steps accept `within_ms`. Read `waited_ms`; timeouts return\n  `timed_out: true`, the last available `actual`, and exit 1.\n- For visual\u002FUI work, use `game ui tree`, semantic `game click`, and\n  `hera-godot screenshot --runtime --analyze`. For prompt requirements, prefer a\n  `game qa --file` scenario with `requirements` and per-step `covers`.\n- After editing GDScript, run `script validate res:\u002F\u002Ffile.gd`; fall back to\n  the project's headless `--check-only` gate, then re-check diagnostics.\n  After C# changes, build the .NET project,\n  reload the assembly, and verify runtime behavior; GDScript `--check-only` does\n  not compile C#.\n\nHera sends any configured `HERA_AGENT_GODOT_TOKEN` automatically. Never print\nor place that token in project files. For the complete command reference, see\nthe Hera repository's `docs\u002FCOMMANDS.md`.\n","# Hera live Godot workflow\n\nUse Hera only with a running Godot editor that has the Hera Agent Godot addon\nenabled (verified on Godot 4.2–4.7; 4.7 recommended). CLI output is the source\nof truth for live editor and runtime state.\n\n## Start with the live editor\n\n1. Run `hera-godot status`. If no live editor is found, ask the user to enable the\n   addon under **Project Settings → Plugins**; do not infer editor state from\n   files.\n2. Reads select the first live editor. Mutations reject multiple editors with\n   their PID list; use `instances` only to choose a PID, then pass `--instance \u003Cpid>`.\n3. Before UI work, read `game_feel_ui_mode` from `status`; use `guidance ui`\n   when the checklist text is needed.\n\nEditor and game PIDs are separate. Use global `--instance \u003Ceditor-pid>` for the\neditor, then `game --pid \u003Cgame-pid> ...` to select a fresh entry from\n`game instances`, including externally launched games. Keep the game PID on QA\ncommands and scenarios. Never fall back to a different runtime when it expires.\n`--instance`\u002F`--pid` do not isolate `user:\u002F\u002F`; if `shared_user_data` is set,\nsplit user data directories before parallel QA. Runtime screenshot sizes are\nthe live viewport; do not assume the project resolution or upscale. If `hera-godot\ninstances` shows `stale`, the editor process may still be running with an\nexpired heartbeat — that is not the same as no editor.\n\nThe 2.1 CLI shape omits redundant counts\u002Fnames, false `truncated`, and status\nsession\u002Fpath fields. Missing log `source` means file. Pretty\u002Fbatch share these rules;\nexplicit `--fields` stay. See `docs\u002FMIGRATING_TO_V2_1.md`.\n\nValue flags accept `--flag=value`; `--flag=` equals `--flag \"\"`, subject to\nthe same validation.\n\n## Keep reads small and writes safe\n\n- Default output is compact. Prefer `hera-godot --ids scene tree`, selected\n  `node get --prop\u002F--props\u002F--changed`, `scene tree [path] --depth N --type Class\n  --props a,b`, `signal list \u003Cpath> --connected`, scoped `game ui tree`, and `game qa discover`\n  before full dumps.\n- Use `node add\u002Fset\u002Fremove` and `signal connect\u002Fdisconnect` for normal editor\n  changes; Godot records those as undoable steps. Prefer them to `eval`, whose\n  expression can have side effects and is not undoable.\n- Scene, resource, script, import, and project-setting commands persist to\n  disk. `game node set\u002Fcall`, `game click`, and `game input` affect only the\n  running game and disappear when it stops.\n- Keep one editor per project. After direct `.tscn` edits, stop the game,\n  `hera-godot scene reload`, then save through the editor.\n- The Hera runtime autoload is excluded from exports and restored afterward;\n  do not persist a separate production autoload for the inspector.\n\n## Choose the script language\n\nUse `.gd` for GDScript or `.cs` for C#; optional `--lang gdscript|csharp` on\n`script create` must match the extension. Do not infer a default from the\nproject. Before C# create\u002Fopen\u002Fattach, check `status.csharp_supported`; it reports\nGodot .NET capability, not SDK installation. C# templates use a filename-matching\npartial class. Build and reload the assembly before attachment; Hera does not\nbuild or generate solution files. C# inspect\u002Fcurrent reads loaded-assembly\nmetadata, which can be unavailable or stale. `script current` cannot observe\nexternal IDE focus. `eval` defaults to C# through the helper host; use\n`--lang gdscript` for a GDScript expression.\n\nRuntime QA discovery accepts `qa_*` and `Qa` followed by an uppercase letter,\nsuch as `QaReady`; preserve exact case when calling C# methods. See the Hera\nrepository's `docs\u002FCSHARP_SUPPORT.md` for setup and limitations.\n\n## Prove the result\n\n- After `node set`, check the response's re-read `value`; use `node get` for\n  other properties. Use repeatable `--set prop=value` on `node add` or\n  `node instance`; check returned `values`. Creation and properties share one\n  undo action. Without `--set`, confirm with `hera-godot --ids scene tree`.\n  After a run, check `diagnostics` first; use `output --type error` for raw lines.\n- For eventual runtime state, use `game assert ... --within-ms N` (1–30,000).\n  QA assertion steps accept `within_ms`. Read `waited_ms`; timeouts return\n  `timed_out: true`, the last available `actual`, and exit 1.\n- For visual\u002FUI work, use `game ui tree`, semantic `game click`, and\n  `hera-godot screenshot --runtime --analyze`. For prompt requirements, prefer a\n  `game qa --file` scenario with `requirements` and per-step `covers`.\n- After editing GDScript, run `script validate res:\u002F\u002Ffile.gd`; fall back to\n  the project's headless `--check-only` gate, then re-check diagnostics.\n  After C# changes, build the .NET project,\n  reload the assembly, and verify runtime behavior; GDScript `--check-only` does\n  not compile C#.\n\nHera sends any configured `HERA_AGENT_GODOT_TOKEN` automatically. Never print\nor place that token in project files. For the complete command reference, see\nthe Hera repository's `docs\u002FCOMMANDS.md`.\n",{"name":5,"description":7},"main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002FNotNull92\u002Fhera-agent-godot\u002Fskills\u002Flive-editor",491,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins","https:\u002F\u002Fhol.org\u002Fplugins\u002Fbest-codex-plugins","https:\u002F\u002Fgithub.com\u002Fhashgraph-online","https:\u002F\u002Fhol.org","Open-source standards and developer tools for interoperable AI agents: discovery, identity, communication, payments, privacy and security.","2026-11-14 14:06:13",{"source":8,"skillName":5,"commands":57,"prompt":67,"zipAvailable":68},[58,61,64],{"tool":59,"command":60},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill live-editor",{"tool":62,"command":63},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill live-editor",{"tool":65,"command":66},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill live-editor","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FNotNull92\u002Fhera-agent-godot\u002Fskills\u002Flive-editor\u002FSKILL.md",true,[],[71,81,89,97,105,113],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":75,"licenseFileUrl":76,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":80},"01M7DV332YQMGD8WTRJ9DZQXTB","worktable-review-with-annotations","Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.","MIT","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":75,"licenseFileUrl":85,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":80},"01M7DV2YGHCZVBEB1AHYB6CGHE","worktable-find-and-synthesize-context","Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":75,"licenseFileUrl":93,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":80},"01M7DV2TQN1H11ME2SAF9MXN7V","worktable-create-or-update-docs","Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FSKILL.md",[],[],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":75,"licenseFileUrl":101,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":80},"01M7DV2NE452NEA8TXATKSNAJH","worktable-create-or-manage-records","Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FSKILL.md",[],[],{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":75,"licenseFileUrl":109,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":80},"01M7DV2HENRBR2KSCVM064WH0Y","worktable-create-or-manage-interactive-html","Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FSKILL.md",[],[],{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":75,"licenseFileUrl":117,"sourceHtmlUrl":118,"categories":119,"keywords":120,"publishedAt":80},"01M7DV2CADR5R7RQFFYPNAGR9Y","worktable-collaborate-threads","Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FSKILL.md",[],[]]