[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MF56QTJR6FE34KQ98ZRQWX":3,"skill-same:01M6MF56QTJR6FE34KQ98ZRQWX":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},"01M6MF56QTJR6FE34KQ98ZRQWX","cometchat-android-v6-kotlin-placement",null,"Where the CometChat Android v6 chat UI goes in a Kotlin XML Views app — the default conversations→message Activity flow, growing to the tab-based app (chats\u002Fusers\u002Fgroups\u002Fcalls + detail, thread and search screens + incoming calls), a single one-to-one screen, or chat embedded in an existing Activity\u002FFragment, with a correct back stack. Triggers: 'tab based chat android', 'add a chat tab to my app', 'open a chat screen for this user', 'embed cometchat in my activity', 'full chat app android kotlin'.","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-kotlin-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 android v6 kotlin placement","cometchat","kotlin","android","jvm","my","verified","activity","flow","screen","layout","message","stack","android kotlin","open","chat ui","default","search","conversations","app","back","2026-11-10 10:12:30",false,"---\nname: cometchat-android-v6-kotlin-placement\ndescription: \"Where the CometChat Android v6 chat UI goes in a Kotlin XML Views app — the default conversations→message Activity flow, growing to the tab-based app (chats\u002Fusers\u002Fgroups\u002Fcalls + detail, thread and search screens + incoming calls), a single one-to-one screen, or chat embedded in an existing Activity\u002FFragment, with a correct back stack. Triggers: 'tab based chat android', 'add a chat tab to my app', 'open a chat screen for this user', 'embed cometchat in my activity', 'full chat app android kotlin'.\"\nlicense: \"MIT\"\ncompatibility: \"Android minSdk >=28; compileSdk >=36; Kotlin >=2.1; AGP >=8.9.1; JVM target 11; com.cometchat:chatuikit-kotlin-android ^6 (XML Views cohort) — 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 placement layout v6 kotlin views navigation activity\"\n---\n\n> **Ground truth:** catalog `android-v6.json` + `contracts.android-v6.json` (`core-chat-surface`, `chat-experience`) + the live recipes (`conversation-message-view`, `tab-based-chat`, `one-to-one-chat`). Signatures below were verified against the INSTALLED 6.0.5 source. Fetch anything else from docs (`core` → `references\u002Fdocs-map.md`).\n>\n> ⚠️ **Kotlin XML Views cohort.** Screens are Activities\u002FFragments hosting kit Views. The Compose cohort (NavHost + composables) is a separate skill.\n\n## Companion skills (read first)\n- `cometchat-android-v6-core` — install, credentials, `initFromSettings → login → render`, and **`references\u002Flayout.md` (the ONE sizing standard)**. Sizing rules live THERE; this skill places screens.\n- `cometchat-android-v6-kotlin-components` — what exists in this cohort.\n\n## Use this skill when\n\"put chat behind a tab\", \"build the full chat app\", \"open a chat screen for this user\u002Fgroup\", \"embed the conversation list in an existing screen\", \"how should I navigate between the list and the messages\".\n\n## Prerequisites & install\nSame kit + `initFromSettings → login` gate as `core` — **no chat Activity is started before login resolves.** Every Activity below must be lifecycle-aware (`AppCompatActivity`\u002F`ComponentActivity`\u002F`FragmentActivity`) — the kit hooks lifecycle events — and **registered in `AndroidManifest.xml`**.\n\n## The rule that governs every layout: one screen per Activity\nAndroid composes by **navigation**, not by side-by-side panes. The list, the message screen, the thread and search are separate destinations with a real back stack. Never build a web-style two-pane split or a \"side panel\" on a phone.\n\n## Placement 1 — conversations → messages (the default)\nThe `core-chat-surface` contract. `core` carries the full code; the structure:\n\n```kotlin\n\u002F\u002F ConversationActivity — the list\nconversations.setOnItemClick { conversation ->\n    val intent = Intent(this, MessageActivity::class.java)\n    when (val entity = conversation.conversationWith) {\n        is User -> intent.putExtra(\"user\", entity)\n        is Group -> intent.putExtra(\"group\", entity)\n    }\n    startActivity(intent)\n}\nconversations.setOnSearchClick { startActivity(Intent(this, SearchActivity::class.java)) }\n```\n`activity_message.xml` is a vertical `LinearLayout`: header `wrap_content` → list **`0dp` + `layout_weight=\"1\"`** → composer `wrap_content`, all `match_parent` wide. The weight is what makes the list scroll instead of pushing the composer off-screen. Bind the SAME `User`\u002F`Group` into header + list + composer, and wire `header.setOnBackPress { finish() }`.\n\n**Thread and search are part of this default** — see Placement 3's screens; wire them or hide the affordance.\n\n## Placement 2 — a chat tab in an existing app\nHost `CometChatConversations` in a Fragment inside your existing `BottomNavigationView`\u002F`ViewPager2`. The tab shows the LIST; tapping a row starts the message Activity **full-screen above the tab bar** (not inside the tab), so the composer isn't fighting the nav bar. Reuse the host's navigation graph — additive only, never rewrite it.\n\n**Brownfield theming — the host Activity KEEPS its own theme.** Kit views resolve `?attr\u002Fcometchat*` tokens at inflate time: constructed with the host's context (its own Material3 theme), the list crashes on first show — `InflateException ... MaterialButton` on `?attr\u002FcometchatPrimaryColor` (verified on device). Do NOT re-parent the `\u003Capplication>` theme (that's `core`'s greenfield path; it breaks a Material3 host's own screens). Scope instead:\n```xml\n\u003C!-- res\u002Fvalues\u002Fthemes.xml — your app theme stays untouched -->\n\u003Cstyle name=\"Theme.YourApp.Chat\" parent=\"CometChatTheme.DayNight\">\n    \u003Citem name=\"cometchatPrimaryColor\">@color\u002Fyour_brand\u003C\u002Fitem>\n\u003C\u002Fstyle>\n\u003C!-- AndroidManifest.xml: android:theme=\"@style\u002FTheme.YourApp.Chat\" on EACH chat Activity -->\n```\n```kotlin\n\u002F\u002F Fragment\u002Ftab-embedded kit views: wrap the context; the host Activity keeps its theme\nval themed = android.view.ContextThemeWrapper(requireContext(), R.style.Theme_YourApp_Chat)\nval conversations = CometChatConversations(themed)\n```\n\n## Placement 3 — grow to the full app (the tab-based recipe)\nThe `chat-experience` contract, from the docs `tab-based-chat` page: a `BottomNavigationView` over four destinations — **Chats** (`CometChatConversations`) · **Users** (`CometChatUsers`) · **Groups** (`CometChatGroups`) · **Calls** (`CometChatCallLogs`) — each item click routing into the same message Activity.\n\n> ⚠️ **A Groups tap is NOT a Conversations tap.** `CometChatGroups` lists groups the user may not\n> have joined; routing one straight into the message screen renders the kit's error state with a\n> live-but-dead composer (verified on device). Before navigating, check membership\n> (`group.isJoined` — the field `hasJoined` is private; `isJoined()` is the accessor) and, when false, join first — `CometChat.joinGroup(guid, groupType, password, CallbackListener\u003CGroup>)` — the listener is REQUIRED (4 params)\n> — prompting for the password when `groupType` is `CometChatConstants.GROUP_TYPE_PASSWORD`. Only a\n> Conversations row is guaranteed joined, because a conversation only exists once you are in it.\n\nThen, as the plan names them:\n- **Detail screens** — user detail (block\u002Funblock) and group detail via `CometChatGroupMembers` (kick\u002Fban\u002Fscope, role-gated).\n- **Thread screen** — `CometChatThreadHeader` + a parent-scoped list\u002Fcomposer:\n```kotlin\n\u002F\u002F ThreadActivity — header takes the parent MESSAGE, list + composer take its ID (Long)\nthreadHeader.setParentMessage(parent)\nthreadList.setParentMessageId(parent.id)\nthreadComposer.setParentMessageId(parent.id)\n\u002F\u002F AND the conversation target, or replies silently never send:\nuser?.let { threadList.setUser(it); threadComposer.setUser(it) }\ngroup?.let { threadList.setGroup(it); threadComposer.setGroup(it) }\n```\n- **Search screen** — `CometChatSearch`; global by default, or scoped to the open chat with `setUid(...)`\u002F`setGuid(...)`, plus `setSearchIn(listOf(SearchScope.CONVERSATIONS, SearchScope.MESSAGES))` (import `com.cometchat.uikit.core.constants.SearchScope`) and `setOnConversationClick`\u002F`setOnMessageClick`.\n- **Incoming calls at app level** — `CometChatIncomingCall` driven by a global call listener so a call rings from any tab (→ `cometchat-android-v6-calls`).\n\nEach tab keeps its own back stack.\n\n## Placement 4 — embed in an existing screen\nDrop a component into a slice of your own layout: `0dp` + constraints inside a `ConstraintLayout`, or a fixed `dp` height — **never `wrap_content`**. The kit fills the box you give it, so an unsized box renders nothing. Useful for a support widget or a chat panel inside a larger screen.\n\n## Placement 5 — deep entry from an arbitrary screen (known UID\u002FGUID)\n\"Open a chat with THIS user\" from one of your own screens (an order, an article, a ticket): gate on the same init\u002Flogin, resolve the entity with the Chat SDK, then start the SAME message Activity from Placement 1 with the entity extra (docs: `core` → `references\u002Fdocs-map.md` → `one-to-one-chat`):\n```kotlin\nCometChat.getUser(uid, object : CometChat.CallbackListener\u003CUser>() {   \u002F\u002F groups: CometChat.getGroup(guid, ...)\n    override fun onSuccess(user: User) {\n        startActivity(Intent(this@YourActivity, MessageActivity::class.java).putExtra(\"user\", user))\n    }\n    override fun onError(e: CometChatException) { \u002F* SURFACE it (toast\u002Fsnackbar) — ERR_UID_NOT_FOUND must not dead-end *\u002F }\n})\n```\nVerified in the installed SDK: `CometChat.getUser(@NonNull String, @NonNull CallbackListener\u003CUser>)` \u002F `CometChat.getGroup(@NonNull String, @NonNull CallbackListener\u003CGroup>)`.\n\n## Sizing and the keyboard\nOwned by `core\u002Freferences\u002Flayout.md`; the two that bite in Views: `android:windowSoftInputMode=\"adjustResize\"` on the message Activity (or the composer hides under the IME), and `enableEdgeToEdge()` + inset padding (or the header\u002Fcomposer sit under the system bars). Never nest `CometChatMessageList` in a `ScrollView`.\n\n## Navigation & back-stack discipline\nEvery pushed screen pops correctly: header `setOnBackPress` → `finish()`; thread\u002Fsearch\u002Fdetail → back returns to the message screen; predictive-back safe. Pass `User`\u002F`Group` as Parcelable extras (or re-fetch by uid\u002Fguid on the destination — Placement 5's `getUser`\u002F`getGroup` — safer across process death). Never re-`init`\u002F`login` per Activity; that happened once at startup.\n\n## Common pitfalls\nStarting a chat Activity before login resolves · inflating a kit view under the host's own theme (brownfield: scoped theme + `ContextThemeWrapper`, Placement 2 — never re-parent the application theme of an app with its own design system) · a swallowed `getUser`\u002F`getGroup` `onError` (Placement 5) · a non-lifecycle host Activity · Activity missing from the manifest · `wrap_content`\u002Funsized parent · missing `layout_weight=\"1\"` on the list (composer pushed off-screen) · composer under the IME · thread screen missing the `user`\u002F`group` target · thread\u002Fsearch opened with no way back · nesting the message list in another scrollable.\n\n## Verify it works\nCompile: `.\u002Fgradlew :app:assembleDebug   # in YOUR app (native-fence.mjs is a pack-repo gate, not installed by the CLI)`. On device: list → tap → message screen for the right entity; back returns; composer stays visible with the keyboard open; nothing under the system bars; thread and search open AND return; on the grown app each tab renders and an incoming call surfaces from any tab. A sliver or a top-left cram is a HOST sizing defect → `core\u002Freferences\u002Flayout.md`.\n","> **Ground truth:** catalog `android-v6.json` + `contracts.android-v6.json` (`core-chat-surface`, `chat-experience`) + the live recipes (`conversation-message-view`, `tab-based-chat`, `one-to-one-chat`). Signatures below were verified against the INSTALLED 6.0.5 source. Fetch anything else from docs (`core` → `references\u002Fdocs-map.md`).\n>\n> ⚠️ **Kotlin XML Views cohort.** Screens are Activities\u002FFragments hosting kit Views. The Compose cohort (NavHost + composables) is a separate skill.\n\n## Companion skills (read first)\n- `cometchat-android-v6-core` — install, credentials, `initFromSettings → login → render`, and **`references\u002Flayout.md` (the ONE sizing standard)**. Sizing rules live THERE; this skill places screens.\n- `cometchat-android-v6-kotlin-components` — what exists in this cohort.\n\n## Use this skill when\n\"put chat behind a tab\", \"build the full chat app\", \"open a chat screen for this user\u002Fgroup\", \"embed the conversation list in an existing screen\", \"how should I navigate between the list and the messages\".\n\n## Prerequisites & install\nSame kit + `initFromSettings → login` gate as `core` — **no chat Activity is started before login resolves.** Every Activity below must be lifecycle-aware (`AppCompatActivity`\u002F`ComponentActivity`\u002F`FragmentActivity`) — the kit hooks lifecycle events — and **registered in `AndroidManifest.xml`**.\n\n## The rule that governs every layout: one screen per Activity\nAndroid composes by **navigation**, not by side-by-side panes. The list, the message screen, the thread and search are separate destinations with a real back stack. Never build a web-style two-pane split or a \"side panel\" on a phone.\n\n## Placement 1 — conversations → messages (the default)\nThe `core-chat-surface` contract. `core` carries the full code; the structure:\n\n```kotlin\n\u002F\u002F ConversationActivity — the list\nconversations.setOnItemClick { conversation ->\n    val intent = Intent(this, MessageActivity::class.java)\n    when (val entity = conversation.conversationWith) {\n        is User -> intent.putExtra(\"user\", entity)\n        is Group -> intent.putExtra(\"group\", entity)\n    }\n    startActivity(intent)\n}\nconversations.setOnSearchClick { startActivity(Intent(this, SearchActivity::class.java)) }\n```\n`activity_message.xml` is a vertical `LinearLayout`: header `wrap_content` → list **`0dp` + `layout_weight=\"1\"`** → composer `wrap_content`, all `match_parent` wide. The weight is what makes the list scroll instead of pushing the composer off-screen. Bind the SAME `User`\u002F`Group` into header + list + composer, and wire `header.setOnBackPress { finish() }`.\n\n**Thread and search are part of this default** — see Placement 3's screens; wire them or hide the affordance.\n\n## Placement 2 — a chat tab in an existing app\nHost `CometChatConversations` in a Fragment inside your existing `BottomNavigationView`\u002F`ViewPager2`. The tab shows the LIST; tapping a row starts the message Activity **full-screen above the tab bar** (not inside the tab), so the composer isn't fighting the nav bar. Reuse the host's navigation graph — additive only, never rewrite it.\n\n**Brownfield theming — the host Activity KEEPS its own theme.** Kit views resolve `?attr\u002Fcometchat*` tokens at inflate time: constructed with the host's context (its own Material3 theme), the list crashes on first show — `InflateException ... MaterialButton` on `?attr\u002FcometchatPrimaryColor` (verified on device). Do NOT re-parent the `\u003Capplication>` theme (that's `core`'s greenfield path; it breaks a Material3 host's own screens). Scope instead:\n```xml\n\u003C!-- res\u002Fvalues\u002Fthemes.xml — your app theme stays untouched -->\n\u003Cstyle name=\"Theme.YourApp.Chat\" parent=\"CometChatTheme.DayNight\">\n    \u003Citem name=\"cometchatPrimaryColor\">@color\u002Fyour_brand\u003C\u002Fitem>\n\u003C\u002Fstyle>\n\u003C!-- AndroidManifest.xml: android:theme=\"@style\u002FTheme.YourApp.Chat\" on EACH chat Activity -->\n```\n```kotlin\n\u002F\u002F Fragment\u002Ftab-embedded kit views: wrap the context; the host Activity keeps its theme\nval themed = android.view.ContextThemeWrapper(requireContext(), R.style.Theme_YourApp_Chat)\nval conversations = CometChatConversations(themed)\n```\n\n## Placement 3 — grow to the full app (the tab-based recipe)\nThe `chat-experience` contract, from the docs `tab-based-chat` page: a `BottomNavigationView` over four destinations — **Chats** (`CometChatConversations`) · **Users** (`CometChatUsers`) · **Groups** (`CometChatGroups`) · **Calls** (`CometChatCallLogs`) — each item click routing into the same message Activity.\n\n> ⚠️ **A Groups tap is NOT a Conversations tap.** `CometChatGroups` lists groups the user may not\n> have joined; routing one straight into the message screen renders the kit's error state with a\n> live-but-dead composer (verified on device). Before navigating, check membership\n> (`group.isJoined` — the field `hasJoined` is private; `isJoined()` is the accessor) and, when false, join first — `CometChat.joinGroup(guid, groupType, password, CallbackListener\u003CGroup>)` — the listener is REQUIRED (4 params)\n> — prompting for the password when `groupType` is `CometChatConstants.GROUP_TYPE_PASSWORD`. Only a\n> Conversations row is guaranteed joined, because a conversation only exists once you are in it.\n\nThen, as the plan names them:\n- **Detail screens** — user detail (block\u002Funblock) and group detail via `CometChatGroupMembers` (kick\u002Fban\u002Fscope, role-gated).\n- **Thread screen** — `CometChatThreadHeader` + a parent-scoped list\u002Fcomposer:\n```kotlin\n\u002F\u002F ThreadActivity — header takes the parent MESSAGE, list + composer take its ID (Long)\nthreadHeader.setParentMessage(parent)\nthreadList.setParentMessageId(parent.id)\nthreadComposer.setParentMessageId(parent.id)\n\u002F\u002F AND the conversation target, or replies silently never send:\nuser?.let { threadList.setUser(it); threadComposer.setUser(it) }\ngroup?.let { threadList.setGroup(it); threadComposer.setGroup(it) }\n```\n- **Search screen** — `CometChatSearch`; global by default, or scoped to the open chat with `setUid(...)`\u002F`setGuid(...)`, plus `setSearchIn(listOf(SearchScope.CONVERSATIONS, SearchScope.MESSAGES))` (import `com.cometchat.uikit.core.constants.SearchScope`) and `setOnConversationClick`\u002F`setOnMessageClick`.\n- **Incoming calls at app level** — `CometChatIncomingCall` driven by a global call listener so a call rings from any tab (→ `cometchat-android-v6-calls`).\n\nEach tab keeps its own back stack.\n\n## Placement 4 — embed in an existing screen\nDrop a component into a slice of your own layout: `0dp` + constraints inside a `ConstraintLayout`, or a fixed `dp` height — **never `wrap_content`**. The kit fills the box you give it, so an unsized box renders nothing. Useful for a support widget or a chat panel inside a larger screen.\n\n## Placement 5 — deep entry from an arbitrary screen (known UID\u002FGUID)\n\"Open a chat with THIS user\" from one of your own screens (an order, an article, a ticket): gate on the same init\u002Flogin, resolve the entity with the Chat SDK, then start the SAME message Activity from Placement 1 with the entity extra (docs: `core` → `references\u002Fdocs-map.md` → `one-to-one-chat`):\n```kotlin\nCometChat.getUser(uid, object : CometChat.CallbackListener\u003CUser>() {   \u002F\u002F groups: CometChat.getGroup(guid, ...)\n    override fun onSuccess(user: User) {\n        startActivity(Intent(this@YourActivity, MessageActivity::class.java).putExtra(\"user\", user))\n    }\n    override fun onError(e: CometChatException) { \u002F* SURFACE it (toast\u002Fsnackbar) — ERR_UID_NOT_FOUND must not dead-end *\u002F }\n})\n```\nVerified in the installed SDK: `CometChat.getUser(@NonNull String, @NonNull CallbackListener\u003CUser>)` \u002F `CometChat.getGroup(@NonNull String, @NonNull CallbackListener\u003CGroup>)`.\n\n## Sizing and the keyboard\nOwned by `core\u002Freferences\u002Flayout.md`; the two that bite in Views: `android:windowSoftInputMode=\"adjustResize\"` on the message Activity (or the composer hides under the IME), and `enableEdgeToEdge()` + inset padding (or the header\u002Fcomposer sit under the system bars). Never nest `CometChatMessageList` in a `ScrollView`.\n\n## Navigation & back-stack discipline\nEvery pushed screen pops correctly: header `setOnBackPress` → `finish()`; thread\u002Fsearch\u002Fdetail → back returns to the message screen; predictive-back safe. Pass `User`\u002F`Group` as Parcelable extras (or re-fetch by uid\u002Fguid on the destination — Placement 5's `getUser`\u002F`getGroup` — safer across process death). Never re-`init`\u002F`login` per Activity; that happened once at startup.\n\n## Common pitfalls\nStarting a chat Activity before login resolves · inflating a kit view under the host's own theme (brownfield: scoped theme + `ContextThemeWrapper`, Placement 2 — never re-parent the application theme of an app with its own design system) · a swallowed `getUser`\u002F`getGroup` `onError` (Placement 5) · a non-lifecycle host Activity · Activity missing from the manifest · `wrap_content`\u002Funsized parent · missing `layout_weight=\"1\"` on the list (composer pushed off-screen) · composer under the IME · thread screen missing the `user`\u002F`group` target · thread\u002Fsearch opened with no way back · nesting the message list in another scrollable.\n\n## Verify it works\nCompile: `.\u002Fgradlew :app:assembleDebug   # in YOUR app (native-fence.mjs is a pack-repo gate, not installed by the CLI)`. On device: list → tap → message screen for the right entity; back returns; composer stays visible with the keyboard open; nothing under the system bars; thread and search open AND return; on the grown app each tab renders and an incoming call surfaces from any tab. A sliver or a top-left cram is a HOST sizing defect → `core\u002Freferences\u002Flayout.md`.\n",{"name":5,"license":15,"metadata":45,"description":7,"compatibility":49},{"tags":46,"author":47,"version":48},"cometchat android placement layout v6 kotlin views navigation activity","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 (XML Views cohort) — 6.1.x, verified 6.1.1; com.cometchat:chat-sdk-android ^5","main","cebc3dce495d7eb80d3b1d5841f877a4a92e162d","plugins\u002Fcometchat\u002Fcometchat-skills\u002Fskills\u002Fcometchat-android-v6-kotlin-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-android-v6-kotlin-placement",{"tool":66,"command":67},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill cometchat-android-v6-kotlin-placement",{"tool":69,"command":70},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill cometchat-android-v6-kotlin-placement","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fcometchat\u002Fcometchat-skills\u002Fskills\u002Fcometchat-android-v6-kotlin-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",[],[]]