[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MF46JHGQM8TY2TZDZJAEFN":3,"skill-same:01M6MF46JHGQM8TY2TZDZJAEFN":76},{"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":52,"commitSha":53,"skillDirectory":54,"forksCount":55,"repositoryHtmlUrl":56,"repositoryHomepageUrl":57,"ownerHtmlUrl":58,"ownerBlogUrl":59,"ownerDescription":60,"updatedAt":61,"install":62,"resources":75},"01M6MF46JHGQM8TY2TZDZJAEFN","cometchat-android-v6-events",null,"React to what the CometChat Android v6 UI Kit is doing — the CometChatEvents SharedFlow bus (message, call, conversation, group, user and UI events), how to collect it in Compose vs XML Views with correct lifecycle scoping, and when to use UI-Kit events versus Chat SDK listeners. Triggers: 'listen for message sent android cometchat', 'cometchat events android', 'know when a call is accepted', 'react when a group is created', 'sdk listener vs uikit event'.","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-android-v6-events\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],"cometchat android v6 events","android","events","cometchat","listeners","when","lifecycle","correct","chat sdk","collect","event","for","compose","scoping","ui","verified","how","message","jvm","react","kit","how to","conversation","2026-11-10 10:12:30",false,"---\nname: cometchat-android-v6-events\ndescription: \"React to what the CometChat Android v6 UI Kit is doing — the CometChatEvents SharedFlow bus (message, call, conversation, group, user and UI events), how to collect it in Compose vs XML Views with correct lifecycle scoping, and when to use UI-Kit events versus Chat SDK listeners. Triggers: 'listen for message sent android cometchat', 'cometchat events android', 'know when a call is accepted', 'react when a group is created', 'sdk listener vs uikit event'.\"\nlicense: \"MIT\"\ncompatibility: \"Android minSdk >=28; compileSdk >=36; Kotlin >=2.1; AGP >=8.9.1; JVM target 11; com.cometchat:chatuikit-kotlin-android ^6 OR com.cometchat:chatuikit-compose-android ^6 (6.1.x, verified 6.1.1); com.cometchat:chat-sdk-android ^5\"\nmetadata:\n  author: \"CometChat\"\n  version: \"1.0.0\"\n  tags: \"cometchat android events v6 sharedflow lifecycle compose views\"\n---\n\n> **Ground truth:** catalog `android-v6.json` + the live pages `events` (the API reference) and `customization-events`. `CometChatEvents` lives in `chatuikit-core-android` (`com.cometchat.uikit.core.events.CometChatEvents`). Verify symbols against the catalog; fetch the exact sealed-class members from the docs page — the event lists below are a MAP, the page is the manual.\n\n## Companion skills (read first)\n- `cometchat-android-v6-core` — install, credentials, `initFromSettings → login → render`, the fetch map. Assumed here, never repeated.\n- `cometchat-android-v6-{kotlin,compose}-customization` — click\u002Fselection callbacks on a single component (usually the simpler answer than the global bus).\n\n## Use this skill when\n\"tell me when a message is sent\u002Fedited\u002Fdeleted\", \"run code when a call is accepted\", \"update my own badge when a conversation changes\", \"hook into group\u002Fmember changes\", \"what's the difference between an SDK listener and a UI Kit event?\".\n\n## Prerequisites & install\nSame kit + init as `core`. `CometChatEvents` ships in `chatuikit-core-android` (already a transitive dependency of both cohort artifacts) — nothing to add.\n\n## The event bus (BAKED map — fetch the page for each sealed class's members)\nAll events come from the **`CometChatEvents` singleton**; each domain exposes a **`SharedFlow`** of a sealed class:\n\n| Flow | Sealed class | What it covers |\n|---|---|---|\n| `CometChatEvents.messageEvents` | `CometChatMessageEvent` | sent · edited · deleted · read · live reaction · interactive\u002Fcard\u002Fform\u002Fscheduler received |\n| `CometChatEvents.callEvents` | `CometChatCallEvent` | call initiated · accepted · rejected · ended |\n| `CometChatEvents.conversationEvents` | `CometChatConversationEvent` | conversation deleted · updated |\n| `CometChatEvents.groupEvents` | `CometChatGroupEvent` | group created\u002Fdeleted · member changes |\n| `CometChatEvents.userEvents` | `CometChatUserEvent` | user blocked · unblocked |\n| `CometChatEvents.uiEvents` | `CometChatUIEvent` | panel visibility · active-chat changes |\n\nMember shapes are **prefixed too** and the message ones repeat the domain: `CometChatMessageEvent.MessageSent(message, status)` (status `IN_PROGRESS`\u002F`SUCCESS`\u002F`ERROR`) · `MessageEdited` · `MessageDeleted` · `MessageRead` · `TextMessageReceived` · `TypingStarted` · `ReactionAdded`. There is no `.Sent` — it is `.MessageSent`. Import the sealed class from `com.cometchat.uikit.core.events`. Full list: fetch `\u002Fui-kit\u002Fandroid\u002Fcustomization-events.md` (NOT `events.md`, which still teaches the old un-prefixed shape).\n\n## Subscribing per cohort (lifecycle is the whole point)\n**Kotlin XML Views** — collect in `lifecycleScope`; the coroutine is cancelled when the lifecycle owner is destroyed:\n```kotlin\nimport androidx.lifecycle.lifecycleScope       \u002F\u002F in an Activity\u002FFragment\nimport kotlinx.coroutines.launch\nimport com.cometchat.uikit.core.events.CometChatEvents\nimport com.cometchat.uikit.core.events.CometChatMessageEvent\n\nlifecycleScope.launch {\n    CometChatEvents.messageEvents.collect { event ->\n        when (event) {\n            is CometChatMessageEvent.MessageSent -> { \u002F* event.message, event.status *\u002F }\n            is CometChatMessageEvent.MessageDeleted -> { \u002F* event.message *\u002F }\n            else -> Unit\n        }\n    }\n}\n```\n**Jetpack Compose** — collect in `LaunchedEffect`; cancelled when the composable leaves composition:\n```kotlin\nLaunchedEffect(Unit) {\n    CometChatEvents.messageEvents.collect { event -> \u002F* when (event) { ... } *\u002F }\n}\n```\n> **No manual removal needed.** Unlike the old static-listener pattern, `SharedFlow` collection is scoped — do NOT invent an `addListener`\u002F`removeListener` pair for `CometChatEvents`. Just don't collect outside a lifecycle-aware scope (a bare `GlobalScope.launch` IS a leak).\n\n## UI-Kit events vs Chat SDK listeners (pick the right bus)\n| | **UI-Kit events** (`CometChatEvents.*`) | **Chat SDK listeners** (`CometChat.add*Listener`) |\n|---|---|---|\n| Source | UI Kit components (what the UI just did) | the CometChat server (what arrived) |\n| Direction | component → component | server → client |\n| Registration | `.collect {}` in a lifecycle scope | `add*Listener(ID, ...)` + **`remove*Listener(ID)` on teardown** |\n| Use for | \"the user sent\u002Fedited a message\", \"a call was accepted\", panel\u002Factive-chat changes | incoming messages, presence, typing, connection status, incoming calls |\n**Both are needed for a full app.** If you're reacting to something the server pushed while your UI didn't do it, that's an SDK listener (→ `core\u002Freferences\u002Fdocs-map.md` SDK section, or `cometchat-android-v5-sdk`) — and SDK listeners DO require explicit removal in `onDestroy`\u002F`onDispose`\u002F`onCleared`.\n\n## Common pitfalls\nCollecting on a non-lifecycle scope (leak) · inventing `CometChatEvents.addListener`\u002F`removeListener` (doesn't exist — it's a flow) · using a UI-Kit event to detect *incoming* messages (use an SDK message listener) · registering an SDK listener and never removing it · a `when` without an `else` branch breaking on a new sealed member · re-collecting the same flow in several places and double-handling · guessing a sealed-class case name instead of fetching the events page.\n\n## Verify it works\nCompile against the pinned kit (`.\u002Fgradlew :app:assembleDebug   # in YOUR app (npm run verify:fences:android-v6 is a pack-repo gate)`). On device: trigger the action (send\u002Fedit\u002Fdelete a message, accept a call) and confirm your handler runs exactly once; rotate the screen \u002F navigate away and back — no duplicate handling and no crash (proves the scope is right); for any SDK listener you added, confirm the matching remove runs on teardown.\n","> **Ground truth:** catalog `android-v6.json` + the live pages `events` (the API reference) and `customization-events`. `CometChatEvents` lives in `chatuikit-core-android` (`com.cometchat.uikit.core.events.CometChatEvents`). Verify symbols against the catalog; fetch the exact sealed-class members from the docs page — the event lists below are a MAP, the page is the manual.\n\n## Companion skills (read first)\n- `cometchat-android-v6-core` — install, credentials, `initFromSettings → login → render`, the fetch map. Assumed here, never repeated.\n- `cometchat-android-v6-{kotlin,compose}-customization` — click\u002Fselection callbacks on a single component (usually the simpler answer than the global bus).\n\n## Use this skill when\n\"tell me when a message is sent\u002Fedited\u002Fdeleted\", \"run code when a call is accepted\", \"update my own badge when a conversation changes\", \"hook into group\u002Fmember changes\", \"what's the difference between an SDK listener and a UI Kit event?\".\n\n## Prerequisites & install\nSame kit + init as `core`. `CometChatEvents` ships in `chatuikit-core-android` (already a transitive dependency of both cohort artifacts) — nothing to add.\n\n## The event bus (BAKED map — fetch the page for each sealed class's members)\nAll events come from the **`CometChatEvents` singleton**; each domain exposes a **`SharedFlow`** of a sealed class:\n\n| Flow | Sealed class | What it covers |\n|---|---|---|\n| `CometChatEvents.messageEvents` | `CometChatMessageEvent` | sent · edited · deleted · read · live reaction · interactive\u002Fcard\u002Fform\u002Fscheduler received |\n| `CometChatEvents.callEvents` | `CometChatCallEvent` | call initiated · accepted · rejected · ended |\n| `CometChatEvents.conversationEvents` | `CometChatConversationEvent` | conversation deleted · updated |\n| `CometChatEvents.groupEvents` | `CometChatGroupEvent` | group created\u002Fdeleted · member changes |\n| `CometChatEvents.userEvents` | `CometChatUserEvent` | user blocked · unblocked |\n| `CometChatEvents.uiEvents` | `CometChatUIEvent` | panel visibility · active-chat changes |\n\nMember shapes are **prefixed too** and the message ones repeat the domain: `CometChatMessageEvent.MessageSent(message, status)` (status `IN_PROGRESS`\u002F`SUCCESS`\u002F`ERROR`) · `MessageEdited` · `MessageDeleted` · `MessageRead` · `TextMessageReceived` · `TypingStarted` · `ReactionAdded`. There is no `.Sent` — it is `.MessageSent`. Import the sealed class from `com.cometchat.uikit.core.events`. Full list: fetch `\u002Fui-kit\u002Fandroid\u002Fcustomization-events.md` (NOT `events.md`, which still teaches the old un-prefixed shape).\n\n## Subscribing per cohort (lifecycle is the whole point)\n**Kotlin XML Views** — collect in `lifecycleScope`; the coroutine is cancelled when the lifecycle owner is destroyed:\n```kotlin\nimport androidx.lifecycle.lifecycleScope       \u002F\u002F in an Activity\u002FFragment\nimport kotlinx.coroutines.launch\nimport com.cometchat.uikit.core.events.CometChatEvents\nimport com.cometchat.uikit.core.events.CometChatMessageEvent\n\nlifecycleScope.launch {\n    CometChatEvents.messageEvents.collect { event ->\n        when (event) {\n            is CometChatMessageEvent.MessageSent -> { \u002F* event.message, event.status *\u002F }\n            is CometChatMessageEvent.MessageDeleted -> { \u002F* event.message *\u002F }\n            else -> Unit\n        }\n    }\n}\n```\n**Jetpack Compose** — collect in `LaunchedEffect`; cancelled when the composable leaves composition:\n```kotlin\nLaunchedEffect(Unit) {\n    CometChatEvents.messageEvents.collect { event -> \u002F* when (event) { ... } *\u002F }\n}\n```\n> **No manual removal needed.** Unlike the old static-listener pattern, `SharedFlow` collection is scoped — do NOT invent an `addListener`\u002F`removeListener` pair for `CometChatEvents`. Just don't collect outside a lifecycle-aware scope (a bare `GlobalScope.launch` IS a leak).\n\n## UI-Kit events vs Chat SDK listeners (pick the right bus)\n| | **UI-Kit events** (`CometChatEvents.*`) | **Chat SDK listeners** (`CometChat.add*Listener`) |\n|---|---|---|\n| Source | UI Kit components (what the UI just did) | the CometChat server (what arrived) |\n| Direction | component → component | server → client |\n| Registration | `.collect {}` in a lifecycle scope | `add*Listener(ID, ...)` + **`remove*Listener(ID)` on teardown** |\n| Use for | \"the user sent\u002Fedited a message\", \"a call was accepted\", panel\u002Factive-chat changes | incoming messages, presence, typing, connection status, incoming calls |\n**Both are needed for a full app.** If you're reacting to something the server pushed while your UI didn't do it, that's an SDK listener (→ `core\u002Freferences\u002Fdocs-map.md` SDK section, or `cometchat-android-v5-sdk`) — and SDK listeners DO require explicit removal in `onDestroy`\u002F`onDispose`\u002F`onCleared`.\n\n## Common pitfalls\nCollecting on a non-lifecycle scope (leak) · inventing `CometChatEvents.addListener`\u002F`removeListener` (doesn't exist — it's a flow) · using a UI-Kit event to detect *incoming* messages (use an SDK message listener) · registering an SDK listener and never removing it · a `when` without an `else` branch breaking on a new sealed member · re-collecting the same flow in several places and double-handling · guessing a sealed-class case name instead of fetching the events page.\n\n## Verify it works\nCompile against the pinned kit (`.\u002Fgradlew :app:assembleDebug   # in YOUR app (npm run verify:fences:android-v6 is a pack-repo gate)`). On device: trigger the action (send\u002Fedit\u002Fdelete a message, accept a call) and confirm your handler runs exactly once; rotate the screen \u002F navigate away and back — no duplicate handling and no crash (proves the scope is right); for any SDK listener you added, confirm the matching remove runs on teardown.\n",{"name":5,"license":15,"metadata":47,"description":7,"compatibility":51},{"tags":48,"author":49,"version":50},"cometchat android events v6 sharedflow lifecycle compose views","CometChat","1.0.0","Android minSdk >=28; compileSdk >=36; Kotlin >=2.1; AGP >=8.9.1; JVM target 11; com.cometchat:chatuikit-kotlin-android ^6 OR com.cometchat:chatuikit-compose-android ^6 (6.1.x, verified 6.1.1); com.cometchat:chat-sdk-android ^5","main","cebc3dce495d7eb80d3b1d5841f877a4a92e162d","plugins\u002Fcometchat\u002Fcometchat-skills\u002Fskills\u002Fcometchat-android-v6-events",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":63,"prompt":73,"zipAvailable":74},[64,67,70],{"tool":65,"command":66},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill cometchat-android-v6-events",{"tool":68,"command":69},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill cometchat-android-v6-events",{"tool":71,"command":72},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill cometchat-android-v6-events","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fcometchat\u002Fcometchat-skills\u002Fskills\u002Fcometchat-android-v6-events\u002FSKILL.md",true,[],[77,86,94,102,110,118],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":81,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":85},"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":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":90,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":85},"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":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":85},"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":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":85},"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":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":85},"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":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":85},"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",[],[]]