[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MF97PWTMDP9V8TY8W329SJ":3,"skill-same:01M6MF97PWTMDP9V8TY8W329SJ":86},{"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":23,"publishedAt":46,"linkOnly":47,"markdownContent":48,"markdownBody":49,"frontMatter":50,"refName":56,"commitSha":57,"skillDirectory":58,"forksCount":59,"repositoryHtmlUrl":60,"repositoryHomepageUrl":61,"ownerHtmlUrl":62,"ownerBlogUrl":63,"ownerDescription":64,"updatedAt":65,"install":66,"resources":79},"01M6MF97PWTMDP9V8TY8W329SJ","cometchat-flutter-v6-calls",null,"Add voice & video calling to a Flutter app with the CometChat v6 UI Kit — turn calling on in settings, wire the native config and the root navigatorKey (the kit presents incoming\u002Foutgoing call screens itself), and add call-log surfaces. Triggers: 'add voice and video calls in flutter', 'add calling to my flutter chat', 'enable video call flutter', 'add call buttons flutter', 'show call logs flutter'.","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-flutter-v6-calls\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000016","图像与多媒体","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45],"flutter","cometchat flutter v6 calls","calls","cometchat","buttons","call","triggers","add","ui","flutter app","my","verified","config","surfaces","native","log","logs","webrtc","kit","show","app","Video","2026-11-10 10:12:30",false,"---\nname: cometchat-flutter-v6-calls\ndescription: \"Add voice & video calling to a Flutter app with the CometChat v6 UI Kit — turn calling on in settings, wire the native config and the root navigatorKey (the kit presents incoming\u002Foutgoing call screens itself), and add call-log surfaces. Triggers: 'add voice and video calls in flutter', 'add calling to my flutter chat', 'enable video call flutter', 'add call buttons flutter', 'show call logs flutter'.\"\nlicense: \"MIT\"\ncompatibility: \"Flutter >=3.38.9; cometchat_chat_uikit ^6.2.0 (6.2.x; catalog compiler-verified vs 6.1.0, source-checked vs 6.2.0); cometchat_calls_sdk ^5.0.8 (5.0.9 latest — separate package)\"\nmetadata:\n  author: \"CometChat\"\n  version: \"1.0.0\"\n  tags: \"cometchat flutter calls voice video calling webrtc v6\"\n---\n\n> **Ground truth:** the call UI ships INSIDE `cometchat_chat_uikit`, but in a **second barrel**, and the WebRTC engine is a separate package (`cometchat_calls_sdk`). Every symbol below is catalog-verified against 6.1.0. Exhaustive props: FETCH the twin via `..\u002Fcometchat-flutter-v6-core\u002Freferences\u002Fdocs-map.md` (`call-features` · `incoming-call` · `outgoing-call` · `call-logs` · `call-buttons`). **APPEND to the user's app — additive wiring only.**\n\n## Companion skills (read first)\n- `cometchat-flutter-v6-core` — install, credentials, the settings asset, `init→login→render`. This skill ASSUMES it (calling rides the SAME init).\n- `cometchat-flutter-v6-components` — the widget catalog.\n- `cometchat-flutter-v6-placement` — where call surfaces sit in the app shell (incoming calls need only the root `navigatorKey` — no widget).\n\n## Use this skill when\n\"add voice & video calls\", \"enable video call\", \"add call buttons\", \"show call logs\". Precondition: chat already works (core done).\n\n## Prerequisites & install\n`cometchat_chat_uikit` **already depends on `cometchat_calls_sdk`** (`^5.0.8`, in the kit's own `dependencies:` — verified in the 6.2.0 pubspec; 6.1.x asked for `^5.0.4`), so the WebRTC engine is pulled in transitively; you do **not** need to add it. Add an explicit direct dependency **only** if you import `cometchat_calls_sdk` symbols directly (then pin it to keep resolution predictable):\n```bash\nflutter pub add cometchat_calls_sdk   # optional — only if you import the package directly\n```\nThen the native config the docs require — **all four steps, or calling silently never rings**:\n1. `cometchat_calls_sdk` (transitive via the kit; pin `^5.0.8` in `pubspec.yaml` only if you added it directly: the 6.2.0 kit does not compile against older).\n2. **Android** `android\u002Fapp\u002Fbuild.gradle.kts`: `minSdk = 26`.\n3. **iOS** `ios\u002FPodfile`: `platform :ios, '15.1'`, then `pod install`.\n4. **Permissions** — camera + microphone (`AndroidManifest.xml`; `NSCameraUsageDescription` \u002F `NSMicrophoneUsageDescription` in `Info.plist`). Without them the call surface opens black.\n> **⚠️ The docs' floors are too low and these are compiler-verified instead.** `cometchat_calls_sdk`\n> pins `minSdkVersion 26` in its `android\u002Fbuild.gradle` and `platform :ios, '15.1'` in its podspec\n> (5.0.7 through 5.0.9; it was 13.0 through 5.0.6). Gradle and CocoaPods take the MAXIMUM across the dependency\n> graph, so a lower app-level value is a build error, not a warning. Docs say 24 \u002F 13.0 —\n> DOCS-BACKLOG D7. Platform floors do move: re-verify against the installed package, not the page.\n\n## THE BARREL TRAP (read before writing a line)\nEvery call widget resolves **only** from the calls barrel, and that barrel does **not** re-export the chat widgets. A calls screen imports **both**:\n```dart\nimport 'package:cometchat_chat_uikit\u002Fcometchat_chat_uikit.dart';        \u002F\u002F chat widgets + SDK types\nimport 'package:cometchat_chat_uikit\u002Fcometchat_calls_uikit.dart';       \u002F\u002F ALL call widgets\n```\nImporting only the chat barrel and then emitting `CometChatIncomingCall` fails to compile with *\"Undefined name\"* — the single most common calls mistake.\n\n## Enable calling (BAKED — the #1 gotcha: TWO things must be true)\nCalling is off until **(a)** the Calls SDK is installed **and (b)** calling is enabled in settings. Core inits via `initFromSettings`, which reads `cometchat-settings.json` — so flip it **in the file**:\n```json\n{\n  \"appId\": \"APP_ID\",\n  \"region\": \"REGION\",\n  \"credentials\": { \"authKey\": \"AUTH_KEY\" },\n  \"uiKit\": { \"subscribePresenceForAllUsers\": true, \"enableCalling\": true },\n  \"chatSDK\": { \"autoEstablishSocketConnection\": true }\n}\n```\n> `uiKit.enableCalling` is the **only** way to enable calling on the `initFromSettings` path — `UIKitSettings` defaults it to false. (If the project uses the classic builder instead, the equivalent is `..enableCalls = true` plus `..callingConfiguration = CallingConfiguration()`.)\n\n## Wire it (BAKED)\n**1. A navigator key at the app root** so the kit can present call screens from anywhere:\n```dart\nimport 'package:cometchat_chat_uikit\u002Fcometchat_calls_uikit.dart';\nimport 'package:flutter\u002Fmaterial.dart';\n\nWidget app(Widget home) => MaterialApp(\n      navigatorKey: CallNavigationContext.navigatorKey,   \u002F\u002F REQUIRED for call routing\n      home: home,\n    );\n```\n\n**2. That's it for incoming calls — the kit does the rest.** Do **NOT** add your own root `CallListener` or present `CometChatIncomingCall` yourself. When `uiKit.enableCalling` is true, the kit's `CallEventService` registers its **own** `CometChat.addCallListener(...)` on login and shows the incoming-call overlay automatically via `IncomingCallOverlay` (verified in `cometchat_chat_uikit` 6.1.x and 6.2.0). Adding a second listener + a manual overlay produces a **DOUBLE** incoming-call screen. All you owe it is the `navigatorKey` from step 1 (that is how the overlay finds a context to present — without it the kit logs *\"Incoming call overlay cannot be shown\"*).\n\n**To customize the incoming\u002Foutgoing\u002Fcall-button surfaces, pass a `CallingConfiguration`** — not a hand-rolled listener. On the classic builder path: `..callingConfiguration = CallingConfiguration(incomingCallConfiguration: ..., outgoingCallConfiguration: ..., callButtonsConfiguration: ...)`. `CallingConfiguration` (with `incomingCallConfiguration` \u002F `outgoingCallConfiguration` \u002F `callButtonsConfiguration`) is the kit's supported entry point; fetch its fields via the twin (`call-features`).\n\n**3. Extra surfaces you place yourself** — call logs, and the incoming\u002Foutgoing widgets only when you build a fully custom flow — from the CALLS barrel:\n```dart\nimport 'package:cometchat_chat_uikit\u002Fcometchat_calls_uikit.dart';\nimport 'package:flutter\u002Fmaterial.dart';\n\nWidget logs() => const CometChatCallLogs();\n\u002F\u002F Only when replacing the built-in overlay with a fully custom flow — otherwise the kit\n\u002F\u002F already presents these for you:\nWidget incoming(Call call, User user) => CometChatIncomingCall(call: call, user: user);\nWidget outgoing(Call call, User user) => CometChatOutgoingCall(call: call, user: user);\n```\n> **Call buttons are already in `CometChatMessageHeader`** — do NOT hand-roll them. They appear once calling is enabled; hide with `hideVoiceCallButton` \u002F `hideVideoCallButton`. `CometChatCallButtons` is for placing them somewhere else (e.g. a profile screen).\n\n### Huddle \u002F docked call — Flutter how-to (BAKED — verified vs cometchat_chat_uikit 6.2.0 + cometchat_calls_sdk 5.0.9)\nSlack-style huddle (start from the channel header, Join opens your dock, leave cleans up): `references\u002Fhuddle.md`. Pattern: `cometchat-onboarding\u002Freferences\u002Fclone-mode.md` → *Huddle \u002F drop-in room pattern*.\n\n## Common pitfalls (BAKED — the ones that actually bite)\n- **Enabled in only one place** — SDK installed but `enableCalling` false (or vice-versa) ⇒ every call affordance stays hidden, with no error.\n- **Missing camera\u002Fmic permissions** ⇒ the call surface opens black. Test on a real device; simulators have no camera.\n- **Adding your own root `CallListener` + `CometChatIncomingCall`** ⇒ a DOUBLE incoming-call screen. The kit's `CallEventService` already listens and shows the overlay when calling is enabled — don't duplicate it; customize via `CallingConfiguration`.\n- **No `navigatorKey`** (`CallNavigationContext.navigatorKey` on your `MaterialApp`) ⇒ the kit's overlay has no context to present from and logs *\"Incoming call overlay cannot be shown\"*.\n- **A call surface with no bounded height** ⇒ zero-dimension video (`..\u002Fcometchat-flutter-v6-core\u002Freferences\u002Flayout.md`).\n- **A docked or mini call opened full screen** — the group call button and the meeting bubble's Join both open `CallScreenOverlay` (a full-screen overlay). For a dock, replace both and join the session into your own box (`references\u002Fhuddle.md`).\n- **Group calls do not ring** the way 1:1 does — group calling is join-based. Verify the behaviour you promise against `call-features`.\n- **Details screens are host-composed** — there is no `CometChatCallLogDetails` widget; build it from `guide-call-log-details`.\n\n## Verify it works\nOn TWO real devices (not simulators): calling enabled in the settings file and the Calls SDK installed → the header shows call buttons → placing a call rings the other device → accept shows the ongoing surface with real video → decline\u002Fend returns both sides cleanly → the call appears in `CometChatCallLogs`. A black surface means permissions; no ring means the enable pair or a missing `navigatorKey`; two incoming screens means a hand-added listener\u002F`CometChatIncomingCall`.\n> Build the feature; do not write tests unless asked (`RULES.md`) — the above is an advisory human pass.\n\n**Close (after it builds):** end with the shared 3-option selectable menu and WAIT — **(1) add another feature · (2) customize theming · (3) test it manually** (same contract as core, `RULES.md` §19).\n","> **Ground truth:** the call UI ships INSIDE `cometchat_chat_uikit`, but in a **second barrel**, and the WebRTC engine is a separate package (`cometchat_calls_sdk`). Every symbol below is catalog-verified against 6.1.0. Exhaustive props: FETCH the twin via `..\u002Fcometchat-flutter-v6-core\u002Freferences\u002Fdocs-map.md` (`call-features` · `incoming-call` · `outgoing-call` · `call-logs` · `call-buttons`). **APPEND to the user's app — additive wiring only.**\n\n## Companion skills (read first)\n- `cometchat-flutter-v6-core` — install, credentials, the settings asset, `init→login→render`. This skill ASSUMES it (calling rides the SAME init).\n- `cometchat-flutter-v6-components` — the widget catalog.\n- `cometchat-flutter-v6-placement` — where call surfaces sit in the app shell (incoming calls need only the root `navigatorKey` — no widget).\n\n## Use this skill when\n\"add voice & video calls\", \"enable video call\", \"add call buttons\", \"show call logs\". Precondition: chat already works (core done).\n\n## Prerequisites & install\n`cometchat_chat_uikit` **already depends on `cometchat_calls_sdk`** (`^5.0.8`, in the kit's own `dependencies:` — verified in the 6.2.0 pubspec; 6.1.x asked for `^5.0.4`), so the WebRTC engine is pulled in transitively; you do **not** need to add it. Add an explicit direct dependency **only** if you import `cometchat_calls_sdk` symbols directly (then pin it to keep resolution predictable):\n```bash\nflutter pub add cometchat_calls_sdk   # optional — only if you import the package directly\n```\nThen the native config the docs require — **all four steps, or calling silently never rings**:\n1. `cometchat_calls_sdk` (transitive via the kit; pin `^5.0.8` in `pubspec.yaml` only if you added it directly: the 6.2.0 kit does not compile against older).\n2. **Android** `android\u002Fapp\u002Fbuild.gradle.kts`: `minSdk = 26`.\n3. **iOS** `ios\u002FPodfile`: `platform :ios, '15.1'`, then `pod install`.\n4. **Permissions** — camera + microphone (`AndroidManifest.xml`; `NSCameraUsageDescription` \u002F `NSMicrophoneUsageDescription` in `Info.plist`). Without them the call surface opens black.\n> **⚠️ The docs' floors are too low and these are compiler-verified instead.** `cometchat_calls_sdk`\n> pins `minSdkVersion 26` in its `android\u002Fbuild.gradle` and `platform :ios, '15.1'` in its podspec\n> (5.0.7 through 5.0.9; it was 13.0 through 5.0.6). Gradle and CocoaPods take the MAXIMUM across the dependency\n> graph, so a lower app-level value is a build error, not a warning. Docs say 24 \u002F 13.0 —\n> DOCS-BACKLOG D7. Platform floors do move: re-verify against the installed package, not the page.\n\n## THE BARREL TRAP (read before writing a line)\nEvery call widget resolves **only** from the calls barrel, and that barrel does **not** re-export the chat widgets. A calls screen imports **both**:\n```dart\nimport 'package:cometchat_chat_uikit\u002Fcometchat_chat_uikit.dart';        \u002F\u002F chat widgets + SDK types\nimport 'package:cometchat_chat_uikit\u002Fcometchat_calls_uikit.dart';       \u002F\u002F ALL call widgets\n```\nImporting only the chat barrel and then emitting `CometChatIncomingCall` fails to compile with *\"Undefined name\"* — the single most common calls mistake.\n\n## Enable calling (BAKED — the #1 gotcha: TWO things must be true)\nCalling is off until **(a)** the Calls SDK is installed **and (b)** calling is enabled in settings. Core inits via `initFromSettings`, which reads `cometchat-settings.json` — so flip it **in the file**:\n```json\n{\n  \"appId\": \"APP_ID\",\n  \"region\": \"REGION\",\n  \"credentials\": { \"authKey\": \"AUTH_KEY\" },\n  \"uiKit\": { \"subscribePresenceForAllUsers\": true, \"enableCalling\": true },\n  \"chatSDK\": { \"autoEstablishSocketConnection\": true }\n}\n```\n> `uiKit.enableCalling` is the **only** way to enable calling on the `initFromSettings` path — `UIKitSettings` defaults it to false. (If the project uses the classic builder instead, the equivalent is `..enableCalls = true` plus `..callingConfiguration = CallingConfiguration()`.)\n\n## Wire it (BAKED)\n**1. A navigator key at the app root** so the kit can present call screens from anywhere:\n```dart\nimport 'package:cometchat_chat_uikit\u002Fcometchat_calls_uikit.dart';\nimport 'package:flutter\u002Fmaterial.dart';\n\nWidget app(Widget home) => MaterialApp(\n      navigatorKey: CallNavigationContext.navigatorKey,   \u002F\u002F REQUIRED for call routing\n      home: home,\n    );\n```\n\n**2. That's it for incoming calls — the kit does the rest.** Do **NOT** add your own root `CallListener` or present `CometChatIncomingCall` yourself. When `uiKit.enableCalling` is true, the kit's `CallEventService` registers its **own** `CometChat.addCallListener(...)` on login and shows the incoming-call overlay automatically via `IncomingCallOverlay` (verified in `cometchat_chat_uikit` 6.1.x and 6.2.0). Adding a second listener + a manual overlay produces a **DOUBLE** incoming-call screen. All you owe it is the `navigatorKey` from step 1 (that is how the overlay finds a context to present — without it the kit logs *\"Incoming call overlay cannot be shown\"*).\n\n**To customize the incoming\u002Foutgoing\u002Fcall-button surfaces, pass a `CallingConfiguration`** — not a hand-rolled listener. On the classic builder path: `..callingConfiguration = CallingConfiguration(incomingCallConfiguration: ..., outgoingCallConfiguration: ..., callButtonsConfiguration: ...)`. `CallingConfiguration` (with `incomingCallConfiguration` \u002F `outgoingCallConfiguration` \u002F `callButtonsConfiguration`) is the kit's supported entry point; fetch its fields via the twin (`call-features`).\n\n**3. Extra surfaces you place yourself** — call logs, and the incoming\u002Foutgoing widgets only when you build a fully custom flow — from the CALLS barrel:\n```dart\nimport 'package:cometchat_chat_uikit\u002Fcometchat_calls_uikit.dart';\nimport 'package:flutter\u002Fmaterial.dart';\n\nWidget logs() => const CometChatCallLogs();\n\u002F\u002F Only when replacing the built-in overlay with a fully custom flow — otherwise the kit\n\u002F\u002F already presents these for you:\nWidget incoming(Call call, User user) => CometChatIncomingCall(call: call, user: user);\nWidget outgoing(Call call, User user) => CometChatOutgoingCall(call: call, user: user);\n```\n> **Call buttons are already in `CometChatMessageHeader`** — do NOT hand-roll them. They appear once calling is enabled; hide with `hideVoiceCallButton` \u002F `hideVideoCallButton`. `CometChatCallButtons` is for placing them somewhere else (e.g. a profile screen).\n\n### Huddle \u002F docked call — Flutter how-to (BAKED — verified vs cometchat_chat_uikit 6.2.0 + cometchat_calls_sdk 5.0.9)\nSlack-style huddle (start from the channel header, Join opens your dock, leave cleans up): `references\u002Fhuddle.md`. Pattern: `cometchat-onboarding\u002Freferences\u002Fclone-mode.md` → *Huddle \u002F drop-in room pattern*.\n\n## Common pitfalls (BAKED — the ones that actually bite)\n- **Enabled in only one place** — SDK installed but `enableCalling` false (or vice-versa) ⇒ every call affordance stays hidden, with no error.\n- **Missing camera\u002Fmic permissions** ⇒ the call surface opens black. Test on a real device; simulators have no camera.\n- **Adding your own root `CallListener` + `CometChatIncomingCall`** ⇒ a DOUBLE incoming-call screen. The kit's `CallEventService` already listens and shows the overlay when calling is enabled — don't duplicate it; customize via `CallingConfiguration`.\n- **No `navigatorKey`** (`CallNavigationContext.navigatorKey` on your `MaterialApp`) ⇒ the kit's overlay has no context to present from and logs *\"Incoming call overlay cannot be shown\"*.\n- **A call surface with no bounded height** ⇒ zero-dimension video (`..\u002Fcometchat-flutter-v6-core\u002Freferences\u002Flayout.md`).\n- **A docked or mini call opened full screen** — the group call button and the meeting bubble's Join both open `CallScreenOverlay` (a full-screen overlay). For a dock, replace both and join the session into your own box (`references\u002Fhuddle.md`).\n- **Group calls do not ring** the way 1:1 does — group calling is join-based. Verify the behaviour you promise against `call-features`.\n- **Details screens are host-composed** — there is no `CometChatCallLogDetails` widget; build it from `guide-call-log-details`.\n\n## Verify it works\nOn TWO real devices (not simulators): calling enabled in the settings file and the Calls SDK installed → the header shows call buttons → placing a call rings the other device → accept shows the ongoing surface with real video → decline\u002Fend returns both sides cleanly → the call appears in `CometChatCallLogs`. A black surface means permissions; no ring means the enable pair or a missing `navigatorKey`; two incoming screens means a hand-added listener\u002F`CometChatIncomingCall`.\n> Build the feature; do not write tests unless asked (`RULES.md`) — the above is an advisory human pass.\n\n**Close (after it builds):** end with the shared 3-option selectable menu and WAIT — **(1) add another feature · (2) customize theming · (3) test it manually** (same contract as core, `RULES.md` §19).\n",{"name":5,"license":15,"metadata":51,"description":7,"compatibility":55},{"tags":52,"author":53,"version":54},"cometchat flutter calls voice video calling webrtc v6","CometChat","1.0.0","Flutter >=3.38.9; cometchat_chat_uikit ^6.2.0 (6.2.x; catalog compiler-verified vs 6.1.0, source-checked vs 6.2.0); cometchat_calls_sdk ^5.0.8 (5.0.9 latest — separate package)","main","cebc3dce495d7eb80d3b1d5841f877a4a92e162d","plugins\u002Fcometchat\u002Fcometchat-skills\u002Fskills\u002Fcometchat-flutter-v6-calls",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":67,"prompt":77,"zipAvailable":78},[68,71,74],{"tool":69,"command":70},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill cometchat-flutter-v6-calls",{"tool":72,"command":73},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill cometchat-flutter-v6-calls",{"tool":75,"command":76},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill cometchat-flutter-v6-calls","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fcometchat\u002Fcometchat-skills\u002Fskills\u002Fcometchat-flutter-v6-calls\u002FSKILL.md",true,[80],{"path":81,"resourceType":82,"resourceTypeDesc":83,"sizeBytes":84,"sourceHtmlUrl":85},"references\u002Fhuddle.md","REFERENCE","参考文档",7107,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fcometchat\u002Fcometchat-skills\u002Fskills\u002Fcometchat-flutter-v6-calls\u002Freferences\u002Fhuddle.md",[87,96,104,112,120,128],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"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.","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":15,"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":15,"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":15,"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":15,"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":15,"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",[],[]]