[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6JW3HGG0WVTJ3GQFTT4PS8E":3,"skill-same:01M6JW3HGG0WVTJ3GQFTT4PS8E":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},"01M6JW3HGG0WVTJ3GQFTT4PS8E","affordance-signifiers",null,"Use this skill when the design has interactive capability but users aren't *seeing* it — when the affordance is technically present but the signifier (the visible cue that tells users \"you can do this\") is missing or weak. Trigger when reviewing flat-design UIs where everything looks the same, when designing custom controls, when stakeholders ask \"should this be more obvious?\", or when picking signifier strength for primary vs. secondary actions. 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-signifiers\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 signifiers","missing","when","capability","custom","for","can","more","you","controls","users","design","trigger","cue","present","but","do","use","interactive","read","ask","actions","2026-11-10 10:12:30",false,"---\nname: affordance-signifiers\ndescription: 'Use this skill when the design has interactive capability but users aren''t *seeing* it — when the affordance is technically present but the signifier (the visible cue that tells users \"you can do this\") is missing or weak. Trigger when reviewing flat-design UIs where everything looks the same, when designing custom controls, when stakeholders ask \"should this be more obvious?\", or when picking signifier strength for primary vs. secondary actions. Sub-aspect of `affordance`; read that first.'\n---\n\n# Signifiers: making affordance perceivable\n\nIn Norman's later refinement (2008), he distinguished *affordance* (the underlying possibility — a button can be pressed) from *signifier* (the visible cue that tells the user about the affordance — the button looks pressable). The distinction matters because designers control signifiers; affordances often exist regardless. A button that's missing a signifier still affords pressing — but no one knows.\n\n## The signifier inventory\n\nEvery interactive element should carry one or more signifiers. The strongest are perceivable preattentively (within the first 200ms of viewing) without conscious thought.\n\n### Strong signifiers\n\n- **Filled background** with a brand or neutral color, distinct from the page background. Reads as \"object.\"\n- **Visible border** outlining the interactive region. Reads as \"discrete element you can act on.\"\n- **Drop shadow \u002F elevation** suggesting the element floats above content.\n- **Distinctive shape** (rounded rectangle for buttons, pill shape for chips, circle for FABs).\n- **Underline** for links.\n\n### Medium signifiers\n\n- **Color difference from surrounding text** (the classic blue link).\n- **Cursor change** on hover (`cursor: pointer`). Desktop only.\n- **Hover state** (color shift, shadow change). Desktop only.\n- **Focus ring** when keyboard-focused. Critical for keyboard users.\n- **Iconography** (a pencil for edit, a trash for delete) for users who recognize the convention.\n\n### Weak signifiers\n\n- **Subtle color tint** (5% darker than background). Easy to miss.\n- **Tiny chevron or arrow** at the edge. Easy to miss.\n- **Implicit position** (e.g., \"the bottom right of every card has the row actions\"). Requires learning.\n\nFor new-user surfaces, lean on strong signifiers. For dense expert tools, medium signifiers are acceptable because users develop spatial memory.\n\n## Signifier strength must match action stakes\n\nA useful rule: signifier strength should match the action's importance and consequence.\n\n```\nPrimary action (Submit, Buy, Continue)\n  → Strongest signifier: filled background + brand color + cursor + hover\n\nSecondary action (Cancel, Save Draft)\n  → Medium signifier: outlined border + cursor + hover\n\nTertiary action (Help, More info)\n  → Lighter signifier: text-only + color + underline on hover\n\nDestructive action (Delete, Remove)\n  → Different signifier: distinct color (red) + cursor + hover, often after a confirmation step\n```\n\nWhen the primary action has the same signifier as the tertiary, the user doesn't know which is most important. Signifier strength is a hierarchy decision.\n\n## Hover, focus, and active state signifiers\n\nStatic signifiers tell the user \"this is interactive.\" Response signifiers tell them \"you've engaged it.\"\n\n- **Hover** (mouse over): color shift, shadow lift, slight scale change.\n- **Focus** (keyboard tab to): visible focus ring (`outline: 2px solid var(--ring); outline-offset: 2px`).\n- **Active** (pressing\u002Fholding): darker color, slight inset shadow, no scale change.\n- **Disabled**: lighter color, no hover\u002Factive response, `cursor: not-allowed`.\n\nThese should *layer*. A button with a strong static signifier should still respond to hover and focus.\n\n```css\n.btn {\n  \u002F* static signifier *\u002F\n  background: hsl(220 90% 50%);\n  color: white;\n  padding: 8px 16px;\n  border: 0;\n  border-radius: 6px;\n  cursor: pointer;\n  transition: background 100ms;\n}\n.btn:hover { background: hsl(220 90% 45%); }\n.btn:focus-visible {\n  outline: 2px solid hsl(220 90% 50%);\n  outline-offset: 2px;\n}\n.btn:active { background: hsl(220 90% 40%); }\n.btn[disabled] {\n  background: hsl(0 0% 92%);\n  color: hsl(0 0% 50%);\n  cursor: not-allowed;\n}\n```\n\nFive distinct states; each communicates something different. Stripping any of them weakens the signifier system.\n\n## Signifier patterns by component type\n\n### Button\n\n- Filled or outlined background.\n- Distinct shape (typically rounded rectangle).\n- Cursor pointer.\n- Hover\u002Ffocus\u002Factive states.\n- Always pair with a verb label.\n\n### Link\n\n- Color (typically brand).\n- Underline (always or on hover, depending on context).\n- Cursor pointer.\n- Distinct from surrounding body text.\n\n### Input field\n\n- Distinct background (usually different from surrounding page).\n- Border (visible or visible on focus).\n- Cursor text on hover.\n- Focus ring or border-color change on focus.\n\n### Toggle \u002F switch\n\n- Distinctive shape (pill with circular slider).\n- Animated transition between states.\n- Strong color difference between on and off.\n\n### Drag handle\n\n- Iconographic signifier (six dots, two-line \"grip\").\n- `cursor: grab` on hover, `cursor: grabbing` on active.\n- Often dimmed in still state, brighter on hover.\n\n### Disclosure trigger (accordion, \"More\")\n\n- Chevron or plus\u002Fminus icon.\n- Animation on toggle.\n- Cursor pointer.\n- Often whole row is hover-responsive, not just the icon.\n\n## Anti-patterns\n\n- **Signifier-stripped flat design.** A \"minimalist\" button with no border, no background, no shadow. Identical to surrounding text except for slight color. Users miss it.\n- **Hover-only signifier.** Element looks like content; only on hover does it reveal it's a button. Touch users see no signifier; keyboard users may not focus it; even mouse users may not hover.\n- **Signifier mismatch with role.** A \"tertiary\" action (like a help link) given the strongest signifier — users press it expecting the primary action.\n- **Inconsistent signifiers for the same role.** \"Submit\" buttons vary in style across pages. Each page is a re-learning.\n- **Disabled controls without anti-affordance.** A disabled button that looks identical to enabled. Users tap; nothing happens; confusion.\n\n## Heuristics\n\n1. **The signifier audit.** For each interactive element on the page, list its signifiers. If the count is 0–1, signifier is too weak. 2+ stacked signifiers (background + cursor + hover) is the safer baseline.\n2. **The role-vs-signifier check.** Does the visual emphasis of each element match its role importance? Primary action should have the strongest signifier; tertiary the weakest.\n3. **The state coverage check.** For each interactive element, do you have static, hover, focus, active, and disabled signifiers? Missing focus = inaccessible to keyboard. Missing active = no press feedback.\n\n## Related sub-skills\n\n- **`affordance`** (parent).\n- **`affordance-false-and-anti`** — the inverse problem: when signifiers suggest interactivity that isn't there.\n- **`hierarchy`** (perception) — signifier strength is a hierarchy decision.\n- **`accessibility-perceivable`** (process) — signifiers must be perceivable across abilities.\n- **`feedback-loop`** — response signifiers (hover, focus, active) are micro-feedback.\n","# Signifiers: making affordance perceivable\n\nIn Norman's later refinement (2008), he distinguished *affordance* (the underlying possibility — a button can be pressed) from *signifier* (the visible cue that tells the user about the affordance — the button looks pressable). The distinction matters because designers control signifiers; affordances often exist regardless. A button that's missing a signifier still affords pressing — but no one knows.\n\n## The signifier inventory\n\nEvery interactive element should carry one or more signifiers. The strongest are perceivable preattentively (within the first 200ms of viewing) without conscious thought.\n\n### Strong signifiers\n\n- **Filled background** with a brand or neutral color, distinct from the page background. Reads as \"object.\"\n- **Visible border** outlining the interactive region. Reads as \"discrete element you can act on.\"\n- **Drop shadow \u002F elevation** suggesting the element floats above content.\n- **Distinctive shape** (rounded rectangle for buttons, pill shape for chips, circle for FABs).\n- **Underline** for links.\n\n### Medium signifiers\n\n- **Color difference from surrounding text** (the classic blue link).\n- **Cursor change** on hover (`cursor: pointer`). Desktop only.\n- **Hover state** (color shift, shadow change). Desktop only.\n- **Focus ring** when keyboard-focused. Critical for keyboard users.\n- **Iconography** (a pencil for edit, a trash for delete) for users who recognize the convention.\n\n### Weak signifiers\n\n- **Subtle color tint** (5% darker than background). Easy to miss.\n- **Tiny chevron or arrow** at the edge. Easy to miss.\n- **Implicit position** (e.g., \"the bottom right of every card has the row actions\"). Requires learning.\n\nFor new-user surfaces, lean on strong signifiers. For dense expert tools, medium signifiers are acceptable because users develop spatial memory.\n\n## Signifier strength must match action stakes\n\nA useful rule: signifier strength should match the action's importance and consequence.\n\n```\nPrimary action (Submit, Buy, Continue)\n  → Strongest signifier: filled background + brand color + cursor + hover\n\nSecondary action (Cancel, Save Draft)\n  → Medium signifier: outlined border + cursor + hover\n\nTertiary action (Help, More info)\n  → Lighter signifier: text-only + color + underline on hover\n\nDestructive action (Delete, Remove)\n  → Different signifier: distinct color (red) + cursor + hover, often after a confirmation step\n```\n\nWhen the primary action has the same signifier as the tertiary, the user doesn't know which is most important. Signifier strength is a hierarchy decision.\n\n## Hover, focus, and active state signifiers\n\nStatic signifiers tell the user \"this is interactive.\" Response signifiers tell them \"you've engaged it.\"\n\n- **Hover** (mouse over): color shift, shadow lift, slight scale change.\n- **Focus** (keyboard tab to): visible focus ring (`outline: 2px solid var(--ring); outline-offset: 2px`).\n- **Active** (pressing\u002Fholding): darker color, slight inset shadow, no scale change.\n- **Disabled**: lighter color, no hover\u002Factive response, `cursor: not-allowed`.\n\nThese should *layer*. A button with a strong static signifier should still respond to hover and focus.\n\n```css\n.btn {\n  \u002F* static signifier *\u002F\n  background: hsl(220 90% 50%);\n  color: white;\n  padding: 8px 16px;\n  border: 0;\n  border-radius: 6px;\n  cursor: pointer;\n  transition: background 100ms;\n}\n.btn:hover { background: hsl(220 90% 45%); }\n.btn:focus-visible {\n  outline: 2px solid hsl(220 90% 50%);\n  outline-offset: 2px;\n}\n.btn:active { background: hsl(220 90% 40%); }\n.btn[disabled] {\n  background: hsl(0 0% 92%);\n  color: hsl(0 0% 50%);\n  cursor: not-allowed;\n}\n```\n\nFive distinct states; each communicates something different. Stripping any of them weakens the signifier system.\n\n## Signifier patterns by component type\n\n### Button\n\n- Filled or outlined background.\n- Distinct shape (typically rounded rectangle).\n- Cursor pointer.\n- Hover\u002Ffocus\u002Factive states.\n- Always pair with a verb label.\n\n### Link\n\n- Color (typically brand).\n- Underline (always or on hover, depending on context).\n- Cursor pointer.\n- Distinct from surrounding body text.\n\n### Input field\n\n- Distinct background (usually different from surrounding page).\n- Border (visible or visible on focus).\n- Cursor text on hover.\n- Focus ring or border-color change on focus.\n\n### Toggle \u002F switch\n\n- Distinctive shape (pill with circular slider).\n- Animated transition between states.\n- Strong color difference between on and off.\n\n### Drag handle\n\n- Iconographic signifier (six dots, two-line \"grip\").\n- `cursor: grab` on hover, `cursor: grabbing` on active.\n- Often dimmed in still state, brighter on hover.\n\n### Disclosure trigger (accordion, \"More\")\n\n- Chevron or plus\u002Fminus icon.\n- Animation on toggle.\n- Cursor pointer.\n- Often whole row is hover-responsive, not just the icon.\n\n## Anti-patterns\n\n- **Signifier-stripped flat design.** A \"minimalist\" button with no border, no background, no shadow. Identical to surrounding text except for slight color. Users miss it.\n- **Hover-only signifier.** Element looks like content; only on hover does it reveal it's a button. Touch users see no signifier; keyboard users may not focus it; even mouse users may not hover.\n- **Signifier mismatch with role.** A \"tertiary\" action (like a help link) given the strongest signifier — users press it expecting the primary action.\n- **Inconsistent signifiers for the same role.** \"Submit\" buttons vary in style across pages. Each page is a re-learning.\n- **Disabled controls without anti-affordance.** A disabled button that looks identical to enabled. Users tap; nothing happens; confusion.\n\n## Heuristics\n\n1. **The signifier audit.** For each interactive element on the page, list its signifiers. If the count is 0–1, signifier is too weak. 2+ stacked signifiers (background + cursor + hover) is the safer baseline.\n2. **The role-vs-signifier check.** Does the visual emphasis of each element match its role importance? Primary action should have the strongest signifier; tertiary the weakest.\n3. **The state coverage check.** For each interactive element, do you have static, hover, focus, active, and disabled signifiers? Missing focus = inaccessible to keyboard. Missing active = no press feedback.\n\n## Related sub-skills\n\n- **`affordance`** (parent).\n- **`affordance-false-and-anti`** — the inverse problem: when signifiers suggest interactivity that isn't there.\n- **`hierarchy`** (perception) — signifier strength is a hierarchy decision.\n- **`accessibility-perceivable`** (process) — signifiers must be perceivable across abilities.\n- **`feedback-loop`** — response signifiers (hover, focus, active) are micro-feedback.\n",{"name":5,"description":7},"main","b0f0a87593c578a7898eccaf1b363f7f87c1f99b","plugins\u002FHDeibler\u002Funiversal-design-principles\u002Fplugins\u002Finteraction-and-control-principles\u002Fskills\u002Faffordance-signifiers",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-signifiers",{"tool":63,"command":64},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill affordance-signifiers",{"tool":66,"command":67},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill affordance-signifiers","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FHDeibler\u002Funiversal-design-principles\u002Fplugins\u002Finteraction-and-control-principles\u002Fskills\u002Faffordance-signifiers\u002FSKILL.md",true,[71],{"path":72,"resourceType":73,"resourceTypeDesc":74,"sizeBytes":75,"sourceHtmlUrl":76},"references\u002Fsignifier-design-decisions.md","REFERENCE","参考文档",3261,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FHDeibler\u002Funiversal-design-principles\u002Fplugins\u002Finteraction-and-control-principles\u002Fskills\u002Faffordance-signifiers\u002Freferences\u002Fsignifier-design-decisions.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",[],[]]