[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MF2BNM538NDQSTGXBEK7HV":3,"skill-same:01M6MF2BNM538NDQSTGXBEK7HV":88},{"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":31,"publishedAt":54,"linkOnly":55,"markdownContent":56,"markdownBody":57,"frontMatter":58,"refName":64,"commitSha":65,"skillDirectory":66,"forksCount":67,"repositoryHtmlUrl":68,"repositoryHomepageUrl":69,"ownerHtmlUrl":70,"ownerBlogUrl":71,"ownerDescription":72,"updatedAt":73,"install":74,"resources":87},"01M6MF2BNM538NDQSTGXBEK7HV","cometchat-analytics",null,"See what your chat is doing — pull usage & message metrics via REST, stream real-time events to your data\u002Fobservability stack via webhooks, monitor client-side errors & the init\u002Flogin path, and read push\u002Fcall logs. Cross-family: metrics\u002Fwebhooks are server-side; client error monitoring wires per family. Triggers: 'chat analytics', 'usage metrics', 'message volume', 'monitor cometchat', 'observability', 'send chat events to datadog\u002Fsegment\u002Fbigquery', 'track delivery', 'error monitoring for chat', 'dashboards for chat'.","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-analytics\u002FSKILL.md",[18,23,26],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000013","分析与可视化",{"categoryNo":27,"categoryName":28,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52,53],"analytics","cometchat","cometchat analytics","listeners","init","send","track","login","errors","error","loki","volume","time","delivery","message","read","stack","api","server","monitoring","logs","grafana","2026-11-10 10:12:30",false,"---\nname: cometchat-analytics\ndescription: \"See what your chat is doing — pull usage & message metrics via REST, stream real-time events to your data\u002Fobservability stack via webhooks, monitor client-side errors & the init\u002Flogin path, and read push\u002Fcall logs. Cross-family: metrics\u002Fwebhooks are server-side; client error monitoring wires per family. Triggers: 'chat analytics', 'usage metrics', 'message volume', 'monitor cometchat', 'observability', 'send chat events to datadog\u002Fsegment\u002Fbigquery', 'track delivery', 'error monitoring for chat', 'dashboards for chat'.\"\nlicense: \"MIT\"\ncompatibility: \"CometChat Metrics REST API (usage · message) · Webhooks · Notification\u002FCall logs · on-prem Prometheus\u002FGrafana\u002FLoki. Client error monitoring via each family's error boundary \u002F listeners.\"\nmetadata:\n  author: \"CometChat\"\n  version: \"1.0.0\"\n  tags: \"cometchat analytics observability metrics webhooks monitoring datadog sentry dashboards\"\n---\n\n> **Ground truth:** shapes are FETCHED from the live docs — `{DOCS_BASE}\u002Frest-api\u002Fmetrics\u002Fusage-metrics`, `\u002Frest-api\u002Fmetrics\u002Fmessage-metrics`, `\u002Ffundamentals\u002Fwebhooks` (+ `\u002Frest-api\u002Fmanagement-apis\u002Fwebhooks\u002Foverview`), `\u002Fnotifications\u002Flogs`, `\u002Frest-api\u002Fcalls-apis\u002Fget-call`, and on-prem `\u002Fon-premise-deployment\u002Fdocker\u002Fmonitoring`. `DOCS_BASE = https:\u002F\u002Fwww.cometchat.com\u002Fdocs`; append `.md`. Verify each metric field \u002F event name against the docs before charting it; don't invent a metric.\n\n## Use this skill when\nYou need visibility into chat: product analytics (DAU, messages, retention), an ops\u002Fobservability signal (delivery, errors, latency), or feeding chat events into an existing warehouse\u002Fmonitoring stack.\n\n## Three layers of visibility\n| Layer | Source | Use it for |\n| --- | --- | --- |\n| **Aggregate metrics** | Metrics REST API (usage + message) | dashboards, MAU\u002FDAU, message volume, growth |\n| **Real-time events** | Webhooks | stream every message\u002Fuser\u002Fgroup\u002Fcall event to your pipeline |\n| **Client health** | your error monitor + the kit's error boundary\u002Flisteners | init\u002Flogin failures, render errors, UX latency |\n\n## 1. Aggregate metrics (REST, server-side)\n- **Usage metrics** (`{DOCS_BASE}\u002Frest-api\u002Fmetrics\u002Fusage-metrics`) — active users and usage over time.\n- **Message metrics** (`{DOCS_BASE}\u002Frest-api\u002Fmetrics\u002Fmessage-metrics`) — message volume\u002Fcounts.\n- **Call metrics** — per-call detail incl. participant metrics via `{DOCS_BASE}\u002Frest-api\u002Fcalls-apis\u002Fget-call`.\nCall these from a server job with the **REST API Key** (never client-side), on a schedule, into your BI tool. Fetch the exact query params + response fields from each page before building the report.\n\n## 2. Real-time events → your stack (webhooks)\nWebhooks POST an HTTPS notification to your server on message \u002F user \u002F group \u002F call events (`{DOCS_BASE}\u002Ffundamentals\u002Fwebhooks`; configure via `\u002Frest-api\u002Fmanagement-apis\u002Fwebhooks\u002Foverview`). This is how you get chat into **Segment \u002F BigQuery \u002F Snowflake \u002F Datadog \u002F a data lake** in real time:\n1. Stand up an HTTPS endpoint (returns 200 to ack). Secure it with the **Basic Auth** credentials CometChat sends on every webhook request (`{DOCS_BASE}\u002Ffundamentals\u002Fwebhooks` — the docs describe Basic Auth only, with no payload-signature scheme, so validate the `Authorization` header rather than looking for an HMAC signature).\n2. Subscribe to the events you need (don't fan out everything if you only need message.sent).\n3. Transform + forward to your warehouse\u002Fobservability sink; make the handler idempotent and fast (queue heavy work).\nThe same webhook stream doubles as a **tamper-evident audit log** for `cometchat-compliance`.\n\n## 3. Client-side error & performance monitoring (per family)\nThe metrics API won't tell you a user's chat failed to load — instrument the client:\n- **Capture kit render errors** — on the React families via the error boundary's hook (React v7: `CometChatErrorBoundary` `onError`; Angular\u002FRN have the equivalent); on iOS\u002FAndroid\u002FFlutter (no error-boundary construct) via the SDK error listeners \u002F the kit's error-state views. Forward to Sentry\u002FDatadog with context.\n- **Instrument the critical path** — wrap init, the token fetch, and login in spans\u002Fbreadcrumbs; a spike in login failures is your earliest incident signal (often Region or token issues).\n- **Listen for connection state** — the SDK's connection\u002Fwebsocket listeners tell you when clients drop; count reconnects.\n- **Don't log secrets or message bodies** to your monitor — log UIDs\u002Fevent types\u002Flatencies, not content (privacy + `cometchat-compliance`).\nWire these through the resolved family's `-core`\u002F`-production`\u002F`-troubleshooting` skills.\n\n## 4. Delivery & call logs\n- **Push delivery logs** (`{DOCS_BASE}\u002Fnotifications\u002Flogs`) — FCM\u002FAPNs\u002Femail\u002FSMS delivery, ~14-day retention; enable when diagnosing \"notifications not arriving\" and export before they age out.\n- **Call logs** — the Calls REST APIs for per-call quality\u002Fparticipant metrics.\n\n## 5. Self-host observability\nOn-prem ships **Prometheus + Grafana + Loki + Promtail** (`{DOCS_BASE}\u002Fon-premise-deployment\u002Fdocker\u002Fmonitoring`): service metrics, dashboards, alerts, and centralized logs — wire alerts (P95 latency, error rate, WS capacity) to your on-call. SaaS customers use the Metrics API + webhooks instead.\n\n## Common pitfalls\n1. **Metrics API called client-side** — it needs the REST API Key; server only.\n2. **Webhook handler slow or non-idempotent** — retries pile up; ack fast, queue the work, dedupe.\n3. **Charting an invented metric** — fetch the real fields from the metrics pages.\n4. **Logging message content to your monitor** — privacy\u002Fcompliance risk; log metadata, not bodies.\n5. **No client error monitoring** — you'll hear about outages from users, not dashboards; wire the error boundary + login-path spans.\n6. **Relying on push logs after they age out** — export within the retention window.\n\n## Verify it works\nUsage\u002Fmessage metrics return real numbers into your dashboard · a test message triggers your webhook and lands in your warehouse\u002Fmonitor · a forced init\u002Flogin failure shows up in your error monitor with context · push\u002Fcall logs are readable when needed · (on-prem) Grafana shows the services and alerts fire.\n","> **Ground truth:** shapes are FETCHED from the live docs — `{DOCS_BASE}\u002Frest-api\u002Fmetrics\u002Fusage-metrics`, `\u002Frest-api\u002Fmetrics\u002Fmessage-metrics`, `\u002Ffundamentals\u002Fwebhooks` (+ `\u002Frest-api\u002Fmanagement-apis\u002Fwebhooks\u002Foverview`), `\u002Fnotifications\u002Flogs`, `\u002Frest-api\u002Fcalls-apis\u002Fget-call`, and on-prem `\u002Fon-premise-deployment\u002Fdocker\u002Fmonitoring`. `DOCS_BASE = https:\u002F\u002Fwww.cometchat.com\u002Fdocs`; append `.md`. Verify each metric field \u002F event name against the docs before charting it; don't invent a metric.\n\n## Use this skill when\nYou need visibility into chat: product analytics (DAU, messages, retention), an ops\u002Fobservability signal (delivery, errors, latency), or feeding chat events into an existing warehouse\u002Fmonitoring stack.\n\n## Three layers of visibility\n| Layer | Source | Use it for |\n| --- | --- | --- |\n| **Aggregate metrics** | Metrics REST API (usage + message) | dashboards, MAU\u002FDAU, message volume, growth |\n| **Real-time events** | Webhooks | stream every message\u002Fuser\u002Fgroup\u002Fcall event to your pipeline |\n| **Client health** | your error monitor + the kit's error boundary\u002Flisteners | init\u002Flogin failures, render errors, UX latency |\n\n## 1. Aggregate metrics (REST, server-side)\n- **Usage metrics** (`{DOCS_BASE}\u002Frest-api\u002Fmetrics\u002Fusage-metrics`) — active users and usage over time.\n- **Message metrics** (`{DOCS_BASE}\u002Frest-api\u002Fmetrics\u002Fmessage-metrics`) — message volume\u002Fcounts.\n- **Call metrics** — per-call detail incl. participant metrics via `{DOCS_BASE}\u002Frest-api\u002Fcalls-apis\u002Fget-call`.\nCall these from a server job with the **REST API Key** (never client-side), on a schedule, into your BI tool. Fetch the exact query params + response fields from each page before building the report.\n\n## 2. Real-time events → your stack (webhooks)\nWebhooks POST an HTTPS notification to your server on message \u002F user \u002F group \u002F call events (`{DOCS_BASE}\u002Ffundamentals\u002Fwebhooks`; configure via `\u002Frest-api\u002Fmanagement-apis\u002Fwebhooks\u002Foverview`). This is how you get chat into **Segment \u002F BigQuery \u002F Snowflake \u002F Datadog \u002F a data lake** in real time:\n1. Stand up an HTTPS endpoint (returns 200 to ack). Secure it with the **Basic Auth** credentials CometChat sends on every webhook request (`{DOCS_BASE}\u002Ffundamentals\u002Fwebhooks` — the docs describe Basic Auth only, with no payload-signature scheme, so validate the `Authorization` header rather than looking for an HMAC signature).\n2. Subscribe to the events you need (don't fan out everything if you only need message.sent).\n3. Transform + forward to your warehouse\u002Fobservability sink; make the handler idempotent and fast (queue heavy work).\nThe same webhook stream doubles as a **tamper-evident audit log** for `cometchat-compliance`.\n\n## 3. Client-side error & performance monitoring (per family)\nThe metrics API won't tell you a user's chat failed to load — instrument the client:\n- **Capture kit render errors** — on the React families via the error boundary's hook (React v7: `CometChatErrorBoundary` `onError`; Angular\u002FRN have the equivalent); on iOS\u002FAndroid\u002FFlutter (no error-boundary construct) via the SDK error listeners \u002F the kit's error-state views. Forward to Sentry\u002FDatadog with context.\n- **Instrument the critical path** — wrap init, the token fetch, and login in spans\u002Fbreadcrumbs; a spike in login failures is your earliest incident signal (often Region or token issues).\n- **Listen for connection state** — the SDK's connection\u002Fwebsocket listeners tell you when clients drop; count reconnects.\n- **Don't log secrets or message bodies** to your monitor — log UIDs\u002Fevent types\u002Flatencies, not content (privacy + `cometchat-compliance`).\nWire these through the resolved family's `-core`\u002F`-production`\u002F`-troubleshooting` skills.\n\n## 4. Delivery & call logs\n- **Push delivery logs** (`{DOCS_BASE}\u002Fnotifications\u002Flogs`) — FCM\u002FAPNs\u002Femail\u002FSMS delivery, ~14-day retention; enable when diagnosing \"notifications not arriving\" and export before they age out.\n- **Call logs** — the Calls REST APIs for per-call quality\u002Fparticipant metrics.\n\n## 5. Self-host observability\nOn-prem ships **Prometheus + Grafana + Loki + Promtail** (`{DOCS_BASE}\u002Fon-premise-deployment\u002Fdocker\u002Fmonitoring`): service metrics, dashboards, alerts, and centralized logs — wire alerts (P95 latency, error rate, WS capacity) to your on-call. SaaS customers use the Metrics API + webhooks instead.\n\n## Common pitfalls\n1. **Metrics API called client-side** — it needs the REST API Key; server only.\n2. **Webhook handler slow or non-idempotent** — retries pile up; ack fast, queue the work, dedupe.\n3. **Charting an invented metric** — fetch the real fields from the metrics pages.\n4. **Logging message content to your monitor** — privacy\u002Fcompliance risk; log metadata, not bodies.\n5. **No client error monitoring** — you'll hear about outages from users, not dashboards; wire the error boundary + login-path spans.\n6. **Relying on push logs after they age out** — export within the retention window.\n\n## Verify it works\nUsage\u002Fmessage metrics return real numbers into your dashboard · a test message triggers your webhook and lands in your warehouse\u002Fmonitor · a forced init\u002Flogin failure shows up in your error monitor with context · push\u002Fcall logs are readable when needed · (on-prem) Grafana shows the services and alerts fire.\n",{"name":5,"license":15,"metadata":59,"description":7,"compatibility":63},{"tags":60,"author":61,"version":62},"cometchat analytics observability metrics webhooks monitoring datadog sentry dashboards","CometChat","1.0.0","CometChat Metrics REST API (usage · message) · Webhooks · Notification\u002FCall logs · on-prem Prometheus\u002FGrafana\u002FLoki. Client error monitoring via each family's error boundary \u002F listeners.","main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002Fcometchat\u002Fcometchat-skills\u002Fskills\u002Fcometchat-analytics",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":75,"prompt":85,"zipAvailable":86},[76,79,82],{"tool":77,"command":78},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill cometchat-analytics",{"tool":80,"command":81},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill cometchat-analytics",{"tool":83,"command":84},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill cometchat-analytics","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fcometchat\u002Fcometchat-skills\u002Fskills\u002Fcometchat-analytics\u002FSKILL.md",true,[],[89,98,106,114,122,130],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":93,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":97},"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":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":102,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":97},"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":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":110,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":97},"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":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":118,"sourceHtmlUrl":119,"categories":120,"keywords":121,"publishedAt":97},"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":123,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":126,"sourceHtmlUrl":127,"categories":128,"keywords":129,"publishedAt":97},"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":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":134,"sourceHtmlUrl":135,"categories":136,"keywords":137,"publishedAt":97},"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",[],[]]