[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6JW3D099VGS74GG9EHASDD5":3,"skill-same:01M6JW3D099VGS74GG9EHASDD5":77},{"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":42,"linkOnly":43,"markdownContent":44,"markdownBody":45,"frontMatter":46,"refName":47,"commitSha":48,"skillDirectory":49,"forksCount":50,"repositoryHtmlUrl":51,"repositoryHomepageUrl":52,"ownerHtmlUrl":53,"ownerBlogUrl":54,"ownerDescription":55,"updatedAt":56,"install":57,"resources":70},"01M6JW3D099VGS74GG9EHASDD5","affordance-false-and-anti",null,"Use this skill when designing or fixing controls that mislead users — elements that look interactive but aren't (false affordance), or controls that need to clearly communicate \"you can't do that here\" (anti-affordance, like disabled states). Trigger when reviewing UIs where users tap inert elements expecting response, when designing disabled states, when picking treatments for read-only fields, or when a \"decorative\" element is being mistaken for a button. Sub-aspect of `affordance`; read that first.","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\u002FHDeibler\u002Funiversal-design-principles\u002Fplugins\u002Finteraction-and-control-principles\u002Fskills\u002Faffordance-false-and-anti\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41],"affordance","affordance false and anti","false","element","when","for","can","read-only","you","states","communicate","controls","users","first","trigger","elements","but","do","tap","only","use","interactive","read","2026-11-10 10:12:30",false,"---\nname: affordance-false-and-anti\ndescription: 'Use this skill when designing or fixing controls that mislead users — elements that look interactive but aren''t (false affordance), or controls that need to clearly communicate \"you can''t do that here\" (anti-affordance, like disabled states). Trigger when reviewing UIs where users tap inert elements expecting response, when designing disabled states, when picking treatments for read-only fields, or when a \"decorative\" element is being mistaken for a button. Sub-aspect of `affordance`; read that first.'\n---\n\n# False affordance and anti-affordance\n\nThe mirror images of standard affordance: the elements that *look* interactive but aren't, and the elements that *are* interactive but should signal \"not right now.\" Both deserve as much design attention as standard affordance — and both are routinely neglected.\n\n## False affordance: looks interactive, isn't\n\nA false affordance is an element whose visual treatment suggests interactivity it doesn't have. The user is led to expect an action; the action doesn't happen; trust drops.\n\nCommon sources:\n\n- **Cards and panels styled like buttons.** A bordered, rounded, slightly-elevated container holds static content. Users tap; nothing happens.\n- **Hover states on non-interactive elements.** A box that highlights on hover but isn't clickable. Users learn to mistrust hover signals.\n- **Hyperlink-blue text that isn't a link.** Some design systems use blue for emphasis without realizing users read it as link affordance.\n- **Underlined non-link text.** Underline is a strong link signifier; using it for emphasis or definition collides with that convention.\n- **Icon-buttons next to non-interactive content.** A trash icon shown next to an item the user actually can't delete.\n\n### Fixes\n\n- Strip interactive-looking treatments from inert content. Use neutral backgrounds, no borders, no hover changes.\n- Reserve underlines for actual links. Use bold or italics for emphasis instead.\n- If a box must look distinct, use *uniform connectedness* (a tinted region) rather than *button-like elevation* (drop shadow, border).\n\n## Anti-affordance: signaling \"you can't\"\n\nAnti-affordance is the deliberate design of cues that tell the user \"this is interactive in principle but unavailable to you right now.\" The most common case: disabled controls.\n\nA disabled control needs to:\n\n1. **Look different** from enabled (lower opacity, neutral color, no fill).\n2. **Not respond** to hover or click as it would when enabled.\n3. **Show a \"no\" cursor** (`cursor: not-allowed`).\n4. **Optionally explain** why it's disabled — via tooltip or adjacent text.\n\n```html\n\u003Cbutton class=\"btn\" disabled\n        aria-disabled=\"true\"\n        title=\"Add at least one item to checkout\">\n  Continue to checkout\n\u003C\u002Fbutton>\n```\n\n```css\n.btn[disabled] {\n  background: hsl(0 0% 92%);\n  color: hsl(0 0% 50%);\n  cursor: not-allowed;\n  opacity: 0.7;\n}\n.btn[disabled]:hover {\n  \u002F* no change — this is the anti-affordance *\u002F\n  background: hsl(0 0% 92%);\n}\n```\n\n### When *not* to disable\n\nA common UX mistake: disabling a button silently when the user \"isn't ready\" (form has unfilled required field; cart is empty). The user sees a non-responsive button and doesn't know why.\n\nBetter:\n\n- **Keep the button enabled** and surface the validation error on click. The user gets a clear explanation rather than a silent block.\n- Or, if the button must be disabled, **explain why** alongside it (a small note, a tooltip on hover\u002Ffocus, or a visible reason).\n\n```html\n\u003Cbutton class=\"btn\">Continue to checkout\u003C\u002Fbutton>\n\u003Cp class=\"hint\">Add at least one item to your cart to continue.\u003C\u002Fp>\n```\n\nThe user can read the hint and act; the button isn't a dead end.\n\n### Read-only fields\n\nA field that's input-shaped but not editable is a special anti-affordance case.\n\n```html\n\u003Clabel>Account ID\n  \u003Cinput type=\"text\" value=\"acct_8f3c7a\" readonly \u002F>\n\u003C\u002Flabel>\n```\n\n```css\ninput[readonly] {\n  background: hsl(0 0% 96%);\n  color: hsl(0 0% 30%);\n  cursor: text;       \u002F* still selectable for copy *\u002F\n  border: 1px solid hsl(0 0% 90%);\n}\n```\n\nThe treatment says \"this is data, not a control\" — neutral background, no focus outline activation, but still selectable so users can copy.\n\nFor fields that aren't *currently* editable but *could* be (e.g., locked behind a permission), the visual treatment should hint that editability exists in principle.\n\n## False affordance from animation\n\nA subtle modern source: animating a non-interactive element. A heading that wiggles, an icon that pulses, a card that slowly tilts. These attract attention; users assume attention means interactivity.\n\nIf the animation is decoration only, audit whether it's drawing attention away from real interactive controls. If it's a callout for new content, ensure clicking does *something* — even if just to dismiss the callout.\n\n## Worked examples\n\n### Example 1: a card that *should* be clickable vs. one that shouldn't\n\n```html\n\u003C!-- Clickable: card-link wraps, hover responds -->\n\u003Ca href=\"\u002Fprojects\u002Facme\" class=\"card-link\">\n  \u003Carticle class=\"card\">...\u003C\u002Farticle>\n\u003C\u002Fa>\n\n\u003C!-- Inert: no link wrap, no hover response -->\n\u003Carticle class=\"card card--inert\">\n  \u003Ch3>System status\u003C\u002Fh3>\n  \u003Cp>All services operational.\u003C\u002Fp>\n\u003C\u002Farticle>\n```\n\n```css\n.card { padding: 16px; border: 1px solid hsl(0 0% 88%); border-radius: 8px; }\n.card-link { display: block; text-decoration: none; color: inherit; }\n.card-link:hover .card { border-color: hsl(220 90% 60%); box-shadow: 0 4px 12px rgba(0,0,0,0.08); }\n\n.card--inert {\n  background: hsl(0 0% 98%);  \u002F* slightly different bg signals \"informational\" *\u002F\n  border-color: hsl(0 0% 92%);\n}\n.card--inert:hover {\n  \u002F* no change — anti-affordance *\u002F\n}\n```\n\nThe clickable card shifts on hover; the inert one stays still. Users learn quickly that hover-responsive cards are clickable and others aren't.\n\n### Example 2: read-only vs. disabled vs. unavailable\n\nThree subtly different states, each with its own anti-affordance:\n\n```html\n\u003C!-- Read-only: data, never editable here -->\n\u003Clabel>Workspace ID\n  \u003Cinput value=\"ws_abc123\" readonly \u002F>\n\u003C\u002Flabel>\n\n\u003C!-- Disabled because of state: editable when condition is met -->\n\u003Clabel>Email\n  \u003Cinput value=\"user@example.com\" disabled aria-describedby=\"email-locked\" \u002F>\n\u003C\u002Flabel>\n\u003Cp id=\"email-locked\" class=\"hint\">Verify your email to enable changes.\u003C\u002Fp>\n\n\u003C!-- Unavailable due to permission: visible but not actionable -->\n\u003Clabel class=\"field-locked\">\n  \u003Cspan>Workspace name \u003CLockIcon aria-hidden \u002F>\u003C\u002Fspan>\n  \u003Cinput value=\"Acme Inc\" readonly \u002F>\n  \u003Cp class=\"hint\">Only workspace admins can change this.\u003C\u002Fp>\n\u003C\u002Flabel>\n```\n\nThe user gets specific anti-affordance signals for each: read-only data is visually demoted; conditionally-disabled is enabled-looking-but-with-explanation; permission-locked has a lock icon and explanation.\n\n## Anti-patterns\n\n- **Decorative elevation on content cards.** Drop shadows that suggest \"object you can interact with\" on cards that are pure content. Strip the shadow.\n- **Disabled-button silent dead ends.** A submit button that's just disabled with no explanation. Users hunt for what's wrong.\n- **Read-only fields styled identically to editable.** Users tab into them, type, get confused.\n- **Inert hover responses.** A non-clickable element with a hover style applied \"for visual interest.\" Users tap it, nothing happens, trust drops.\n\n## Heuristics\n\n1. **The \"I tapped, nothing happened\" audit.** Watch users. Each unproductive tap is a false-affordance failure or an anti-affordance failure (disabled with no explanation).\n2. **The hover-style audit.** Every element with a hover state should be interactive. If you have hover styles on non-interactive elements, strip them.\n3. **The disabled-with-context check.** Every disabled control on every page should answer \"why?\" — via tooltip, adjacent text, or context.\n\n## Related sub-skills\n\n- **`affordance`** (parent).\n- **`affordance-signifiers`** — the standard case of making affordance visible.\n- **`feedback-loop`** — disabled controls should still give *some* feedback (cursor change at minimum).\n- **`accessibility-understandable`** (process) — disabled states must be programmatically conveyed (`disabled` attribute, `aria-disabled`).\n","# False affordance and anti-affordance\n\nThe mirror images of standard affordance: the elements that *look* interactive but aren't, and the elements that *are* interactive but should signal \"not right now.\" Both deserve as much design attention as standard affordance — and both are routinely neglected.\n\n## False affordance: looks interactive, isn't\n\nA false affordance is an element whose visual treatment suggests interactivity it doesn't have. The user is led to expect an action; the action doesn't happen; trust drops.\n\nCommon sources:\n\n- **Cards and panels styled like buttons.** A bordered, rounded, slightly-elevated container holds static content. Users tap; nothing happens.\n- **Hover states on non-interactive elements.** A box that highlights on hover but isn't clickable. Users learn to mistrust hover signals.\n- **Hyperlink-blue text that isn't a link.** Some design systems use blue for emphasis without realizing users read it as link affordance.\n- **Underlined non-link text.** Underline is a strong link signifier; using it for emphasis or definition collides with that convention.\n- **Icon-buttons next to non-interactive content.** A trash icon shown next to an item the user actually can't delete.\n\n### Fixes\n\n- Strip interactive-looking treatments from inert content. Use neutral backgrounds, no borders, no hover changes.\n- Reserve underlines for actual links. Use bold or italics for emphasis instead.\n- If a box must look distinct, use *uniform connectedness* (a tinted region) rather than *button-like elevation* (drop shadow, border).\n\n## Anti-affordance: signaling \"you can't\"\n\nAnti-affordance is the deliberate design of cues that tell the user \"this is interactive in principle but unavailable to you right now.\" The most common case: disabled controls.\n\nA disabled control needs to:\n\n1. **Look different** from enabled (lower opacity, neutral color, no fill).\n2. **Not respond** to hover or click as it would when enabled.\n3. **Show a \"no\" cursor** (`cursor: not-allowed`).\n4. **Optionally explain** why it's disabled — via tooltip or adjacent text.\n\n```html\n\u003Cbutton class=\"btn\" disabled\n        aria-disabled=\"true\"\n        title=\"Add at least one item to checkout\">\n  Continue to checkout\n\u003C\u002Fbutton>\n```\n\n```css\n.btn[disabled] {\n  background: hsl(0 0% 92%);\n  color: hsl(0 0% 50%);\n  cursor: not-allowed;\n  opacity: 0.7;\n}\n.btn[disabled]:hover {\n  \u002F* no change — this is the anti-affordance *\u002F\n  background: hsl(0 0% 92%);\n}\n```\n\n### When *not* to disable\n\nA common UX mistake: disabling a button silently when the user \"isn't ready\" (form has unfilled required field; cart is empty). The user sees a non-responsive button and doesn't know why.\n\nBetter:\n\n- **Keep the button enabled** and surface the validation error on click. The user gets a clear explanation rather than a silent block.\n- Or, if the button must be disabled, **explain why** alongside it (a small note, a tooltip on hover\u002Ffocus, or a visible reason).\n\n```html\n\u003Cbutton class=\"btn\">Continue to checkout\u003C\u002Fbutton>\n\u003Cp class=\"hint\">Add at least one item to your cart to continue.\u003C\u002Fp>\n```\n\nThe user can read the hint and act; the button isn't a dead end.\n\n### Read-only fields\n\nA field that's input-shaped but not editable is a special anti-affordance case.\n\n```html\n\u003Clabel>Account ID\n  \u003Cinput type=\"text\" value=\"acct_8f3c7a\" readonly \u002F>\n\u003C\u002Flabel>\n```\n\n```css\ninput[readonly] {\n  background: hsl(0 0% 96%);\n  color: hsl(0 0% 30%);\n  cursor: text;       \u002F* still selectable for copy *\u002F\n  border: 1px solid hsl(0 0% 90%);\n}\n```\n\nThe treatment says \"this is data, not a control\" — neutral background, no focus outline activation, but still selectable so users can copy.\n\nFor fields that aren't *currently* editable but *could* be (e.g., locked behind a permission), the visual treatment should hint that editability exists in principle.\n\n## False affordance from animation\n\nA subtle modern source: animating a non-interactive element. A heading that wiggles, an icon that pulses, a card that slowly tilts. These attract attention; users assume attention means interactivity.\n\nIf the animation is decoration only, audit whether it's drawing attention away from real interactive controls. If it's a callout for new content, ensure clicking does *something* — even if just to dismiss the callout.\n\n## Worked examples\n\n### Example 1: a card that *should* be clickable vs. one that shouldn't\n\n```html\n\u003C!-- Clickable: card-link wraps, hover responds -->\n\u003Ca href=\"\u002Fprojects\u002Facme\" class=\"card-link\">\n  \u003Carticle class=\"card\">...\u003C\u002Farticle>\n\u003C\u002Fa>\n\n\u003C!-- Inert: no link wrap, no hover response -->\n\u003Carticle class=\"card card--inert\">\n  \u003Ch3>System status\u003C\u002Fh3>\n  \u003Cp>All services operational.\u003C\u002Fp>\n\u003C\u002Farticle>\n```\n\n```css\n.card { padding: 16px; border: 1px solid hsl(0 0% 88%); border-radius: 8px; }\n.card-link { display: block; text-decoration: none; color: inherit; }\n.card-link:hover .card { border-color: hsl(220 90% 60%); box-shadow: 0 4px 12px rgba(0,0,0,0.08); }\n\n.card--inert {\n  background: hsl(0 0% 98%);  \u002F* slightly different bg signals \"informational\" *\u002F\n  border-color: hsl(0 0% 92%);\n}\n.card--inert:hover {\n  \u002F* no change — anti-affordance *\u002F\n}\n```\n\nThe clickable card shifts on hover; the inert one stays still. Users learn quickly that hover-responsive cards are clickable and others aren't.\n\n### Example 2: read-only vs. disabled vs. unavailable\n\nThree subtly different states, each with its own anti-affordance:\n\n```html\n\u003C!-- Read-only: data, never editable here -->\n\u003Clabel>Workspace ID\n  \u003Cinput value=\"ws_abc123\" readonly \u002F>\n\u003C\u002Flabel>\n\n\u003C!-- Disabled because of state: editable when condition is met -->\n\u003Clabel>Email\n  \u003Cinput value=\"user@example.com\" disabled aria-describedby=\"email-locked\" \u002F>\n\u003C\u002Flabel>\n\u003Cp id=\"email-locked\" class=\"hint\">Verify your email to enable changes.\u003C\u002Fp>\n\n\u003C!-- Unavailable due to permission: visible but not actionable -->\n\u003Clabel class=\"field-locked\">\n  \u003Cspan>Workspace name \u003CLockIcon aria-hidden \u002F>\u003C\u002Fspan>\n  \u003Cinput value=\"Acme Inc\" readonly \u002F>\n  \u003Cp class=\"hint\">Only workspace admins can change this.\u003C\u002Fp>\n\u003C\u002Flabel>\n```\n\nThe user gets specific anti-affordance signals for each: read-only data is visually demoted; conditionally-disabled is enabled-looking-but-with-explanation; permission-locked has a lock icon and explanation.\n\n## Anti-patterns\n\n- **Decorative elevation on content cards.** Drop shadows that suggest \"object you can interact with\" on cards that are pure content. Strip the shadow.\n- **Disabled-button silent dead ends.** A submit button that's just disabled with no explanation. Users hunt for what's wrong.\n- **Read-only fields styled identically to editable.** Users tab into them, type, get confused.\n- **Inert hover responses.** A non-clickable element with a hover style applied \"for visual interest.\" Users tap it, nothing happens, trust drops.\n\n## Heuristics\n\n1. **The \"I tapped, nothing happened\" audit.** Watch users. Each unproductive tap is a false-affordance failure or an anti-affordance failure (disabled with no explanation).\n2. **The hover-style audit.** Every element with a hover state should be interactive. If you have hover styles on non-interactive elements, strip them.\n3. **The disabled-with-context check.** Every disabled control on every page should answer \"why?\" — via tooltip, adjacent text, or context.\n\n## Related sub-skills\n\n- **`affordance`** (parent).\n- **`affordance-signifiers`** — the standard case of making affordance visible.\n- **`feedback-loop`** — disabled controls should still give *some* feedback (cursor change at minimum).\n- **`accessibility-understandable`** (process) — disabled states must be programmatically conveyed (`disabled` attribute, `aria-disabled`).\n",{"name":5,"description":7},"main","b0f0a87593c578a7898eccaf1b363f7f87c1f99b","plugins\u002FHDeibler\u002Funiversal-design-principles\u002Fplugins\u002Finteraction-and-control-principles\u002Fskills\u002Faffordance-false-and-anti",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":58,"prompt":68,"zipAvailable":69},[59,62,65],{"tool":60,"command":61},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill affordance-false-and-anti",{"tool":63,"command":64},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill affordance-false-and-anti",{"tool":66,"command":67},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill affordance-false-and-anti","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FHDeibler\u002Funiversal-design-principles\u002Fplugins\u002Finteraction-and-control-principles\u002Fskills\u002Faffordance-false-and-anti\u002FSKILL.md",true,[71],{"path":72,"resourceType":73,"resourceTypeDesc":74,"sizeBytes":75,"sourceHtmlUrl":76},"references\u002Fdisabled-state-patterns.md","REFERENCE","参考文档",3871,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FHDeibler\u002Funiversal-design-principles\u002Fplugins\u002Finteraction-and-control-principles\u002Fskills\u002Faffordance-false-and-anti\u002Freferences\u002Fdisabled-state-patterns.md",[78,88,96,104,112,120],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":82,"licenseFileUrl":83,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":87},"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":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":82,"licenseFileUrl":92,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":87},"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":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":82,"licenseFileUrl":100,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":87},"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":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":82,"licenseFileUrl":108,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":87},"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":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":82,"licenseFileUrl":116,"sourceHtmlUrl":117,"categories":118,"keywords":119,"publishedAt":87},"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":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":82,"licenseFileUrl":124,"sourceHtmlUrl":125,"categories":126,"keywords":127,"publishedAt":87},"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",[],[]]