[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MF7RVS4K6RC0GAJP54DX7P":3,"skill-same:01M6MF7RVS4K6RC0GAJP54DX7P":84},{"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":40,"linkOnly":41,"markdownContent":42,"markdownBody":43,"frontMatter":44,"refName":50,"commitSha":51,"skillDirectory":52,"forksCount":53,"repositoryHtmlUrl":54,"repositoryHomepageUrl":55,"ownerHtmlUrl":56,"ownerBlogUrl":57,"ownerDescription":58,"updatedAt":59,"install":60,"resources":73},"01M6MF7RVS4K6RC0GAJP54DX7P","cometchat-angular-v5-placement",null,"Where CometChat components go in an Angular app — the chat shell layout, thread and details panels, search, routing a chat page, and the mobile one-pane fallback. Triggers: 'add a chat page', 'put chat in my dashboard', 'conversation list beside messages', 'open a thread panel', 'chat route', 'make chat responsive'.","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1575,"MIT","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fcometchat\u002Fcometchat-skills\u002Fskills\u002Fcometchat-angular-v5-placement\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39],"cometchat angular v5 placement","cometchat","angular","layout","make","add","responsive","my","go","list","verified","mobile","app","dashboard","route","components","open","panels","messages","search","conversation","2026-11-10 10:12:30",false,"---\nname: cometchat-angular-v5-placement\ndescription: \"Where CometChat components go in an Angular app — the chat shell layout, thread and details panels, search, routing a chat page, and the mobile one-pane fallback. Triggers: 'add a chat page', 'put chat in my dashboard', 'conversation list beside messages', 'open a thread panel', 'chat route', 'make chat responsive'.\"\nlicense: \"MIT\"\ncompatibility: \"@cometchat\u002Fchat-uikit-angular ^5 (5.1.0–5.2.2 verified); Angular 17-21\"\nmetadata:\n  author: \"CometChat\"\n  version: \"1.0.0\"\n  tags: \"cometchat angular placement v5 layout routing panels responsive shell\"\n---\n\n> **Ground truth:** `@cometchat\u002Fchat-uikit-angular@5` (5.1.0–5.2.2 verified). Uses only components in the `angular-v5` catalog. The layouts here are built FROM the live task guides — `{DOCS_BASE}\u002Fui-kit\u002Fangular\u002Fguides\u002Fnew-chat.md`, `\u002Fguides\u002Fgroup-chat.md`, `\u002Fguides\u002Fthreaded-messages.md`, `\u002Fguides\u002Fsearch-messages.md`, plus `\u002Fangular-conversation`, `\u002Fangular-one-to-one-chat`, `\u002Fangular-tab-based-chat` and `\u002Fapi-reference\u002Fchat-state-service.md`; base + paths in `cometchat-angular-v5-core\u002Freferences\u002Fdocs-map.md`. Fetch layout-specific inputs from the component's `.md` twin rather than reading the installed bundle. **APPEND to the user's app — additive only** (`RULES.md`).\n\n## Companion skills (read first)\n- `cometchat-angular-v5-core` — install, credentials, `init→login→render`, and `references\u002Flayout.md` for the sizing rules this skill assumes.\n- `cometchat-angular-v5-components` — which component to use and its real inputs\u002Foutputs.\n\n## Use this skill when\nDeciding **where** chat lives: a dedicated route, a panel inside an existing dashboard, a widget, or the full multi-pane app.\n\n## Pick a placement\n| Ask | Placement | Recipe |\n| --- | --- | --- |\n| \"add chat to my app\" (unscoped) | **Core surface** — list + message pane, thread and search as panels | `references\u002Fcore-surface.md` |\n| \"the whole chat app\" — users, groups, calls, details | **Combined app** — tabbed selector + panels | `references\u002Fcombined-app.md` |\n| \"chat inside my dashboard\" | Embed the core surface in an existing layout slot | below |\n| \"a support widget\" | Single conversation — header + list + composer, no list pane | below |\n\nDefault to the **core surface** for an unscoped request. Grow to the combined app only when asked.\n\n## Active item — use ChatStateService, not your own field\nAngular ships an injectable source of truth for the active chat. It exposes **signals** and **observables**; prefer signals in templates. This is what satisfies \"the selected row is visually reflected\" and makes panel-close round-trip correctly.\n\n```ts\nimport { Component, computed, inject } from '@angular\u002Fcore';\nimport { CometChat } from '@cometchat\u002Fchat-sdk-javascript';\nimport { ChatStateService, CometChatUIKitConstants } from '@cometchat\u002Fchat-uikit-angular';\n\n@Component({ selector: 'app-chat-shell', standalone: true, template: '' })\nexport class ChatShellComponent {\n  readonly chatState = inject(ChatStateService);\n  \u002F\u002F The service's signals are `T | null`, but the kit's inputs are optional\n  \u002F\u002F (`T | undefined`) — bind the raw signal and Angular's strict template check\n  \u002F\u002F rejects it. Normalise once, here.\n  readonly activeUser = computed(() => this.chatState.activeUser() ?? undefined);\n  readonly activeGroup = computed(() => this.chatState.activeGroup() ?? undefined);\n\n  \u002F\u002F (itemClick) emits a Conversation — resolve the subject, then branch on its TYPE.\n  \u002F\u002F A Conversation has no getGuid(), so duck-typing routes groups into the user slot\n  \u002F\u002F and the message pane throws \"getUid is not a function\". See references\u002Fcore-surface.md.\n  open(conversation: CometChat.Conversation) {\n    const subject = conversation.getConversationWith();\n    if (conversation.getConversationType() === CometChatUIKitConstants.MessageReceiverType.group) {\n      this.chatState.setActiveGroup(subject as CometChat.Group);\n    } else {\n      this.chatState.setActiveUser(subject as CometChat.User);\n    }\n  }\n  closeChat() { this.chatState.clearActiveChat(); }\n}\n```\nAvailable: `activeUser` `activeGroup` `activeConversation` (signals) · `activeUser$` `activeGroup$` `activeConversation$` (observables) · `setActiveUser\u002FGroup\u002FConversation` · `getActiveChatEntity()` · `clearActiveChat()`.\n\nKeeping a separate `selected` field alongside this is how the two drift and the list stops highlighting the open conversation.\n\n## Panels are columns, not overlays\nThread, user\u002Fgroup details and search are **additional columns in the same flex shell**. Opening one must not resize or remount the message list, and closing must return to the exact prior layout.\n\n```html\n\u003Cdiv class=\"cc-shell\">\n  \u003Caside class=\"cc-side\">\u003C!-- list -->\u003C\u002Faside>\n  \u003Cmain class=\"cc-main\">\u003C!-- header · list · composer -->\u003C\u002Fmain>\n  \u003Caside class=\"cc-panel\" *ngIf=\"threadParent()\">\u003C!-- thread -->\u003C\u002Faside>\n\u003C\u002Fdiv>\n```\n```css\n.cc-shell { display: flex; height: 100dvh; width: 100%; min-height: 0; overflow: hidden; }\n.cc-side  { width: 320px; min-height: 0; overflow: hidden; }\n.cc-main  { flex: 1; display: flex; flex-direction: column; min-height: 0; overflow: hidden; }\n.cc-panel { width: 360px; min-height: 0; overflow: hidden; border-left: 1px solid var(--cometchat-border-color-default); }\n```\n`min-height: 0` on every column is required — see core's `references\u002Flayout.md`.\n\n## Routing a chat page\n```ts\n\u002F\u002F app.routes.ts\nimport { Routes } from '@angular\u002Frouter';\nexport const routes: Routes = [\n  { path: 'chat', loadComponent: () => import('.\u002Fchat\u002Fchat.component').then(m => m.ChatComponent) },\n  { path: 'chat\u002F:uid', loadComponent: () => import('.\u002Fchat\u002Fchat.component').then(m => m.ChatComponent) },\n];\n```\nTwo rules:\n1. **Do not re-init CometChat per route.** Init happens once at bootstrap (core). A route guard may await login, never re-init.\n2. **Tear down on leave.** Every subscription in the chat component needs `takeUntil(destroy$)` in `ngOnDestroy`, or navigating away leaks listeners that keep firing.\n\nReading `:uid` into the active chat belongs in the component's `ngOnInit`, resolved through `ChatStateService`.\n\n## Embedding in an existing dashboard\nGive the host slot a resolved height and let the shell fill it — do **not** put the kit inside a container sized by its content.\n```css\n.dashboard-chat-slot { height: calc(100dvh - var(--app-header-height)); min-height: 0; display: flex; }\n```\nIf the surrounding app uses `transform` or `filter` on an ancestor, the height chain breaks — core's `layout.md` covers why.\n\n## Mobile — one pane at a time (mandatory for any multi-pane layout)\nBelow ~768px show the list **or** the conversation, never both.\n```html\n\u003Cdiv class=\"cc-shell\">\n  \u003Caside class=\"cc-side\" [hidden]=\"isMobile() && hasActiveChat()\">\u003C!-- list -->\u003C\u002Faside>\n  \u003Cmain class=\"cc-main\" [hidden]=\"isMobile() && !hasActiveChat()\">\u003C!-- message pane -->\u003C\u002Fmain>\n\u003C\u002Fdiv>\n```\nDrive `[hidden]` from the same `ChatStateService` state as the message components, and give the mobile conversation view a back control that calls `clearActiveChat()`. A multi-pane layout squeezed onto a phone is a defect, not a style choice.\n\n## Common pitfalls\n1. **Two sources of truth** — a local `selected` field plus `ChatStateService`. They drift; the list stops highlighting.\n2. **Panels as overlays** — thread rendered over the list instead of beside it, so closing does not restore layout.\n3. **Re-initialising per route** — init belongs at bootstrap, once.\n4. **No teardown on navigate** — leaked listeners keep firing against a destroyed view.\n5. **Unsized embed slot** — the kit collapses to zero height inside a content-sized container.\n6. **Both panes on mobile** — unusable at 375px.\n\n## Verify it works\nClicking a conversation opens it AND highlights the row · opening a thread does not resize the message list · closing returns to the exact prior layout · navigating away and back does not duplicate messages · at 375px only one pane is visible with a working back control · no console errors.\n\n## Explain what you built (REQUIRED close)\nTell the developer what changed, naming the files: the layout you built — which panes exist, and how the mobile one-pane fallback behaves. Flag anything dev-only as dev-only, and say what you did **not** touch — this is additive.\n\n**Then offer these THREE options as a SELECTABLE choice and WAIT for the pick — never auto-continue (`RULES.md` §19):**\n1. **Add another feature** → a feature from `features.angular-v5.json`, or growing the surface — users\u002Fgroups tabs, a details panel, calling. **Never offer an `auto` entry** (reactions, mentions, receipts, typing, media) — those are core in v5 and already on.\n2. **Customize theming** → `cometchat-angular-v5-customization`.\n3. **Test it manually** → do nothing further; hand back so the user runs it.\n","> **Ground truth:** `@cometchat\u002Fchat-uikit-angular@5` (5.1.0–5.2.2 verified). Uses only components in the `angular-v5` catalog. The layouts here are built FROM the live task guides — `{DOCS_BASE}\u002Fui-kit\u002Fangular\u002Fguides\u002Fnew-chat.md`, `\u002Fguides\u002Fgroup-chat.md`, `\u002Fguides\u002Fthreaded-messages.md`, `\u002Fguides\u002Fsearch-messages.md`, plus `\u002Fangular-conversation`, `\u002Fangular-one-to-one-chat`, `\u002Fangular-tab-based-chat` and `\u002Fapi-reference\u002Fchat-state-service.md`; base + paths in `cometchat-angular-v5-core\u002Freferences\u002Fdocs-map.md`. Fetch layout-specific inputs from the component's `.md` twin rather than reading the installed bundle. **APPEND to the user's app — additive only** (`RULES.md`).\n\n## Companion skills (read first)\n- `cometchat-angular-v5-core` — install, credentials, `init→login→render`, and `references\u002Flayout.md` for the sizing rules this skill assumes.\n- `cometchat-angular-v5-components` — which component to use and its real inputs\u002Foutputs.\n\n## Use this skill when\nDeciding **where** chat lives: a dedicated route, a panel inside an existing dashboard, a widget, or the full multi-pane app.\n\n## Pick a placement\n| Ask | Placement | Recipe |\n| --- | --- | --- |\n| \"add chat to my app\" (unscoped) | **Core surface** — list + message pane, thread and search as panels | `references\u002Fcore-surface.md` |\n| \"the whole chat app\" — users, groups, calls, details | **Combined app** — tabbed selector + panels | `references\u002Fcombined-app.md` |\n| \"chat inside my dashboard\" | Embed the core surface in an existing layout slot | below |\n| \"a support widget\" | Single conversation — header + list + composer, no list pane | below |\n\nDefault to the **core surface** for an unscoped request. Grow to the combined app only when asked.\n\n## Active item — use ChatStateService, not your own field\nAngular ships an injectable source of truth for the active chat. It exposes **signals** and **observables**; prefer signals in templates. This is what satisfies \"the selected row is visually reflected\" and makes panel-close round-trip correctly.\n\n```ts\nimport { Component, computed, inject } from '@angular\u002Fcore';\nimport { CometChat } from '@cometchat\u002Fchat-sdk-javascript';\nimport { ChatStateService, CometChatUIKitConstants } from '@cometchat\u002Fchat-uikit-angular';\n\n@Component({ selector: 'app-chat-shell', standalone: true, template: '' })\nexport class ChatShellComponent {\n  readonly chatState = inject(ChatStateService);\n  \u002F\u002F The service's signals are `T | null`, but the kit's inputs are optional\n  \u002F\u002F (`T | undefined`) — bind the raw signal and Angular's strict template check\n  \u002F\u002F rejects it. Normalise once, here.\n  readonly activeUser = computed(() => this.chatState.activeUser() ?? undefined);\n  readonly activeGroup = computed(() => this.chatState.activeGroup() ?? undefined);\n\n  \u002F\u002F (itemClick) emits a Conversation — resolve the subject, then branch on its TYPE.\n  \u002F\u002F A Conversation has no getGuid(), so duck-typing routes groups into the user slot\n  \u002F\u002F and the message pane throws \"getUid is not a function\". See references\u002Fcore-surface.md.\n  open(conversation: CometChat.Conversation) {\n    const subject = conversation.getConversationWith();\n    if (conversation.getConversationType() === CometChatUIKitConstants.MessageReceiverType.group) {\n      this.chatState.setActiveGroup(subject as CometChat.Group);\n    } else {\n      this.chatState.setActiveUser(subject as CometChat.User);\n    }\n  }\n  closeChat() { this.chatState.clearActiveChat(); }\n}\n```\nAvailable: `activeUser` `activeGroup` `activeConversation` (signals) · `activeUser$` `activeGroup$` `activeConversation$` (observables) · `setActiveUser\u002FGroup\u002FConversation` · `getActiveChatEntity()` · `clearActiveChat()`.\n\nKeeping a separate `selected` field alongside this is how the two drift and the list stops highlighting the open conversation.\n\n## Panels are columns, not overlays\nThread, user\u002Fgroup details and search are **additional columns in the same flex shell**. Opening one must not resize or remount the message list, and closing must return to the exact prior layout.\n\n```html\n\u003Cdiv class=\"cc-shell\">\n  \u003Caside class=\"cc-side\">\u003C!-- list -->\u003C\u002Faside>\n  \u003Cmain class=\"cc-main\">\u003C!-- header · list · composer -->\u003C\u002Fmain>\n  \u003Caside class=\"cc-panel\" *ngIf=\"threadParent()\">\u003C!-- thread -->\u003C\u002Faside>\n\u003C\u002Fdiv>\n```\n```css\n.cc-shell { display: flex; height: 100dvh; width: 100%; min-height: 0; overflow: hidden; }\n.cc-side  { width: 320px; min-height: 0; overflow: hidden; }\n.cc-main  { flex: 1; display: flex; flex-direction: column; min-height: 0; overflow: hidden; }\n.cc-panel { width: 360px; min-height: 0; overflow: hidden; border-left: 1px solid var(--cometchat-border-color-default); }\n```\n`min-height: 0` on every column is required — see core's `references\u002Flayout.md`.\n\n## Routing a chat page\n```ts\n\u002F\u002F app.routes.ts\nimport { Routes } from '@angular\u002Frouter';\nexport const routes: Routes = [\n  { path: 'chat', loadComponent: () => import('.\u002Fchat\u002Fchat.component').then(m => m.ChatComponent) },\n  { path: 'chat\u002F:uid', loadComponent: () => import('.\u002Fchat\u002Fchat.component').then(m => m.ChatComponent) },\n];\n```\nTwo rules:\n1. **Do not re-init CometChat per route.** Init happens once at bootstrap (core). A route guard may await login, never re-init.\n2. **Tear down on leave.** Every subscription in the chat component needs `takeUntil(destroy$)` in `ngOnDestroy`, or navigating away leaks listeners that keep firing.\n\nReading `:uid` into the active chat belongs in the component's `ngOnInit`, resolved through `ChatStateService`.\n\n## Embedding in an existing dashboard\nGive the host slot a resolved height and let the shell fill it — do **not** put the kit inside a container sized by its content.\n```css\n.dashboard-chat-slot { height: calc(100dvh - var(--app-header-height)); min-height: 0; display: flex; }\n```\nIf the surrounding app uses `transform` or `filter` on an ancestor, the height chain breaks — core's `layout.md` covers why.\n\n## Mobile — one pane at a time (mandatory for any multi-pane layout)\nBelow ~768px show the list **or** the conversation, never both.\n```html\n\u003Cdiv class=\"cc-shell\">\n  \u003Caside class=\"cc-side\" [hidden]=\"isMobile() && hasActiveChat()\">\u003C!-- list -->\u003C\u002Faside>\n  \u003Cmain class=\"cc-main\" [hidden]=\"isMobile() && !hasActiveChat()\">\u003C!-- message pane -->\u003C\u002Fmain>\n\u003C\u002Fdiv>\n```\nDrive `[hidden]` from the same `ChatStateService` state as the message components, and give the mobile conversation view a back control that calls `clearActiveChat()`. A multi-pane layout squeezed onto a phone is a defect, not a style choice.\n\n## Common pitfalls\n1. **Two sources of truth** — a local `selected` field plus `ChatStateService`. They drift; the list stops highlighting.\n2. **Panels as overlays** — thread rendered over the list instead of beside it, so closing does not restore layout.\n3. **Re-initialising per route** — init belongs at bootstrap, once.\n4. **No teardown on navigate** — leaked listeners keep firing against a destroyed view.\n5. **Unsized embed slot** — the kit collapses to zero height inside a content-sized container.\n6. **Both panes on mobile** — unusable at 375px.\n\n## Verify it works\nClicking a conversation opens it AND highlights the row · opening a thread does not resize the message list · closing returns to the exact prior layout · navigating away and back does not duplicate messages · at 375px only one pane is visible with a working back control · no console errors.\n\n## Explain what you built (REQUIRED close)\nTell the developer what changed, naming the files: the layout you built — which panes exist, and how the mobile one-pane fallback behaves. Flag anything dev-only as dev-only, and say what you did **not** touch — this is additive.\n\n**Then offer these THREE options as a SELECTABLE choice and WAIT for the pick — never auto-continue (`RULES.md` §19):**\n1. **Add another feature** → a feature from `features.angular-v5.json`, or growing the surface — users\u002Fgroups tabs, a details panel, calling. **Never offer an `auto` entry** (reactions, mentions, receipts, typing, media) — those are core in v5 and already on.\n2. **Customize theming** → `cometchat-angular-v5-customization`.\n3. **Test it manually** → do nothing further; hand back so the user runs it.\n",{"name":5,"license":15,"metadata":45,"description":7,"compatibility":49},{"tags":46,"author":47,"version":48},"cometchat angular placement v5 layout routing panels responsive shell","CometChat","1.0.0","@cometchat\u002Fchat-uikit-angular ^5 (5.1.0–5.2.2 verified); Angular 17-21","main","cebc3dce495d7eb80d3b1d5841f877a4a92e162d","plugins\u002Fcometchat\u002Fcometchat-skills\u002Fskills\u002Fcometchat-angular-v5-placement",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":61,"prompt":71,"zipAvailable":72},[62,65,68],{"tool":63,"command":64},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill cometchat-angular-v5-placement",{"tool":66,"command":67},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill cometchat-angular-v5-placement",{"tool":69,"command":70},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill cometchat-angular-v5-placement","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fcometchat\u002Fcometchat-skills\u002Fskills\u002Fcometchat-angular-v5-placement\u002FSKILL.md",true,[74,80],{"path":75,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":78,"sourceHtmlUrl":79},"references\u002Fcombined-app.md","REFERENCE","参考文档",9053,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fcometchat\u002Fcometchat-skills\u002Fskills\u002Fcometchat-angular-v5-placement\u002Freferences\u002Fcombined-app.md",{"path":81,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":82,"sourceHtmlUrl":83},"references\u002Fcore-surface.md",10676,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fcometchat\u002Fcometchat-skills\u002Fskills\u002Fcometchat-angular-v5-placement\u002Freferences\u002Fcore-surface.md",[85,94,102,110,118,126],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":89,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":93},"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.","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":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":98,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":93},"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":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":106,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":93},"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":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":114,"sourceHtmlUrl":115,"categories":116,"keywords":117,"publishedAt":93},"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":119,"name":120,"nameZh":6,"description":121,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":122,"sourceHtmlUrl":123,"categories":124,"keywords":125,"publishedAt":93},"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":127,"name":128,"nameZh":6,"description":129,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":130,"sourceHtmlUrl":131,"categories":132,"keywords":133,"publishedAt":93},"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",[],[]]