[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6JWB4MMM8Q6Y6CY8WEM4F7W":3,"skill-same:01M6JWB4MMM8Q6Y6CY8WEM4F7W":85},{"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":50,"linkOnly":51,"markdownContent":52,"markdownBody":53,"frontMatter":54,"refName":55,"commitSha":56,"skillDirectory":57,"forksCount":58,"repositoryHtmlUrl":59,"repositoryHomepageUrl":60,"ownerHtmlUrl":61,"ownerBlogUrl":62,"ownerDescription":63,"updatedAt":64,"install":65,"resources":78},"01M6JWB4MMM8Q6Y6CY8WEM4F7W","color-semantic-systems",null,"Use this skill when building or auditing a color system that encodes meaning — status colors (success \u002F warning \u002F error), category colors (department, product line, user segment), brand-role colors (primary, secondary, tertiary). Trigger when designing status badges, picking chart palettes, building a design-system color spec, or fixing inconsistent color use across surfaces. Sub-aspect of `color`; 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\u002Fperception-and-hierarchy-principles\u002Fskills\u002Fcolor-semantic-systems\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,49],"color semantic systems","color","semantic","systems","product line","when","meaning","error","segment","line","trigger","chart","design","across","surfaces","design-system","read","brand","system","product","status","2026-11-10 10:12:30",false,"---\nname: color-semantic-systems\ndescription: 'Use this skill when building or auditing a color system that encodes meaning — status colors (success \u002F warning \u002F error), category colors (department, product line, user segment), brand-role colors (primary, secondary, tertiary). Trigger when designing status badges, picking chart palettes, building a design-system color spec, or fixing inconsistent color use across surfaces. Sub-aspect of `color`; read that first.'\n---\n\n# Building semantic color systems\n\nA semantic color system encodes meaning through color: green means success, red means error, blue means primary brand. Done well, users learn the system once and read every surface fluently. Done poorly, the same color means different things in different places, and users learn nothing reliably.\n\n## What semantic colors should encode\n\nThree useful categories:\n\n### Status \u002F state\n\nConveys the condition of a thing:\n\n- Success \u002F completed \u002F passed\n- Warning \u002F pending \u002F caution\n- Error \u002F failed \u002F overdue\n- Info \u002F neutral \u002F draft\n\nStatus colors map to specific outcome semantics. Use sparingly: every visible status badge is attention spent.\n\n### Category\n\nConveys what kind of thing this is:\n\n- Project tags (a small palette of distinct hues for project labels)\n- Department or team\n- Product line\n- User segment\n\nCategories should use perceptually distinct hues; for ≤ 7 categories, color works well. Beyond that, the user can't reliably remember which color means which.\n\n### Brand role\n\nConveys importance or role within the design:\n\n- Primary brand color → primary CTA\n- Secondary \u002F accent → recommended option, focused state\n- Tertiary → light emphasis (informational badges)\n\nRole colors are about hierarchy more than meaning per se.\n\n## Building a status palette\n\nA workable status set:\n\n```\nsuccess:    hsl(142 70% ...)   green\nwarning:    hsl(38 90% ...)    amber\ndestructive: hsl(0 75% ...)    red\ninfo:       hsl(220 90% ...)   blue\nneutral:    hsl(0 0% ...)      grey\n```\n\nFor each, define multiple lightness stops:\n\n- `*-50` — tinted background (used for badges, alerts, subtle treatments)\n- `*-300` — border or icon\n- `*-500` — primary use (badge color, button color)\n- `*-700` — text color (dark, used on tinted backgrounds)\n- `*-900` — text on dark backgrounds\n\nThe pairing rule: `*-50` background + `*-700` text gives WCAG AA contrast at body size; `*-50` + `*-500` gives AA for large text only.\n\n## Consistency rules for semantic colors\n\nA semantic color system breaks the moment a color means different things in different places. Rules:\n\n- **One color per role.** Don't have \"two reds\" for \"destructive\" and \"important emphasis.\" Pick one role per color.\n- **Status colors stay status.** Don't use the destructive red for marketing emphasis. The user reads it as error.\n- **Category colors stay categorical.** Don't reuse a project-tag color for a status badge.\n- **Document the system.** A color-system spec page that lists every color and its role keeps the team honest.\n\n## Building a category palette\n\nFor project tags, departments, or chart series:\n\n- **5–7 hues maximum** for memorability; beyond that, users can't recall what means what.\n- **Distribute around the color wheel** so adjacent items are visually distinct.\n- **Match lightness and saturation** across the set so no one color dominates.\n- **Test with colorblind simulation** to ensure each hue remains distinct.\n\nA workable 7-color category palette:\n\n```\nhsl(220 70% 55%)    blue\nhsl(160 60% 45%)    teal\nhsl(40 90% 55%)     amber\nhsl(310 60% 55%)    pink\nhsl(10 70% 55%)     red-orange\nhsl(270 50% 55%)    violet\nhsl(85 50% 45%)     olive\n```\n\nEach at similar lightness and saturation; each visually distinct from neighbors.\n\n## Brand role palette\n\nThe minimum useful set:\n\n- **Primary**: filled CTA, focused state, brand emphasis. One hue, used sparingly.\n- **Secondary**: optional alternative emphasis (often used for \"recommended\" highlight).\n- **Accent \u002F tertiary**: micro-emphasis (informational icons, soft highlights).\n\nMost products need only primary plus neutrals; secondary and accent are optional.\n\n## Worked example: a complete semantic system\n\n```css\n:root {\n  \u002F* Brand *\u002F\n  --brand-primary: hsl(220 90% 50%);\n  --brand-primary-fg: white;\n  --brand-primary-hover: hsl(220 90% 45%);\n\n  \u002F* Neutrals (tinted toward brand) *\u002F\n  --neutral-50: hsl(220 6% 98%);\n  --neutral-100: hsl(220 6% 96%);\n  --neutral-200: hsl(220 6% 92%);\n  --neutral-300: hsl(220 6% 85%);\n  --neutral-400: hsl(220 6% 65%);\n  --neutral-500: hsl(220 6% 50%);\n  --neutral-600: hsl(220 6% 40%);\n  --neutral-700: hsl(220 6% 27%);\n  --neutral-800: hsl(220 6% 18%);\n  --neutral-900: hsl(220 6% 9%);\n\n  \u002F* Status *\u002F\n  --success-bg: hsl(142 70% 95%);\n  --success-fg: hsl(142 70% 22%);\n  --success-border: hsl(142 60% 70%);\n\n  --warning-bg: hsl(38 95% 95%);\n  --warning-fg: hsl(38 90% 25%);\n  --warning-border: hsl(38 80% 70%);\n\n  --destructive-bg: hsl(0 80% 95%);\n  --destructive-fg: hsl(0 75% 32%);\n  --destructive-border: hsl(0 60% 70%);\n\n  --info-bg: hsl(210 80% 95%);\n  --info-fg: hsl(210 80% 30%);\n  --info-border: hsl(210 60% 70%);\n}\n```\n\nEvery status pair (bg + fg) clears WCAG AA contrast. The neutrals are tinted toward the brand for cohesion.\n\n## Anti-patterns\n\n- **Brand color reused as primary semantic.** If the brand is red and red also means \"destructive,\" every CTA looks dangerous.\n- **Decorative status color.** A red border around a card with no actual error. Users learn to dismiss the cue.\n- **Inconsistent saturation across statuses.** Bright green success, muted yellow warning, vivid red error. The visual hierarchy jumps; nothing reads coherently.\n- **Too many statuses.** A system with 8 distinct status colors no user can remember.\n- **Categories that compete with statuses.** A \"project\" category color happens to be the same red as your destructive status. Users get confused.\n\n## Heuristics\n\n1. **The \"what does each color mean?\" audit.** List every color in your design system. Can you name a single specific role for each? If yes, the system is coherent. If a color has multiple roles, conflicts are inevitable.\n2. **The grayscale test.** Convert to grayscale. Does the visual hierarchy still work? If yes, color is enhancing, not carrying. If no, you're depending on color alone.\n3. **The colorblind test.** Simulate deuteranopia. Are status colors still distinct? Categories?\n4. **The cross-surface check.** Open three different pages of the product. Does the same status look the same color across all three?\n\n## Related sub-skills\n\n- **`color`** (parent).\n- **`color-accessibility-and-mode`** — accessibility and dark-mode considerations for semantic systems.\n- **`hierarchy-color-and-tone`** — color as a hierarchy axis.\n- **`consistency`** (cognition) — semantic color is a consistency discipline.\n","# Building semantic color systems\n\nA semantic color system encodes meaning through color: green means success, red means error, blue means primary brand. Done well, users learn the system once and read every surface fluently. Done poorly, the same color means different things in different places, and users learn nothing reliably.\n\n## What semantic colors should encode\n\nThree useful categories:\n\n### Status \u002F state\n\nConveys the condition of a thing:\n\n- Success \u002F completed \u002F passed\n- Warning \u002F pending \u002F caution\n- Error \u002F failed \u002F overdue\n- Info \u002F neutral \u002F draft\n\nStatus colors map to specific outcome semantics. Use sparingly: every visible status badge is attention spent.\n\n### Category\n\nConveys what kind of thing this is:\n\n- Project tags (a small palette of distinct hues for project labels)\n- Department or team\n- Product line\n- User segment\n\nCategories should use perceptually distinct hues; for ≤ 7 categories, color works well. Beyond that, the user can't reliably remember which color means which.\n\n### Brand role\n\nConveys importance or role within the design:\n\n- Primary brand color → primary CTA\n- Secondary \u002F accent → recommended option, focused state\n- Tertiary → light emphasis (informational badges)\n\nRole colors are about hierarchy more than meaning per se.\n\n## Building a status palette\n\nA workable status set:\n\n```\nsuccess:    hsl(142 70% ...)   green\nwarning:    hsl(38 90% ...)    amber\ndestructive: hsl(0 75% ...)    red\ninfo:       hsl(220 90% ...)   blue\nneutral:    hsl(0 0% ...)      grey\n```\n\nFor each, define multiple lightness stops:\n\n- `*-50` — tinted background (used for badges, alerts, subtle treatments)\n- `*-300` — border or icon\n- `*-500` — primary use (badge color, button color)\n- `*-700` — text color (dark, used on tinted backgrounds)\n- `*-900` — text on dark backgrounds\n\nThe pairing rule: `*-50` background + `*-700` text gives WCAG AA contrast at body size; `*-50` + `*-500` gives AA for large text only.\n\n## Consistency rules for semantic colors\n\nA semantic color system breaks the moment a color means different things in different places. Rules:\n\n- **One color per role.** Don't have \"two reds\" for \"destructive\" and \"important emphasis.\" Pick one role per color.\n- **Status colors stay status.** Don't use the destructive red for marketing emphasis. The user reads it as error.\n- **Category colors stay categorical.** Don't reuse a project-tag color for a status badge.\n- **Document the system.** A color-system spec page that lists every color and its role keeps the team honest.\n\n## Building a category palette\n\nFor project tags, departments, or chart series:\n\n- **5–7 hues maximum** for memorability; beyond that, users can't recall what means what.\n- **Distribute around the color wheel** so adjacent items are visually distinct.\n- **Match lightness and saturation** across the set so no one color dominates.\n- **Test with colorblind simulation** to ensure each hue remains distinct.\n\nA workable 7-color category palette:\n\n```\nhsl(220 70% 55%)    blue\nhsl(160 60% 45%)    teal\nhsl(40 90% 55%)     amber\nhsl(310 60% 55%)    pink\nhsl(10 70% 55%)     red-orange\nhsl(270 50% 55%)    violet\nhsl(85 50% 45%)     olive\n```\n\nEach at similar lightness and saturation; each visually distinct from neighbors.\n\n## Brand role palette\n\nThe minimum useful set:\n\n- **Primary**: filled CTA, focused state, brand emphasis. One hue, used sparingly.\n- **Secondary**: optional alternative emphasis (often used for \"recommended\" highlight).\n- **Accent \u002F tertiary**: micro-emphasis (informational icons, soft highlights).\n\nMost products need only primary plus neutrals; secondary and accent are optional.\n\n## Worked example: a complete semantic system\n\n```css\n:root {\n  \u002F* Brand *\u002F\n  --brand-primary: hsl(220 90% 50%);\n  --brand-primary-fg: white;\n  --brand-primary-hover: hsl(220 90% 45%);\n\n  \u002F* Neutrals (tinted toward brand) *\u002F\n  --neutral-50: hsl(220 6% 98%);\n  --neutral-100: hsl(220 6% 96%);\n  --neutral-200: hsl(220 6% 92%);\n  --neutral-300: hsl(220 6% 85%);\n  --neutral-400: hsl(220 6% 65%);\n  --neutral-500: hsl(220 6% 50%);\n  --neutral-600: hsl(220 6% 40%);\n  --neutral-700: hsl(220 6% 27%);\n  --neutral-800: hsl(220 6% 18%);\n  --neutral-900: hsl(220 6% 9%);\n\n  \u002F* Status *\u002F\n  --success-bg: hsl(142 70% 95%);\n  --success-fg: hsl(142 70% 22%);\n  --success-border: hsl(142 60% 70%);\n\n  --warning-bg: hsl(38 95% 95%);\n  --warning-fg: hsl(38 90% 25%);\n  --warning-border: hsl(38 80% 70%);\n\n  --destructive-bg: hsl(0 80% 95%);\n  --destructive-fg: hsl(0 75% 32%);\n  --destructive-border: hsl(0 60% 70%);\n\n  --info-bg: hsl(210 80% 95%);\n  --info-fg: hsl(210 80% 30%);\n  --info-border: hsl(210 60% 70%);\n}\n```\n\nEvery status pair (bg + fg) clears WCAG AA contrast. The neutrals are tinted toward the brand for cohesion.\n\n## Anti-patterns\n\n- **Brand color reused as primary semantic.** If the brand is red and red also means \"destructive,\" every CTA looks dangerous.\n- **Decorative status color.** A red border around a card with no actual error. Users learn to dismiss the cue.\n- **Inconsistent saturation across statuses.** Bright green success, muted yellow warning, vivid red error. The visual hierarchy jumps; nothing reads coherently.\n- **Too many statuses.** A system with 8 distinct status colors no user can remember.\n- **Categories that compete with statuses.** A \"project\" category color happens to be the same red as your destructive status. Users get confused.\n\n## Heuristics\n\n1. **The \"what does each color mean?\" audit.** List every color in your design system. Can you name a single specific role for each? If yes, the system is coherent. If a color has multiple roles, conflicts are inevitable.\n2. **The grayscale test.** Convert to grayscale. Does the visual hierarchy still work? If yes, color is enhancing, not carrying. If no, you're depending on color alone.\n3. **The colorblind test.** Simulate deuteranopia. Are status colors still distinct? Categories?\n4. **The cross-surface check.** Open three different pages of the product. Does the same status look the same color across all three?\n\n## Related sub-skills\n\n- **`color`** (parent).\n- **`color-accessibility-and-mode`** — accessibility and dark-mode considerations for semantic systems.\n- **`hierarchy-color-and-tone`** — color as a hierarchy axis.\n- **`consistency`** (cognition) — semantic color is a consistency discipline.\n",{"name":5,"description":7},"main","b0f0a87593c578a7898eccaf1b363f7f87c1f99b","plugins\u002FHDeibler\u002Funiversal-design-principles\u002Fplugins\u002Fperception-and-hierarchy-principles\u002Fskills\u002Fcolor-semantic-systems",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":66,"prompt":76,"zipAvailable":77},[67,70,73],{"tool":68,"command":69},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill color-semantic-systems",{"tool":71,"command":72},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill color-semantic-systems",{"tool":74,"command":75},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill color-semantic-systems","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FHDeibler\u002Funiversal-design-principles\u002Fplugins\u002Fperception-and-hierarchy-principles\u002Fskills\u002Fcolor-semantic-systems\u002FSKILL.md",true,[79],{"path":80,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":83,"sourceHtmlUrl":84},"references\u002Fsemantic-system-cases.md","REFERENCE","参考文档",3497,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FHDeibler\u002Funiversal-design-principles\u002Fplugins\u002Fperception-and-hierarchy-principles\u002Fskills\u002Fcolor-semantic-systems\u002Freferences\u002Fsemantic-system-cases.md",[86,96,104,112,120,128],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":90,"licenseFileUrl":91,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":95},"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":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":90,"licenseFileUrl":100,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":95},"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":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":90,"licenseFileUrl":108,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":95},"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":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":90,"licenseFileUrl":116,"sourceHtmlUrl":117,"categories":118,"keywords":119,"publishedAt":95},"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":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":90,"licenseFileUrl":124,"sourceHtmlUrl":125,"categories":126,"keywords":127,"publishedAt":95},"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":129,"name":130,"nameZh":6,"description":131,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":90,"licenseFileUrl":132,"sourceHtmlUrl":133,"categories":134,"keywords":135,"publishedAt":95},"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",[],[]]