[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MD18REWMQ95JR707YAD3XD":3,"skill-same:01M6MD18REWMQ95JR707YAD3XD":88},{"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":28,"publishedAt":49,"linkOnly":50,"markdownContent":51,"markdownBody":52,"frontMatter":53,"refName":54,"commitSha":55,"skillDirectory":56,"forksCount":57,"repositoryHtmlUrl":58,"repositoryHomepageUrl":59,"ownerHtmlUrl":60,"ownerBlogUrl":61,"ownerDescription":62,"updatedAt":63,"install":64,"resources":77},"01M6MD18REWMQ95JR707YAD3XD","ui-theme-qa",null,"Use this skill to find and fix undisciplined Control-node UI in a Godot project — spacing that follows no ladder, font sizes with no modular scale, near-duplicate colours, and text that fails WCAG contrast — by measuring the live editor with the `hera-godot` CLI and snapping theme tokens to a reference corpus. It also reports (without changing) inert container wrappers and decorative nodes. Triggers: \"clean up the UI spacing\u002Ftype\u002Fcontrast\", \"the UI values look arbitrary\", \"tidy the Godot UI\", \"check UI contrast\", or any request to mechanically remove statistical UI-design defects without a redesign. Reductive only; edits per-node theme overrides (undoable), never copy or layout content.","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\u002Fui-theme-qa\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48],"ui theme qa","qa","ui","theme","only","godot ui","near","layout","project","clean","reports","up","design","never","remove","fix","text","tidy","modular","cli","2026-11-10 10:12:30",false,"---\nname: ui-theme-qa\ndescription: \"Use this skill to find and fix undisciplined Control-node UI in a Godot project — spacing that follows no ladder, font sizes with no modular scale, near-duplicate colours, and text that fails WCAG contrast — by measuring the live editor with the `hera-godot` CLI and snapping theme tokens to a reference corpus. It also reports (without changing) inert container wrappers and decorative nodes. Triggers: \\\"clean up the UI spacing\u002Ftype\u002Fcontrast\\\", \\\"the UI values look arbitrary\\\", \\\"tidy the Godot UI\\\", \\\"check UI contrast\\\", or any request to mechanically remove statistical UI-design defects without a redesign. Reductive only; edits per-node theme overrides (undoable), never copy or layout content.\"\n---\n\n\u003C!-- markdownlint-disable MD013 -->\n\n# UI Theme QA (Godot, reductive)\n\nMechanically remove statistical design defects from a live Godot editor, over\n`Control` nodes. It does not redesign: it snaps theme tokens to a reference\ncorpus and never touches copy, information order, or layout structure.\n\nSix areas, split by what they may do:\n\n| | areas | effect |\n| --- | --- | --- |\n| **enforcing** | `spacing` · `type-scale` · `color` · `contrast` | set `theme_override_*` (undoable) |\n| **report-only** | `containers` · `decoration` | proposals in the report; **no mutation** |\n\nThe report-only pair would have to delete or re-parent nodes, which cannot be\ndecided mechanically — a node that looks decorative may be a divider, and\nflattening a wrapper breaks the `$Path\u002FTo\u002FNode` references scripts rely on. They\nmeasure and surface; a human decides.\n\n**Why a pipeline, not one pass:** one context holding every rule while fixing a\nlarge UI lets loud items crowd out quiet rules, which get silently dropped. So\ninspection and enforcement are split per area, and findings live in files. The\norchestrator (this context) stays thin — it holds routing only; the detailed\nrules and findings live in the reference doc and the findings files.\n\nRules SSOT: [references\u002Fui-theme-areas.md](references\u002Fui-theme-areas.md).\nValues: [references\u002Freference-corpus.md](references\u002Freference-corpus.md).\nRead only the area section you are working; do not load all rules into one\ncontext.\n\n## 0. Prep\n\n1. `hera-godot status` — confirm one live editor (the `live-editor` skill covers\n   setup). If multiple, pass `hera-godot --instance \u003Cpid>` to every mutation.\n2. `hera-godot guidance ui` — respect the returned UI mode.\n3. Ensure git is clean or on a branch; each area fix is one commit.\n4. Enumerate the target Controls: `hera-godot --ids scene tree` (edited scene) — this\n   is the static surface the checks read.\n\n## 1. Inspect (parallel, static, read-only)\n\nDispatch one inspector per area (`spacing`, `type-scale`, `color`, `contrast`,\n`containers`, `decoration`). Each:\n\n- reads **only its area section** of `references\u002Fui-theme-areas.md`,\n- measures the live editor with the read commands listed there\n  (`node get --props`, `eval --lang gdscript get_theme_color`, `game ui tree` rects),\n- writes `findings-\u003Carea>.md` using the schema (each item a **`check`\n  predicate**, never a status word).\n\nNo mutation here. Inspectors snap replacement values to the corpus so the fix is\ncarried in the finding, not invented later.\n\n## 2. Report\n\nMerge the `findings-*.md` into one local HTML report and serve it:\n`python3 -m http.server \u003Cport>` from the run folder, then hand the user\n`http:\u002F\u002Flocalhost:\u003Cport>\u002F`. Show measured values verbatim (distinct spacing\nvalues, font-size ratios, contrast ratios). No artifact, no browser auto-open —\nlink only.\n\n## 3. Enforce (sequential: spacing → type-scale → color → contrast)\n\nOne area enforcer at a time, in order. `containers` and `decoration` are skipped\nhere — they enforce nothing. Each enforcing area:\n\n- loads `findings-\u003Carea>.md` + its area section,\n- **re-measures each `check` from the live editor**; applies the fix only where\n  the predicate is currently false (never trust the finding text),\n- enforces with `hera-godot node set \u003Cpath> --prop \"\u003Ctheme_override…>\" --value \u003Cv>`\n  (undoable), snapping to the corpus rung\u002Fhex,\n- commits that area before the next runs.\n\nOrder = dependency order: `spacing` commits before `type-scale`, `color`\nconverges before `contrast`, and `contrast` runs last because it depends on the\nfinal colours.\n\n## 4. Re-inspect (fresh, parallel)\n\nDispatch fresh inspectors (not the enforcers) to recompute each **enforcing**\narea's `check` predicates from source and write `verify-\u003Carea>.md` (true =\napplied, false = missed). Any false re-enters step 3 for that area only. The\nreport-only areas have no `check` — they changed nothing, so there is nothing to\nre-verify, and inventing a predicate that always passes would be a lie.\n\n## 5. Render QA (confirmation only)\n\n`hera-godot run --current --wait`, then `hera-godot screenshot --runtime --analyze` for a\nbefore\u002Fafter and a clipping\u002Fblank sanity gate (`possible_clipping`, `nonblank`).\n`hera-godot stop --wait`. Render is confirmation, not measurement — the design facts\ncame from steps 1\u002F3. Update the report in place.\n\n## Contract (why this skill exists)\n\n- **Thin orchestrator.** This context holds routing only. Rules and findings\n  live in files. Holding all areas here reintroduces the capacity drop.\n- **A check is a predicate, not a status.** A finding is a `check` recomputed\n  from the live editor every time — never a stored \"done\". Enforcers fix only\n  false predicates; fresh re-inspectors recompute them.\n- **Snap, don't invent.** Replacement values come from the corpus, which is\n  rooted in Godot's own default theme plus WCAG. A project's own theme\u002Ftokens\n  win over the corpus if present.\n- **Undoable + reductive.** Only per-node theme overrides change, via\n  `node set` (Ctrl+Z survives). Copy, order, and layout are inviolable — which\n  is precisely why `containers` and `decoration` report instead of enforce.\n  Widening that would need an explicit opt-in flag, never a quiet default.\n- **Static inspect, render once.** Measurement is `node get` \u002F `eval` \u002F\n  `game ui tree`; the screenshot analyzer is the confirmation gate, not a\n  measurement tool.\n\n## Non-interactive\n\nFast, mechanical, non-interactive. Ambiguous items are proposed in the report,\nnot asked. Redesign-scale decisions (which accent, is this density right) are\nout of scope — surface them, do not silently pick.\n\n## Companion primitives and boundaries\n\nProject-wide Theme construction is available through\n`resource create Theme \u003Cres:\u002F\u002Ftheme.tres>` plus `theme set`, and\n`screenshot diff` can locate before\u002Fafter pixel changes. They complement this\nskill but do not change its safe default: enforcement remains undoable per-node\ntheme overrides, while project-wide resource writes are persistent and not\nundoable.\n\nAutomatic wholesale restyling remains out of scope. Hera can apply a style an\nagent or user has already chosen, but this workflow does not invent taste or\nsilently replace the project's visual language. See the repo's\n`docs\u002FUI_THEME_QA_DESIGN.md` §11.1.\n","\u003C!-- markdownlint-disable MD013 -->\n\n# UI Theme QA (Godot, reductive)\n\nMechanically remove statistical design defects from a live Godot editor, over\n`Control` nodes. It does not redesign: it snaps theme tokens to a reference\ncorpus and never touches copy, information order, or layout structure.\n\nSix areas, split by what they may do:\n\n| | areas | effect |\n| --- | --- | --- |\n| **enforcing** | `spacing` · `type-scale` · `color` · `contrast` | set `theme_override_*` (undoable) |\n| **report-only** | `containers` · `decoration` | proposals in the report; **no mutation** |\n\nThe report-only pair would have to delete or re-parent nodes, which cannot be\ndecided mechanically — a node that looks decorative may be a divider, and\nflattening a wrapper breaks the `$Path\u002FTo\u002FNode` references scripts rely on. They\nmeasure and surface; a human decides.\n\n**Why a pipeline, not one pass:** one context holding every rule while fixing a\nlarge UI lets loud items crowd out quiet rules, which get silently dropped. So\ninspection and enforcement are split per area, and findings live in files. The\norchestrator (this context) stays thin — it holds routing only; the detailed\nrules and findings live in the reference doc and the findings files.\n\nRules SSOT: [references\u002Fui-theme-areas.md](references\u002Fui-theme-areas.md).\nValues: [references\u002Freference-corpus.md](references\u002Freference-corpus.md).\nRead only the area section you are working; do not load all rules into one\ncontext.\n\n## 0. Prep\n\n1. `hera-godot status` — confirm one live editor (the `live-editor` skill covers\n   setup). If multiple, pass `hera-godot --instance \u003Cpid>` to every mutation.\n2. `hera-godot guidance ui` — respect the returned UI mode.\n3. Ensure git is clean or on a branch; each area fix is one commit.\n4. Enumerate the target Controls: `hera-godot --ids scene tree` (edited scene) — this\n   is the static surface the checks read.\n\n## 1. Inspect (parallel, static, read-only)\n\nDispatch one inspector per area (`spacing`, `type-scale`, `color`, `contrast`,\n`containers`, `decoration`). Each:\n\n- reads **only its area section** of `references\u002Fui-theme-areas.md`,\n- measures the live editor with the read commands listed there\n  (`node get --props`, `eval --lang gdscript get_theme_color`, `game ui tree` rects),\n- writes `findings-\u003Carea>.md` using the schema (each item a **`check`\n  predicate**, never a status word).\n\nNo mutation here. Inspectors snap replacement values to the corpus so the fix is\ncarried in the finding, not invented later.\n\n## 2. Report\n\nMerge the `findings-*.md` into one local HTML report and serve it:\n`python3 -m http.server \u003Cport>` from the run folder, then hand the user\n`http:\u002F\u002Flocalhost:\u003Cport>\u002F`. Show measured values verbatim (distinct spacing\nvalues, font-size ratios, contrast ratios). No artifact, no browser auto-open —\nlink only.\n\n## 3. Enforce (sequential: spacing → type-scale → color → contrast)\n\nOne area enforcer at a time, in order. `containers` and `decoration` are skipped\nhere — they enforce nothing. Each enforcing area:\n\n- loads `findings-\u003Carea>.md` + its area section,\n- **re-measures each `check` from the live editor**; applies the fix only where\n  the predicate is currently false (never trust the finding text),\n- enforces with `hera-godot node set \u003Cpath> --prop \"\u003Ctheme_override…>\" --value \u003Cv>`\n  (undoable), snapping to the corpus rung\u002Fhex,\n- commits that area before the next runs.\n\nOrder = dependency order: `spacing` commits before `type-scale`, `color`\nconverges before `contrast`, and `contrast` runs last because it depends on the\nfinal colours.\n\n## 4. Re-inspect (fresh, parallel)\n\nDispatch fresh inspectors (not the enforcers) to recompute each **enforcing**\narea's `check` predicates from source and write `verify-\u003Carea>.md` (true =\napplied, false = missed). Any false re-enters step 3 for that area only. The\nreport-only areas have no `check` — they changed nothing, so there is nothing to\nre-verify, and inventing a predicate that always passes would be a lie.\n\n## 5. Render QA (confirmation only)\n\n`hera-godot run --current --wait`, then `hera-godot screenshot --runtime --analyze` for a\nbefore\u002Fafter and a clipping\u002Fblank sanity gate (`possible_clipping`, `nonblank`).\n`hera-godot stop --wait`. Render is confirmation, not measurement — the design facts\ncame from steps 1\u002F3. Update the report in place.\n\n## Contract (why this skill exists)\n\n- **Thin orchestrator.** This context holds routing only. Rules and findings\n  live in files. Holding all areas here reintroduces the capacity drop.\n- **A check is a predicate, not a status.** A finding is a `check` recomputed\n  from the live editor every time — never a stored \"done\". Enforcers fix only\n  false predicates; fresh re-inspectors recompute them.\n- **Snap, don't invent.** Replacement values come from the corpus, which is\n  rooted in Godot's own default theme plus WCAG. A project's own theme\u002Ftokens\n  win over the corpus if present.\n- **Undoable + reductive.** Only per-node theme overrides change, via\n  `node set` (Ctrl+Z survives). Copy, order, and layout are inviolable — which\n  is precisely why `containers` and `decoration` report instead of enforce.\n  Widening that would need an explicit opt-in flag, never a quiet default.\n- **Static inspect, render once.** Measurement is `node get` \u002F `eval` \u002F\n  `game ui tree`; the screenshot analyzer is the confirmation gate, not a\n  measurement tool.\n\n## Non-interactive\n\nFast, mechanical, non-interactive. Ambiguous items are proposed in the report,\nnot asked. Redesign-scale decisions (which accent, is this density right) are\nout of scope — surface them, do not silently pick.\n\n## Companion primitives and boundaries\n\nProject-wide Theme construction is available through\n`resource create Theme \u003Cres:\u002F\u002Ftheme.tres>` plus `theme set`, and\n`screenshot diff` can locate before\u002Fafter pixel changes. They complement this\nskill but do not change its safe default: enforcement remains undoable per-node\ntheme overrides, while project-wide resource writes are persistent and not\nundoable.\n\nAutomatic wholesale restyling remains out of scope. Hera can apply a style an\nagent or user has already chosen, but this workflow does not invent taste or\nsilently replace the project's visual language. See the repo's\n`docs\u002FUI_THEME_QA_DESIGN.md` §11.1.\n",{"name":5,"description":7},"main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002FNotNull92\u002Fhera-agent-godot\u002Fskills\u002Fui-theme-qa",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":65,"prompt":75,"zipAvailable":76},[66,69,72],{"tool":67,"command":68},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill ui-theme-qa",{"tool":70,"command":71},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill ui-theme-qa",{"tool":73,"command":74},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill ui-theme-qa","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FNotNull92\u002Fhera-agent-godot\u002Fskills\u002Fui-theme-qa\u002FSKILL.md",true,[78,84],{"path":79,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":82,"sourceHtmlUrl":83},"references\u002Freference-corpus.md","REFERENCE","参考文档",5726,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FNotNull92\u002Fhera-agent-godot\u002Fskills\u002Fui-theme-qa\u002Freferences\u002Freference-corpus.md",{"path":85,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":86,"sourceHtmlUrl":87},"references\u002Fui-theme-areas.md",14872,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FNotNull92\u002Fhera-agent-godot\u002Fskills\u002Fui-theme-qa\u002Freferences\u002Fui-theme-areas.md",[89,99,107,115,123,131],{"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":93,"licenseFileUrl":94,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":98},"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":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":93,"licenseFileUrl":103,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":98},"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":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":93,"licenseFileUrl":111,"sourceHtmlUrl":112,"categories":113,"keywords":114,"publishedAt":98},"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":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":93,"licenseFileUrl":119,"sourceHtmlUrl":120,"categories":121,"keywords":122,"publishedAt":98},"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":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":93,"licenseFileUrl":127,"sourceHtmlUrl":128,"categories":129,"keywords":130,"publishedAt":98},"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":132,"name":133,"nameZh":6,"description":134,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":93,"licenseFileUrl":135,"sourceHtmlUrl":136,"categories":137,"keywords":138,"publishedAt":98},"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",[],[]]