[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MFARBJ8YDRZKYEF3T5RTAF":3,"skill-same:01M6MFARBJ8YDRZKYEF3T5RTAF":74},{"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},"01M6MFARBJ8YDRZKYEF3T5RTAF","cometchat-flutter-v6-placement",null,"Where CometChat chat lives in a Flutter app and how to wire each shape — a tab-based app, a chat tab inside an existing app, a full-screen route, a modal \u002F bottom-sheet chat, or an embedded panel. Triggers: 'add a chat tab', 'full screen chat page flutter', 'chat bottom sheet', 'embed chat in my screen', 'build a full chat app in 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-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 flutter v6 placement","cometchat","flutter","full","chat","embed","uikit","Existing","triggers","page","panel","add","app","flutter app","my","verified","screen","how","layout","route","how to","2026-11-10 10:12:30",false,"---\nname: cometchat-flutter-v6-placement\ndescription: \"Where CometChat chat lives in a Flutter app and how to wire each shape — a tab-based app, a chat tab inside an existing app, a full-screen route, a modal \u002F bottom-sheet chat, or an embedded panel. Triggers: 'add a chat tab', 'full screen chat page flutter', 'chat bottom sheet', 'embed chat in my screen', 'build a full chat app in 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)\"\nmetadata:\n  author: \"CometChat\"\n  version: \"1.0.0\"\n  tags: \"cometchat flutter placement layout navigation tabs bottom-sheet v6\"\n---\n\n> **Ground truth:** every widget below is in `catalogs\u002Fflutter-v6.json`. The recipes follow the official guides (`flutter-tab-based-chat` · `multi-tab-chat-ui-guide` · `flutter-conversation` · `flutter-one-to-one-chat`) via `..\u002Fcometchat-flutter-v6-core\u002Freferences\u002Fdocs-map.md`. Sizing follows the ONE mobile standard in `..\u002Fcometchat-flutter-v6-core\u002Freferences\u002Flayout.md` — change sizing rules THERE, not here.\n\n## Companion skills (read first)\n- `cometchat-flutter-v6-core` — install, credentials, `init→login→render`, the golden-path screens. This skill ASSUMES it.\n- `cometchat-flutter-v6-components` — the widget catalog these compose.\n\n## Use this skill when\nDeciding or wiring WHERE chat lives — either (a) **growing the core surface into the full tab-based app**, or (b) a scoped-down placement: a chat tab in an existing app, a modal\u002Fbottom sheet, or an embedded panel. A plain unscoped \"add chat\" is NOT this skill — that is the core surface in `-core`.\n\n## Prerequisites & install\nCovered by core. No new package.\n\n## The one invariant every placement shares\nMobile shows **one screen at a time**, so placement is a NAVIGATION problem, not a column problem:\n1. **Bounded height** — every kit list needs `Expanded`\u002F`Flexible` or a fixed height. Unbounded ⇒ exception or a zero-height list.\n2. **`Scaffold` + `SafeArea`**, `resizeToAvoidBottomInset` left at `true`.\n3. **Round-trip** — everything you push must pop back to the state that opened it.\n4. **One init\u002Flogin gate at the root**, not per screen (core's `lifecycle.md`).\n\n## Placement patterns (BAKED)\n\n**A. Tab-based app (the GROW target — the full app).** Bottom tabs: Chats (`CometChatConversations`) · Users (`CometChatUsers`) · Groups (`CometChatGroups`) · Calls (`CometChatCallLogs`), each pushing the message screen. **Incoming calls need NO widget from you** — once calling is enabled the kit's `CallEventService` presents the incoming-call overlay itself from any tab; you only set `navigatorKey: CallNavigationContext.navigatorKey` on your `MaterialApp` (see `-calls`). Do NOT mount `CometChatIncomingCall` at the root yourself — that plus the kit's own overlay = a double incoming screen. Build from `flutter-tab-based-chat`. Note `hideAppbar: true` on the list widgets when your own `Scaffold` already supplies one, or you get two headers.\n```dart\n\u002F\u002F Tab-based placement: four list components + group details + global search\n\u002F\u002F Users tab\nCometChatUsers(\n  hideAppbar: true,\n  onItemTap: (user) => Navigator.push(context, MaterialPageRoute(builder: (_) => MessageScreen(user: user))),\n)\n\u002F\u002F Groups tab\nCometChatGroups(\n  hideAppbar: true,\n  onItemTap: (group) => Navigator.push(context, MaterialPageRoute(builder: (_) => MessageScreen(group: group))),\n)\n\u002F\u002F Group details: members + kick\u002Fban\u002Fscope built in\nCometChatGroupMembers(group: group, hideAppbar: true)\n\u002F\u002F Global search from conversations list (onSearchTap -> push this screen). Result callbacks are\n\u002F\u002F onConversationClicked\u002FonMessageClicked — verified against kit 6.1.0 and the live search page\n\u002F\u002F (DOCS-BACKLOG F3 corrected upstream).\nCometChatSearch(\n  onConversationClicked: (conv) { Navigator.pop(context); openChat(conv); },\n  onMessageClicked: (msg) { Navigator.pop(context); openChat(msg); },\n  onBack: () => Navigator.pop(context),\n)\n```\n```dart\nimport 'package:cometchat_chat_uikit\u002Fcometchat_chat_uikit.dart';\nimport 'package:flutter\u002Fmaterial.dart';\n\nclass ChatsTab extends StatelessWidget {\n  const ChatsTab({super.key});\n\n  @override\n  Widget build(BuildContext context) {\n    return Scaffold(\n      appBar: AppBar(title: const Text('Chats')),\n      body: SafeArea(\n        child: CometChatConversations(\n          hideAppbar: true,                       \u002F\u002F the Scaffold already has one\n          onItemTap: (conversation) {\n            final entity = conversation.conversationWith;\n            Navigator.push(context, MaterialPageRoute(\n              builder: (_) => MessageScreen(\n                user: entity is User ? entity : null,\n                group: entity is Group ? entity : null,\n              ),\n            ));\n          },\n        ),\n      ),\n    );\n  }\n}\n```\n> The Calls tab (`CometChatCallLogs`) comes from the **calls barrel** — that screen imports both barrels (`-calls`). Incoming-call presentation is handled by the kit itself; you don't mount an incoming widget at the root.\n\n**B. Chat tab inside an existing app.** Same as (A) but only the Chats tab: drop `CometChatConversations` into your existing tab scaffold. Keep the init\u002Flogin gate at YOUR app root so chat is ready before the tab is first shown.\n\n**C. Full-screen route.** `Navigator.pushNamed('\u002Fchat')` → a `Scaffold` holding the core surface. The simplest placement; nothing extra.\n\n**D. Modal \u002F bottom-sheet chat.** A sheet has no intrinsic height — give it one explicitly, or the list throws.\n```dart\nimport 'package:cometchat_chat_uikit\u002Fcometchat_chat_uikit.dart';\nimport 'package:flutter\u002Fmaterial.dart';\n\nvoid openChatSheet(BuildContext context, User user) {\n  showModalBottomSheet(\n    context: context,\n    isScrollControlled: true,                     \u002F\u002F REQUIRED: lets it exceed half-height\n    builder: (_) => SizedBox(\n      height: MediaQuery.of(context).size.height * 0.9,   \u002F\u002F bounded — the kit fills it\n      child: SafeArea(\n        child: Column(\n          children: [\n            CometChatMessageHeader(user: user),\n            Expanded(child: CometChatMessageList(user: user)),\n            CometChatMessageComposer(user: user),\n          ],\n        ),\n      ),\n    ),\n  );\n}\n```\n> `isScrollControlled: true` + an explicit height are both required; without them the sheet caps at ~half screen and the composer fights the keyboard.\n\n**E. Embedded panel (chat inside a bigger screen).** Give the region a fixed height or a sized flex cell — never let it sit inside an unbounded `SingleChildScrollView`\u002F`Column`. If the host page scrolls, the chat needs its own `SizedBox(height: ...)`.\n\n## Choosing\n| The ask | Placement |\n|---|---|\n| \"add chat\" (unscoped) | NOT here — core surface (`-core`) |\n| \"build the full chat app\" | A — tab-based |\n| \"add a chat tab\" | B |\n| \"a chat screen\u002Fpage\" | C |\n| \"popup \u002F floating \u002F sheet chat\" | D |\n| \"chat inside my dashboard screen\" | E |\n\n## Common pitfalls (BAKED)\n- **Over-delivering the tab app for a plain \"add chat\"** — that is the core surface, not this.\n- **A list with no bounded height** — the most common Flutter failure (`layout.md`).\n- **A bottom sheet without `isScrollControlled` + an explicit height.**\n- **Two headers** — your `Scaffold` `AppBar` plus the widget's own; set `hideAppbar: true`.\n- **Mounting `CometChatIncomingCall` yourself** — unnecessary and causes a double incoming-call screen. The kit presents the overlay automatically once calling is enabled; you only set `CallNavigationContext.navigatorKey` on your `MaterialApp` (`-calls`).\n- **A pushed screen with no way back** (`navigation-round-trip`).\n- **Re-running init\u002Flogin per screen** instead of gating once at the root.\n\n## Verify it works\nEach placement renders full-size with no unbounded-height exception; item tap pushes and back pops; the composer stays above the keyboard; on the tab app an incoming call surfaces from every tab. Growing beyond this ⇒ `-calls` \u002F `-features`.\n","> **Ground truth:** every widget below is in `catalogs\u002Fflutter-v6.json`. The recipes follow the official guides (`flutter-tab-based-chat` · `multi-tab-chat-ui-guide` · `flutter-conversation` · `flutter-one-to-one-chat`) via `..\u002Fcometchat-flutter-v6-core\u002Freferences\u002Fdocs-map.md`. Sizing follows the ONE mobile standard in `..\u002Fcometchat-flutter-v6-core\u002Freferences\u002Flayout.md` — change sizing rules THERE, not here.\n\n## Companion skills (read first)\n- `cometchat-flutter-v6-core` — install, credentials, `init→login→render`, the golden-path screens. This skill ASSUMES it.\n- `cometchat-flutter-v6-components` — the widget catalog these compose.\n\n## Use this skill when\nDeciding or wiring WHERE chat lives — either (a) **growing the core surface into the full tab-based app**, or (b) a scoped-down placement: a chat tab in an existing app, a modal\u002Fbottom sheet, or an embedded panel. A plain unscoped \"add chat\" is NOT this skill — that is the core surface in `-core`.\n\n## Prerequisites & install\nCovered by core. No new package.\n\n## The one invariant every placement shares\nMobile shows **one screen at a time**, so placement is a NAVIGATION problem, not a column problem:\n1. **Bounded height** — every kit list needs `Expanded`\u002F`Flexible` or a fixed height. Unbounded ⇒ exception or a zero-height list.\n2. **`Scaffold` + `SafeArea`**, `resizeToAvoidBottomInset` left at `true`.\n3. **Round-trip** — everything you push must pop back to the state that opened it.\n4. **One init\u002Flogin gate at the root**, not per screen (core's `lifecycle.md`).\n\n## Placement patterns (BAKED)\n\n**A. Tab-based app (the GROW target — the full app).** Bottom tabs: Chats (`CometChatConversations`) · Users (`CometChatUsers`) · Groups (`CometChatGroups`) · Calls (`CometChatCallLogs`), each pushing the message screen. **Incoming calls need NO widget from you** — once calling is enabled the kit's `CallEventService` presents the incoming-call overlay itself from any tab; you only set `navigatorKey: CallNavigationContext.navigatorKey` on your `MaterialApp` (see `-calls`). Do NOT mount `CometChatIncomingCall` at the root yourself — that plus the kit's own overlay = a double incoming screen. Build from `flutter-tab-based-chat`. Note `hideAppbar: true` on the list widgets when your own `Scaffold` already supplies one, or you get two headers.\n```dart\n\u002F\u002F Tab-based placement: four list components + group details + global search\n\u002F\u002F Users tab\nCometChatUsers(\n  hideAppbar: true,\n  onItemTap: (user) => Navigator.push(context, MaterialPageRoute(builder: (_) => MessageScreen(user: user))),\n)\n\u002F\u002F Groups tab\nCometChatGroups(\n  hideAppbar: true,\n  onItemTap: (group) => Navigator.push(context, MaterialPageRoute(builder: (_) => MessageScreen(group: group))),\n)\n\u002F\u002F Group details: members + kick\u002Fban\u002Fscope built in\nCometChatGroupMembers(group: group, hideAppbar: true)\n\u002F\u002F Global search from conversations list (onSearchTap -> push this screen). Result callbacks are\n\u002F\u002F onConversationClicked\u002FonMessageClicked — verified against kit 6.1.0 and the live search page\n\u002F\u002F (DOCS-BACKLOG F3 corrected upstream).\nCometChatSearch(\n  onConversationClicked: (conv) { Navigator.pop(context); openChat(conv); },\n  onMessageClicked: (msg) { Navigator.pop(context); openChat(msg); },\n  onBack: () => Navigator.pop(context),\n)\n```\n```dart\nimport 'package:cometchat_chat_uikit\u002Fcometchat_chat_uikit.dart';\nimport 'package:flutter\u002Fmaterial.dart';\n\nclass ChatsTab extends StatelessWidget {\n  const ChatsTab({super.key});\n\n  @override\n  Widget build(BuildContext context) {\n    return Scaffold(\n      appBar: AppBar(title: const Text('Chats')),\n      body: SafeArea(\n        child: CometChatConversations(\n          hideAppbar: true,                       \u002F\u002F the Scaffold already has one\n          onItemTap: (conversation) {\n            final entity = conversation.conversationWith;\n            Navigator.push(context, MaterialPageRoute(\n              builder: (_) => MessageScreen(\n                user: entity is User ? entity : null,\n                group: entity is Group ? entity : null,\n              ),\n            ));\n          },\n        ),\n      ),\n    );\n  }\n}\n```\n> The Calls tab (`CometChatCallLogs`) comes from the **calls barrel** — that screen imports both barrels (`-calls`). Incoming-call presentation is handled by the kit itself; you don't mount an incoming widget at the root.\n\n**B. Chat tab inside an existing app.** Same as (A) but only the Chats tab: drop `CometChatConversations` into your existing tab scaffold. Keep the init\u002Flogin gate at YOUR app root so chat is ready before the tab is first shown.\n\n**C. Full-screen route.** `Navigator.pushNamed('\u002Fchat')` → a `Scaffold` holding the core surface. The simplest placement; nothing extra.\n\n**D. Modal \u002F bottom-sheet chat.** A sheet has no intrinsic height — give it one explicitly, or the list throws.\n```dart\nimport 'package:cometchat_chat_uikit\u002Fcometchat_chat_uikit.dart';\nimport 'package:flutter\u002Fmaterial.dart';\n\nvoid openChatSheet(BuildContext context, User user) {\n  showModalBottomSheet(\n    context: context,\n    isScrollControlled: true,                     \u002F\u002F REQUIRED: lets it exceed half-height\n    builder: (_) => SizedBox(\n      height: MediaQuery.of(context).size.height * 0.9,   \u002F\u002F bounded — the kit fills it\n      child: SafeArea(\n        child: Column(\n          children: [\n            CometChatMessageHeader(user: user),\n            Expanded(child: CometChatMessageList(user: user)),\n            CometChatMessageComposer(user: user),\n          ],\n        ),\n      ),\n    ),\n  );\n}\n```\n> `isScrollControlled: true` + an explicit height are both required; without them the sheet caps at ~half screen and the composer fights the keyboard.\n\n**E. Embedded panel (chat inside a bigger screen).** Give the region a fixed height or a sized flex cell — never let it sit inside an unbounded `SingleChildScrollView`\u002F`Column`. If the host page scrolls, the chat needs its own `SizedBox(height: ...)`.\n\n## Choosing\n| The ask | Placement |\n|---|---|\n| \"add chat\" (unscoped) | NOT here — core surface (`-core`) |\n| \"build the full chat app\" | A — tab-based |\n| \"add a chat tab\" | B |\n| \"a chat screen\u002Fpage\" | C |\n| \"popup \u002F floating \u002F sheet chat\" | D |\n| \"chat inside my dashboard screen\" | E |\n\n## Common pitfalls (BAKED)\n- **Over-delivering the tab app for a plain \"add chat\"** — that is the core surface, not this.\n- **A list with no bounded height** — the most common Flutter failure (`layout.md`).\n- **A bottom sheet without `isScrollControlled` + an explicit height.**\n- **Two headers** — your `Scaffold` `AppBar` plus the widget's own; set `hideAppbar: true`.\n- **Mounting `CometChatIncomingCall` yourself** — unnecessary and causes a double incoming-call screen. The kit presents the overlay automatically once calling is enabled; you only set `CallNavigationContext.navigatorKey` on your `MaterialApp` (`-calls`).\n- **A pushed screen with no way back** (`navigation-round-trip`).\n- **Re-running init\u002Flogin per screen** instead of gating once at the root.\n\n## Verify it works\nEach placement renders full-size with no unbounded-height exception; item tap pushes and back pops; the composer stays above the keyboard; on the tab app an incoming call surfaces from every tab. Growing beyond this ⇒ `-calls` \u002F `-features`.\n",{"name":5,"license":15,"metadata":45,"description":7,"compatibility":49},{"tags":46,"author":47,"version":48},"cometchat flutter placement layout navigation tabs bottom-sheet 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)","main","cebc3dce495d7eb80d3b1d5841f877a4a92e162d","plugins\u002Fcometchat\u002Fcometchat-skills\u002Fskills\u002Fcometchat-flutter-v6-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-flutter-v6-placement",{"tool":66,"command":67},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill cometchat-flutter-v6-placement",{"tool":69,"command":70},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill cometchat-flutter-v6-placement","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fcometchat\u002Fcometchat-skills\u002Fskills\u002Fcometchat-flutter-v6-placement\u002FSKILL.md",true,[],[75,84,92,100,108,116],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":79,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":83},"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":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":88,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":83},"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":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":96,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":83},"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":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":104,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":83},"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":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":112,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":83},"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":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":120,"sourceHtmlUrl":121,"categories":122,"keywords":123,"publishedAt":83},"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",[],[]]