[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MFE6STYC7VA2J4KWX9Z0D4":3,"skill-same:01M6MFE6STYC7VA2J4KWX9Z0D4":115},{"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":29,"publishedAt":51,"linkOnly":52,"markdownContent":53,"markdownBody":54,"frontMatter":55,"refName":61,"commitSha":62,"skillDirectory":63,"forksCount":64,"repositoryHtmlUrl":65,"repositoryHomepageUrl":66,"ownerHtmlUrl":67,"ownerBlogUrl":68,"ownerDescription":69,"updatedAt":70,"install":71,"resources":84},"01M6MFE6STYC7VA2J4KWX9Z0D4","cometchat-migrate-from-getstream",null,"Migrate an app from Stream (GetStream) Chat to CometChat end-to-end in ONE prompt, on any platform in this pack (React, Angular, React Native\u002FExpo, iOS, Android, Flutter). Inventories every Stream usage (stream-chat client, the React\u002FAngular\u002FRN\u002FFlutter\u002FSwift\u002FAndroid SDKs, Stream Video, Activity Feeds, push, server tokens, webhooks), swaps each supported feature for its CometChat equivalent, REMOVES features CometChat has no equivalent for (code, UI, deps), writes a data-migration script for users\u002Fchannels\u002Fhistory, uninstalls Stream, verifies the build, and ends with a report listing what was migrated, what was removed and what you still need to do. Triggers: 'migrate my app from Stream to CometChat', 'migrate from GetStream', 'migrate my app to CometChat' (Stream detected), 'replace Stream Chat with CometChat', 'switch from getstream', 'move off Stream', 'stream-chat to cometchat', 'port my GetStream chat to CometChat', 'migrate only my data from Stream', 'import my Stream data into CometChat'.","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-migrate-from-getstream\u002FSKILL.md",[18,23,26],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":27,"categoryName":28,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50],"migrate","cometchat","cometchat migrate from getstream","react native","import","usage","do","swift","ui","expo","swaps","react-native","Video","port","server","react","you","kit","move","deps","app","2026-11-10 10:12:30",false,"---\nname: cometchat-migrate-from-getstream\ndescription: \"Migrate an app from Stream (GetStream) Chat to CometChat end-to-end in ONE prompt, on any platform in this pack (React, Angular, React Native\u002FExpo, iOS, Android, Flutter). Inventories every Stream usage (stream-chat client, the React\u002FAngular\u002FRN\u002FFlutter\u002FSwift\u002FAndroid SDKs, Stream Video, Activity Feeds, push, server tokens, webhooks), swaps each supported feature for its CometChat equivalent, REMOVES features CometChat has no equivalent for (code, UI, deps), writes a data-migration script for users\u002Fchannels\u002Fhistory, uninstalls Stream, verifies the build, and ends with a report listing what was migrated, what was removed and what you still need to do. Triggers: 'migrate my app from Stream to CometChat', 'migrate from GetStream', 'migrate my app to CometChat' (Stream detected), 'replace Stream Chat with CometChat', 'switch from getstream', 'move off Stream', 'stream-chat to cometchat', 'port my GetStream chat to CometChat', 'migrate only my data from Stream', 'import my Stream data into CometChat'.\"\nlicense: \"MIT\"\ncompatibility: \"FROM Stream Chat (`stream-chat` JS client; stream-chat-react, stream-chat-angular, stream-chat-react-native \u002F stream-chat-expo, stream_chat_flutter, StreamChat\u002FStreamChatUI\u002FStreamChatSwiftUI, io.getstream:stream-chat-android-*), Stream Video, Stream Activity Feeds → TO the CometChat family this pack detects (peers.yaml): React UI Kit v7, Angular v5, React Native v5, iOS v5, Android v6, Flutter v6, plus the headless Chat\u002FCalls SDKs. Node >=18 for the data-migration script.\"\nmetadata:\n  author: \"CometChat\"\n  version: \"1.0.0\"\n  tags: \"cometchat migration getstream stream stream-chat competitor switch replace port uikit sdk calls data-import\"\n---\n\n> **Ground truth:** the STREAM side (what to look for) is baked in `references\u002Finventory.md` + `references\u002Ffeature-map.md` — confirm each hit by reading the user's code. The COMETCHAT side is never from memory: symbols come from the target family's skills + catalog, feature existence from that family's `features.json`, signatures from the docs via the family's `-core\u002Freferences\u002Fdocs-map.md` (Docs MCP first — `RULES.md` → Fetch discipline). REST pages live under `DOCS_BASE` = `https:\u002F\u002Fwww.cometchat.com\u002Fdocs`.\n\n## Companion skills (read first)\n- `cometchat-\u003Cfamily>-core` — the init → login → render the migrated app lands on. `\u003Cfamily>` is resolved in step 1; this skill ASSUMES that core and never restates its code.\n- `cometchat-\u003Cfamily>-components` \u002F `-features` \u002F `-calls` \u002F `-push` \u002F `-customization` — pulled in only for the Stream features the inventory finds.\n\n## Use this skill when\nThe user asks to move an app off Stream: \"migrate my app from GetStream\u002FStream to CometChat\", \"replace Stream Chat\", \"switch to CometChat\", or \"migrate my app to CometChat\" when `npx @cometchat\u002Fskills detect --json` reports `migrate_from` with vendor `getstream`. Sendbird apps → `cometchat-migrate-from-sendbird`. An app with BOTH vendors: run both skills, one after the other, into one report.\n**Data only** (\"migrate only my data\", \"import my Stream users and messages\", \"don't change my code\", or the app already runs on CometChat) → follow `references\u002Fdata-only.md` INSTEAD of the workflow below: it writes and runs the data script and changes nothing else.\n\n## The single-prompt contract (read before step 1)\nThe migration request IS the approval (`RULES.md` → Competitor migration). Run every step below to the end in this one turn:\n- **Docs MCP check comes first.** No `search_cometchat_docs` tool? Say so in your first message, before any edit, with how to connect it (`RULES.md` → Canonical doc channel), then continue on web docs. Note it in the report.\n- **Do not stop to ask.** No onboarding plan\u002Fapprove gate, no clarification questions. Where a companion skill would ask, take the default written here, and record it under *Defaults taken* in the report.\n- **Safety net instead of questions:** in a git repo, first `git switch -c cometchat-migration` (carries any uncommitted work along; mention that in the report). Never commit, push, or rewrite history. No git → proceed and say so in the report.\n- **Removing Stream is the requested outcome** — `RULES.md`'s append-never-replace does not protect Stream code. It still protects everything else: touch non-chat code only to rewire it.\n- **Credentials: never ask, never provision.** Reuse `.cometchat\u002Fconfig.json` or existing CometChat env values if present; otherwise write the family's env\u002Fsettings file with clearly-named placeholders so the build still compiles, and make \"add your CometChat credentials\" action item #1. **Never write a real key into a git-tracked file:** check `git ls-files \u003Cfile>` first. If the file is tracked, put real values in the untracked local variant the framework reads (Vite\u002FNext `.env.local`, Android `local.properties`, ...) and keep placeholders in the tracked file. Adding a tracked file to `.gitignore` does NOT untrack it. The server's REST API key only ever goes into an untracked file or the hosting env.\n- **Only three STOPs:** (1) no Stream usage found → say so and hand to `cometchat`; (2) the app's platform has no family in this pack (Vue, Unity, .NET, ...) → deliver the inventory + feature map as the report, change nothing; (3) the build was already failing before you started → record the pre-existing errors, migrate anyway, and label them as pre-existing.\n\n## Migration workflow (BAKED — do every step, in order)\nEvery step applies to every app, however small: a 3-file sample still has vendor users and history, so steps 4 (`toCometChatId`) and 8 (data script) are ALWAYS delivered. Only a step whose subject truly doesn't exist (no server → step 7) may be skipped, and it's listed under *Defaults taken* as `skipped: \u003Cwhy>`. A silent skip is a failed migration.\n1. **Detect.** `npx @cometchat\u002Fskills detect --json` → `framework`, `android_variant`, `existing_cometchat`, `migrate_from`. Resolve `\u003Cfamily>` exactly like the router (`peers.yaml` `dir_prefix`; per-platform targets in `references\u002Finventory.md` §Target family). Monorepo: migrate every package that uses Stream, including the server that mints tokens. `existing_cometchat: true` + Stream still present = a half-finished migration: resume it, don't redo it. Read `.cometchat\u002Fconfig.json` if it exists: its `appId`\u002F`region`\u002F`authKey` are THE credentials. Write them into the family's untracked env\u002Fsettings file (single-prompt contract), never ask. Before editing anything, run the app's build once and record whether it passed.\n2. **Inventory — the usage ledger.** Grep per `references\u002Finventory.md` (packages, imports, client creation, `connectUser`, SDK components, event subscriptions, channel queries, custom attachments, push devices, Video, Feeds, env vars, server tokens, webhooks, tests\u002Fmocks). Record every hit as `file:line → what it does`. Classify the app: **UI SDK mode** (Stream's React\u002FAngular\u002FRN\u002FFlutter\u002FiOS\u002FAndroid UI components render the chat) → the family's CometChat UI Kit replaces them; **client mode** (own UI on the low-level client: `stream-chat`, `stream_chat`, `StreamChat`\u002F`ChatClient`, `stream-chat-android-client`) → KEEP the app's UI and port its data layer to the family's CometChat Chat SDK; **mixed** → both.\n3. **Feature map.** For every Stream feature the ledger shows, look up its row in `references\u002Ffeature-map.md`, then check the listed CometChat id in the TARGET family's `features.json`. Present → **migrate**. Absent → check BOTH levels — UI Kit (`search_cometchat_docs \"\u003Cfeature> \u003Cplatform> ui kit\"`) AND Chat SDK\u002FREST (`... SDK`); documented at either → migrate (**no UI Kit drop-in is NOT unsupported**), built with the SDK method in the app's own UI (`RULES.md` → UI Kit first, SDK fallback). Mark **UNSUPPORTED only** when NEITHER has it — and **an empty MCP search is NOT proof**: follow the verification ladder (re-query with CometChat vocabulary → live-fetch the likely docs page → cross-check the family CATALOG) in `references\u002Ffeature-map.md` §Deciding unsupported, before any REMOVE. Never call a feature unsupported from memory or invent an API; if it truly can't be verified, KEEP it as `needs-verification`. **Every UNSUPPORTED row needs evidence in the report** — the `features.json` result + the exact UI Kit AND SDK queries you ran.\n4. **Install CometChat and wire the core** per `cometchat-\u003Cfamily>-core` (its install, `initFromSettings`, login gate, render order, env file). **Identity:** the CometChat UID is the app's existing Stream user ID passed through ONE shared `toCometChatId()` (`references\u002Fconcept-map.md` §IDs). The GUID is the channel **cid** (`type:id`) through the same helper. The client login, the server token endpoint AND the data script all call the SAME `toCometChatId()` — put it in a shared client module (`src\u002Fcometchat\u002Fids.ts`; native → §Native platforms) the login imports, and copy that body verbatim into the data script. **Route the current-user id through it at login even when the Stream id already looks valid** (it's a no-op then); confining `toCometChatId` to the data script is the #1 Stream migration miss and imports users under UIDs the app never logs in as (`references\u002Fconcept-map.md` §IDs). Login: the app minted Stream user tokens on a server (`createToken`) or used a `tokenProvider` → migrate that endpoint (step 7) and use the auth-token login; the app used `devToken()` → Auth Key login (dev only) + an action item to switch to tokens before production. **Keep every identity source, in the same order:** whatever decides the current user today (URL params, env vars like `VITE_USER_ID`, the auth provider, a stored ID, a demo fallback) still decides it after the migration. Only the Stream-token-derived path becomes the CometChat auth token. Dropping one silently logs a configured deployment in as someone else. **Returning users:** the app already persists who is signed in (localStorage, keychain, prefs, a cookie) from the vendor era. Gate the chat on CometChat's logged-in user, NOT that cached ID. On start, a stored ID with no CometChat session → run the same login path before rendering any CometChat component; if that fails → the sign-in screen. Otherwise every user who was signed in before the upgrade lands on a broken chat. **No UI Kit family for this app?** A headless \u002F vanilla-JS app that draws its own UI on the `stream-chat` client (no framework the pack ships a UI Kit for) has no `-core` to wire — do NOT stop. Install the CometChat **Chat SDK** for the platform (web → `@cometchat\u002Fchat-sdk-javascript`) and migrate the data layer straight onto it, taking every method from the SDK docs (`\u002Fsdk\u002F\u003Cplatform>\u002F*`). Keep the app's own UI; there is no UI Kit to install. This is client\u002FSDK mode with no framework core — the concept map's SDK\u002Fclient-mode section still applies.\n5. **Replace usage, file by file,** using `references\u002Fconcept-map.md`: client\u002F`connectUser` → CometChat init\u002Flogin; `ChannelList` → conversations; channel (`Channel`\u002F`Window`\u002F`MessageList`\u002F`MessageInput`\u002F`Thread`) → message pane; member-based distinct channels → user conversations; `client.on(...)`\u002F`channel.on(...)` → listeners (remove them on unmount); attachments\u002Fthreads\u002Freactions → the core + `-features` skill; theme\u002FCSS variables\u002Fi18n → `-customization`; Stream Video → `-calls` (or the headless calls peer); push devices → `-push`. Remove each Stream import as you replace its last use. **Both modes fetch from docs only:** UI Kit component props AND SDK method signatures come from the live docs (the family `core`'s `docs-map.md`), verified against the catalog — never written from memory or ported from the vendor's API shape.\n6. **Remove unsupported features FULLY.** For each UNSUPPORTED row: delete the feature's code path, its UI entry points (buttons, menu items, slash commands, routes, screens, settings toggles), state\u002Fstores, types, hooks, assets, tests, env vars, server endpoints and dependencies — no dead buttons, no commented-out blocks, no feature flags left on. Keep the surrounding screen working. **Activity Feeds has no CometChat equivalent**: feed screens, activity writers, follow buttons and the feed server calls all go, and are listed. Log each one for the report: feature · what it did · files changed · what users lose · the closest CometChat alternative (if any).\n7. **Server side.** Replace Stream token minting (`createToken`, `upsertUser` on sign-up) with a CometChat auth-token endpoint (REST: create the user if missing, then create an auth token — `\u002Frest-api\u002Fauth-tokens`, REST API key from server env only). Map Stream webhooks (`verifyWebhook`, `x-signature`) to CometChat webhooks (`\u002Frest-api\u002Fmanagement-apis\u002Fwebhooks\u002Foverview`); before-message-send hooks, custom-command endpoints and SQS\u002FSNS without an equivalent are REMOVED + listed. Replace other server-client calls with CometChat REST, or remove + list them.\n8. **Data migration script — write it, then run the import for the user.** Generate `scripts\u002Fcometchat-migration\u002F` per `references\u002Fdata-migration.md`: export users, channels, members and messages with the Stream server client → transform with the same `toCometChatId()` → import through the CometChat Data Import API. When the code migration is done, tell the user the **data-import script is ready** and ask for the credentials it needs — the source keys (`STREAM_API_KEY`, `STREAM_API_SECRET`) and the CometChat **App ID, Region and full-access REST API key**. (Asking for these is the ONE question the single-prompt contract allows; everything else still takes the documented default.) As soon as the user provides them, **RUN the import yourself** from env vars — never write the secrets into a repo file: a `--dry-run` first (show the users \u002F channels \u002F members \u002F messages counts), then the real import, then report what landed and what failed. Only messages within CometChat's **6-month retention window** import — tell the user to **reach out to CometChat to import messages older than 6 months**. If the user does not share credentials, leave running the script as an action item.\n9. **Uninstall Stream.** Remove every Stream dependency (package.json + regenerate the lockfile, Podfile\u002FSPM, Gradle, pubspec), CSS imports (`stream-chat-react\u002Fdist\u002Fcss\u002F...`, `@stream-io\u002Fstream-chat-css`), i18n setup, env vars, native config, and CI secrets references. Remove Stream-only peer dependencies (offline SQLite, audio recorder, ...) **only when nothing else imports them**. `react-native-reanimated`, `react-native-gesture-handler` and `react-native-svg` are usually shared: keep those. Re-run the package manager install. **On iOS\u002FSPM the ROOT manifest counts too**: a vendored-SDK repo declares the vendor in its own `Package.swift`\u002F`*.podspec` at the repo root, not just in the app's `.xcodeproj` — remove the dependency there AND delete any vendored `Framework\u002F*.xcframework`, or the vendor package is still declared after every call site is gone. Update the app's OWN docs (README, setup\u002Fdeploy guides, `.env.example`): setup steps, env var names and screenshots captions that describe Stream now describe CometChat. Rename Stream-named identifiers (`getstreamUserId` → `userId`).\n10. **Verify** (§Verify it works). Fix every build error you introduced. Don't run live tests unless asked (`RULES.md` → Verification scope).\n11. **Report.** Write `COMETCHAT_MIGRATION.md` at the repo root from `references\u002Freport-template.md`, then END your reply with its two lists pasted in full: **Removed — not available in CometChat** and **Your action items**. This final list is the deliverable the user asked for; never skip it, even if nothing was removed (say \"none\").\n\n## Common pitfalls\n- **Accessibility is never a \"missing feature\".** Stream-provided skip links, focus management, live regions and keyboard shortcuts are plain HTML\u002FARIA\u002Fhost code. Re-create them in the app against the new CometChat layout, and never list them as Removed. Losing them is a regression, not an honest removal.\n- **The provider swap moves wrapper elements.** `CometChatProvider` (and, on web, `CometChatErrorBoundary`) render wrapper elements exactly where the vendor's provider sat. If they now wrap the app's own shell\u002Fheader, each wrapper needs a height in the chain, or the chat renders at 0px while the build passes. Follow the core's layout reference, and check the chain from the root element down to the conversation list.\n- **IDs that CometChat rejects or merges.** UIDs\u002FGUIDs are alpha-dash (`a-z 0-9 - _`), max 100 characters, and lowercased. Stream cids contain `:`, member-based channel IDs start with `!members-`, and user IDs can contain `@` or `.`. Sanitize with one deterministic function everywhere, and always feed it the full **cid**, so `messaging:general` and `team:general` stay distinct.\n- **1:1 chats are not groups.** A member-based channel (`!members-...` ID, created from exactly two members) becomes a CometChat *user* conversation, not a two-person group.\n- **Livestream channels and large groups.** CometChat sends receipts and typing indicators only in groups up to 300 members (100,000 without them). List that as a behavior change for big channels.\n- **Leftover subscriptions.** Every `client.on(...)`\u002F`channel.on(...)`\u002F`useChatContext` event path needs a CometChat listener that is also removed on unmount\u002Fdispose. Missing removals cause duplicate messages.\n- **Custom attachments and `extraData`.** Stream custom fields ride on users, channels and messages; move them into CometChat metadata\u002Fcustom messages, or they silently disappear.\n- **Half-removed features.** Deleting the API call but leaving the slash command, button or route is a dead end (`RULES.md` → Default-on affordances). Remove the entry point too.\n- **Shared native dependencies.** Removing a Stream peer dependency the app also uses (Reanimated, gesture handler, SVG, image picker) breaks unrelated screens. Grep for other importers first.\n- **Never delete non-Stream code** that just shares a file with Stream code. Rewire it.\n\n## Native platforms (Android · iOS · Flutter) — NOT done until the platform build passes\nNative builds (Android\u002FiOS\u002FFlutter) have extra REQUIRED steps beyond editing code — bump the sample toolchain to the `-core` build floors, add the kit dep AND wire `initFromSettings` in the app entry, port `toCometChatId` to the client language, edit `.pbxproj`\u002F`.xcscheme` as structured build graphs (never a text scrub), and RUN the platform build. **A native migration is NOT done until you have followed `references\u002Fnative-build.md` in full** — open it and work through every step; it is mandatory, not optional.\n\n## Verify it works\n- The app builds\u002Ftype-checks with the family's normal command (the core skill's \"Verify it works\").\n- **RUN it and read the logs — a compile is NOT a working app (do this; don't skip).** When you're done implementing, START the app and confirm it LOADS with the chat surface rendered and NO errors: web → the dev server (or build + preview), open it, watch the **browser console** + the dev-server terminal; native → the platform run + logcat \u002F Xcode console \u002F `flutter` logs. Fix EVERY runtime error you introduced before declaring done — a `Cannot read properties of undefined` from a half-migrated reference, or an SDK enum\u002Fclass read at module-load before the SDK is ready, is a migration bug, not the user's problem (hand off to `cometchat-\u003Cfamily>-troubleshooting` for symptom → fix). If the app genuinely can't be started here (no dev env \u002F needs a device), SAY SO and give the user the exact run command + what to watch for — never silently skip this.\n- **Zero Stream residue — run exactly this, over ALL file types (docs included):** `grep -rIilE 'stream-chat|stream_chat|@stream-io|getstream|StreamChat|StreamVideo' . --exclude-dir=node_modules --exclude-dir=.git --exclude-dir=dist --exclude-dir=build --exclude-dir=.claude --exclude-dir=Pods --exclude-dir=.dart_tool --exclude-dir=.gradle | grep -vE 'COMETCHAT_MIGRATION.md|scripts\u002Fcometchat-migration'` → must print nothing (repeated `--exclude-dir=` flags on purpose: a `{a,b}` brace list is rejected by the coding agent's command-permission parser, so the check silently never runs). The ONE allowed mention is a single provenance comment above `toCometChatId()`; code identifiers, README lines and env names are residue, not \"expected\". **This includes a \"migrated from \u003Cvendor>\" line in the README or any doc you write** — a provenance note reads as helpful and is still residue; the migration report is where that belongs, and it is already exempt. Rewrite the app's own README so it describes CometChat, naming the vendor nowhere. The same goes for every other doc the repo ships — `CHANGELOG.md`, `docs\u002F`, `changelogs\u002F`, a vendored SDK's own release notes: if a file is not the migration report, it must not name the vendor. Delete the ones that document the vendor's product rather than your app.\n- `scripts\u002Fcometchat-migration\u002Fmigrate.mjs` + `README.md` exist — **even for a demo\u002Fsample app with no data of its own** (it is for the user's real data; step 8 is never skipped).\n- Every CometChat symbol you emitted exists in the family catalog. Every migrated feature is in `features.json` or the docs. Every UNSUPPORTED item is in the report's Removed list with its files.\n- The server token endpoint, the client login and the data script all call the same `toCometChatId()` — from a shared client module, and at login even for already-valid ids (not only inside the data script).\n- **Runtime shape, statically checked:** every element from the root to the conversation list has a height (wrappers included). A user who was signed in before the migration is logged in to CometChat again before the chat renders. No real secret sits in a git-tracked file (`git ls-files` each file you wrote credentials to).\n","> **Ground truth:** the STREAM side (what to look for) is baked in `references\u002Finventory.md` + `references\u002Ffeature-map.md` — confirm each hit by reading the user's code. The COMETCHAT side is never from memory: symbols come from the target family's skills + catalog, feature existence from that family's `features.json`, signatures from the docs via the family's `-core\u002Freferences\u002Fdocs-map.md` (Docs MCP first — `RULES.md` → Fetch discipline). REST pages live under `DOCS_BASE` = `https:\u002F\u002Fwww.cometchat.com\u002Fdocs`.\n\n## Companion skills (read first)\n- `cometchat-\u003Cfamily>-core` — the init → login → render the migrated app lands on. `\u003Cfamily>` is resolved in step 1; this skill ASSUMES that core and never restates its code.\n- `cometchat-\u003Cfamily>-components` \u002F `-features` \u002F `-calls` \u002F `-push` \u002F `-customization` — pulled in only for the Stream features the inventory finds.\n\n## Use this skill when\nThe user asks to move an app off Stream: \"migrate my app from GetStream\u002FStream to CometChat\", \"replace Stream Chat\", \"switch to CometChat\", or \"migrate my app to CometChat\" when `npx @cometchat\u002Fskills detect --json` reports `migrate_from` with vendor `getstream`. Sendbird apps → `cometchat-migrate-from-sendbird`. An app with BOTH vendors: run both skills, one after the other, into one report.\n**Data only** (\"migrate only my data\", \"import my Stream users and messages\", \"don't change my code\", or the app already runs on CometChat) → follow `references\u002Fdata-only.md` INSTEAD of the workflow below: it writes and runs the data script and changes nothing else.\n\n## The single-prompt contract (read before step 1)\nThe migration request IS the approval (`RULES.md` → Competitor migration). Run every step below to the end in this one turn:\n- **Docs MCP check comes first.** No `search_cometchat_docs` tool? Say so in your first message, before any edit, with how to connect it (`RULES.md` → Canonical doc channel), then continue on web docs. Note it in the report.\n- **Do not stop to ask.** No onboarding plan\u002Fapprove gate, no clarification questions. Where a companion skill would ask, take the default written here, and record it under *Defaults taken* in the report.\n- **Safety net instead of questions:** in a git repo, first `git switch -c cometchat-migration` (carries any uncommitted work along; mention that in the report). Never commit, push, or rewrite history. No git → proceed and say so in the report.\n- **Removing Stream is the requested outcome** — `RULES.md`'s append-never-replace does not protect Stream code. It still protects everything else: touch non-chat code only to rewire it.\n- **Credentials: never ask, never provision.** Reuse `.cometchat\u002Fconfig.json` or existing CometChat env values if present; otherwise write the family's env\u002Fsettings file with clearly-named placeholders so the build still compiles, and make \"add your CometChat credentials\" action item #1. **Never write a real key into a git-tracked file:** check `git ls-files \u003Cfile>` first. If the file is tracked, put real values in the untracked local variant the framework reads (Vite\u002FNext `.env.local`, Android `local.properties`, ...) and keep placeholders in the tracked file. Adding a tracked file to `.gitignore` does NOT untrack it. The server's REST API key only ever goes into an untracked file or the hosting env.\n- **Only three STOPs:** (1) no Stream usage found → say so and hand to `cometchat`; (2) the app's platform has no family in this pack (Vue, Unity, .NET, ...) → deliver the inventory + feature map as the report, change nothing; (3) the build was already failing before you started → record the pre-existing errors, migrate anyway, and label them as pre-existing.\n\n## Migration workflow (BAKED — do every step, in order)\nEvery step applies to every app, however small: a 3-file sample still has vendor users and history, so steps 4 (`toCometChatId`) and 8 (data script) are ALWAYS delivered. Only a step whose subject truly doesn't exist (no server → step 7) may be skipped, and it's listed under *Defaults taken* as `skipped: \u003Cwhy>`. A silent skip is a failed migration.\n1. **Detect.** `npx @cometchat\u002Fskills detect --json` → `framework`, `android_variant`, `existing_cometchat`, `migrate_from`. Resolve `\u003Cfamily>` exactly like the router (`peers.yaml` `dir_prefix`; per-platform targets in `references\u002Finventory.md` §Target family). Monorepo: migrate every package that uses Stream, including the server that mints tokens. `existing_cometchat: true` + Stream still present = a half-finished migration: resume it, don't redo it. Read `.cometchat\u002Fconfig.json` if it exists: its `appId`\u002F`region`\u002F`authKey` are THE credentials. Write them into the family's untracked env\u002Fsettings file (single-prompt contract), never ask. Before editing anything, run the app's build once and record whether it passed.\n2. **Inventory — the usage ledger.** Grep per `references\u002Finventory.md` (packages, imports, client creation, `connectUser`, SDK components, event subscriptions, channel queries, custom attachments, push devices, Video, Feeds, env vars, server tokens, webhooks, tests\u002Fmocks). Record every hit as `file:line → what it does`. Classify the app: **UI SDK mode** (Stream's React\u002FAngular\u002FRN\u002FFlutter\u002FiOS\u002FAndroid UI components render the chat) → the family's CometChat UI Kit replaces them; **client mode** (own UI on the low-level client: `stream-chat`, `stream_chat`, `StreamChat`\u002F`ChatClient`, `stream-chat-android-client`) → KEEP the app's UI and port its data layer to the family's CometChat Chat SDK; **mixed** → both.\n3. **Feature map.** For every Stream feature the ledger shows, look up its row in `references\u002Ffeature-map.md`, then check the listed CometChat id in the TARGET family's `features.json`. Present → **migrate**. Absent → check BOTH levels — UI Kit (`search_cometchat_docs \"\u003Cfeature> \u003Cplatform> ui kit\"`) AND Chat SDK\u002FREST (`... SDK`); documented at either → migrate (**no UI Kit drop-in is NOT unsupported**), built with the SDK method in the app's own UI (`RULES.md` → UI Kit first, SDK fallback). Mark **UNSUPPORTED only** when NEITHER has it — and **an empty MCP search is NOT proof**: follow the verification ladder (re-query with CometChat vocabulary → live-fetch the likely docs page → cross-check the family CATALOG) in `references\u002Ffeature-map.md` §Deciding unsupported, before any REMOVE. Never call a feature unsupported from memory or invent an API; if it truly can't be verified, KEEP it as `needs-verification`. **Every UNSUPPORTED row needs evidence in the report** — the `features.json` result + the exact UI Kit AND SDK queries you ran.\n4. **Install CometChat and wire the core** per `cometchat-\u003Cfamily>-core` (its install, `initFromSettings`, login gate, render order, env file). **Identity:** the CometChat UID is the app's existing Stream user ID passed through ONE shared `toCometChatId()` (`references\u002Fconcept-map.md` §IDs). The GUID is the channel **cid** (`type:id`) through the same helper. The client login, the server token endpoint AND the data script all call the SAME `toCometChatId()` — put it in a shared client module (`src\u002Fcometchat\u002Fids.ts`; native → §Native platforms) the login imports, and copy that body verbatim into the data script. **Route the current-user id through it at login even when the Stream id already looks valid** (it's a no-op then); confining `toCometChatId` to the data script is the #1 Stream migration miss and imports users under UIDs the app never logs in as (`references\u002Fconcept-map.md` §IDs). Login: the app minted Stream user tokens on a server (`createToken`) or used a `tokenProvider` → migrate that endpoint (step 7) and use the auth-token login; the app used `devToken()` → Auth Key login (dev only) + an action item to switch to tokens before production. **Keep every identity source, in the same order:** whatever decides the current user today (URL params, env vars like `VITE_USER_ID`, the auth provider, a stored ID, a demo fallback) still decides it after the migration. Only the Stream-token-derived path becomes the CometChat auth token. Dropping one silently logs a configured deployment in as someone else. **Returning users:** the app already persists who is signed in (localStorage, keychain, prefs, a cookie) from the vendor era. Gate the chat on CometChat's logged-in user, NOT that cached ID. On start, a stored ID with no CometChat session → run the same login path before rendering any CometChat component; if that fails → the sign-in screen. Otherwise every user who was signed in before the upgrade lands on a broken chat. **No UI Kit family for this app?** A headless \u002F vanilla-JS app that draws its own UI on the `stream-chat` client (no framework the pack ships a UI Kit for) has no `-core` to wire — do NOT stop. Install the CometChat **Chat SDK** for the platform (web → `@cometchat\u002Fchat-sdk-javascript`) and migrate the data layer straight onto it, taking every method from the SDK docs (`\u002Fsdk\u002F\u003Cplatform>\u002F*`). Keep the app's own UI; there is no UI Kit to install. This is client\u002FSDK mode with no framework core — the concept map's SDK\u002Fclient-mode section still applies.\n5. **Replace usage, file by file,** using `references\u002Fconcept-map.md`: client\u002F`connectUser` → CometChat init\u002Flogin; `ChannelList` → conversations; channel (`Channel`\u002F`Window`\u002F`MessageList`\u002F`MessageInput`\u002F`Thread`) → message pane; member-based distinct channels → user conversations; `client.on(...)`\u002F`channel.on(...)` → listeners (remove them on unmount); attachments\u002Fthreads\u002Freactions → the core + `-features` skill; theme\u002FCSS variables\u002Fi18n → `-customization`; Stream Video → `-calls` (or the headless calls peer); push devices → `-push`. Remove each Stream import as you replace its last use. **Both modes fetch from docs only:** UI Kit component props AND SDK method signatures come from the live docs (the family `core`'s `docs-map.md`), verified against the catalog — never written from memory or ported from the vendor's API shape.\n6. **Remove unsupported features FULLY.** For each UNSUPPORTED row: delete the feature's code path, its UI entry points (buttons, menu items, slash commands, routes, screens, settings toggles), state\u002Fstores, types, hooks, assets, tests, env vars, server endpoints and dependencies — no dead buttons, no commented-out blocks, no feature flags left on. Keep the surrounding screen working. **Activity Feeds has no CometChat equivalent**: feed screens, activity writers, follow buttons and the feed server calls all go, and are listed. Log each one for the report: feature · what it did · files changed · what users lose · the closest CometChat alternative (if any).\n7. **Server side.** Replace Stream token minting (`createToken`, `upsertUser` on sign-up) with a CometChat auth-token endpoint (REST: create the user if missing, then create an auth token — `\u002Frest-api\u002Fauth-tokens`, REST API key from server env only). Map Stream webhooks (`verifyWebhook`, `x-signature`) to CometChat webhooks (`\u002Frest-api\u002Fmanagement-apis\u002Fwebhooks\u002Foverview`); before-message-send hooks, custom-command endpoints and SQS\u002FSNS without an equivalent are REMOVED + listed. Replace other server-client calls with CometChat REST, or remove + list them.\n8. **Data migration script — write it, then run the import for the user.** Generate `scripts\u002Fcometchat-migration\u002F` per `references\u002Fdata-migration.md`: export users, channels, members and messages with the Stream server client → transform with the same `toCometChatId()` → import through the CometChat Data Import API. When the code migration is done, tell the user the **data-import script is ready** and ask for the credentials it needs — the source keys (`STREAM_API_KEY`, `STREAM_API_SECRET`) and the CometChat **App ID, Region and full-access REST API key**. (Asking for these is the ONE question the single-prompt contract allows; everything else still takes the documented default.) As soon as the user provides them, **RUN the import yourself** from env vars — never write the secrets into a repo file: a `--dry-run` first (show the users \u002F channels \u002F members \u002F messages counts), then the real import, then report what landed and what failed. Only messages within CometChat's **6-month retention window** import — tell the user to **reach out to CometChat to import messages older than 6 months**. If the user does not share credentials, leave running the script as an action item.\n9. **Uninstall Stream.** Remove every Stream dependency (package.json + regenerate the lockfile, Podfile\u002FSPM, Gradle, pubspec), CSS imports (`stream-chat-react\u002Fdist\u002Fcss\u002F...`, `@stream-io\u002Fstream-chat-css`), i18n setup, env vars, native config, and CI secrets references. Remove Stream-only peer dependencies (offline SQLite, audio recorder, ...) **only when nothing else imports them**. `react-native-reanimated`, `react-native-gesture-handler` and `react-native-svg` are usually shared: keep those. Re-run the package manager install. **On iOS\u002FSPM the ROOT manifest counts too**: a vendored-SDK repo declares the vendor in its own `Package.swift`\u002F`*.podspec` at the repo root, not just in the app's `.xcodeproj` — remove the dependency there AND delete any vendored `Framework\u002F*.xcframework`, or the vendor package is still declared after every call site is gone. Update the app's OWN docs (README, setup\u002Fdeploy guides, `.env.example`): setup steps, env var names and screenshots captions that describe Stream now describe CometChat. Rename Stream-named identifiers (`getstreamUserId` → `userId`).\n10. **Verify** (§Verify it works). Fix every build error you introduced. Don't run live tests unless asked (`RULES.md` → Verification scope).\n11. **Report.** Write `COMETCHAT_MIGRATION.md` at the repo root from `references\u002Freport-template.md`, then END your reply with its two lists pasted in full: **Removed — not available in CometChat** and **Your action items**. This final list is the deliverable the user asked for; never skip it, even if nothing was removed (say \"none\").\n\n## Common pitfalls\n- **Accessibility is never a \"missing feature\".** Stream-provided skip links, focus management, live regions and keyboard shortcuts are plain HTML\u002FARIA\u002Fhost code. Re-create them in the app against the new CometChat layout, and never list them as Removed. Losing them is a regression, not an honest removal.\n- **The provider swap moves wrapper elements.** `CometChatProvider` (and, on web, `CometChatErrorBoundary`) render wrapper elements exactly where the vendor's provider sat. If they now wrap the app's own shell\u002Fheader, each wrapper needs a height in the chain, or the chat renders at 0px while the build passes. Follow the core's layout reference, and check the chain from the root element down to the conversation list.\n- **IDs that CometChat rejects or merges.** UIDs\u002FGUIDs are alpha-dash (`a-z 0-9 - _`), max 100 characters, and lowercased. Stream cids contain `:`, member-based channel IDs start with `!members-`, and user IDs can contain `@` or `.`. Sanitize with one deterministic function everywhere, and always feed it the full **cid**, so `messaging:general` and `team:general` stay distinct.\n- **1:1 chats are not groups.** A member-based channel (`!members-...` ID, created from exactly two members) becomes a CometChat *user* conversation, not a two-person group.\n- **Livestream channels and large groups.** CometChat sends receipts and typing indicators only in groups up to 300 members (100,000 without them). List that as a behavior change for big channels.\n- **Leftover subscriptions.** Every `client.on(...)`\u002F`channel.on(...)`\u002F`useChatContext` event path needs a CometChat listener that is also removed on unmount\u002Fdispose. Missing removals cause duplicate messages.\n- **Custom attachments and `extraData`.** Stream custom fields ride on users, channels and messages; move them into CometChat metadata\u002Fcustom messages, or they silently disappear.\n- **Half-removed features.** Deleting the API call but leaving the slash command, button or route is a dead end (`RULES.md` → Default-on affordances). Remove the entry point too.\n- **Shared native dependencies.** Removing a Stream peer dependency the app also uses (Reanimated, gesture handler, SVG, image picker) breaks unrelated screens. Grep for other importers first.\n- **Never delete non-Stream code** that just shares a file with Stream code. Rewire it.\n\n## Native platforms (Android · iOS · Flutter) — NOT done until the platform build passes\nNative builds (Android\u002FiOS\u002FFlutter) have extra REQUIRED steps beyond editing code — bump the sample toolchain to the `-core` build floors, add the kit dep AND wire `initFromSettings` in the app entry, port `toCometChatId` to the client language, edit `.pbxproj`\u002F`.xcscheme` as structured build graphs (never a text scrub), and RUN the platform build. **A native migration is NOT done until you have followed `references\u002Fnative-build.md` in full** — open it and work through every step; it is mandatory, not optional.\n\n## Verify it works\n- The app builds\u002Ftype-checks with the family's normal command (the core skill's \"Verify it works\").\n- **RUN it and read the logs — a compile is NOT a working app (do this; don't skip).** When you're done implementing, START the app and confirm it LOADS with the chat surface rendered and NO errors: web → the dev server (or build + preview), open it, watch the **browser console** + the dev-server terminal; native → the platform run + logcat \u002F Xcode console \u002F `flutter` logs. Fix EVERY runtime error you introduced before declaring done — a `Cannot read properties of undefined` from a half-migrated reference, or an SDK enum\u002Fclass read at module-load before the SDK is ready, is a migration bug, not the user's problem (hand off to `cometchat-\u003Cfamily>-troubleshooting` for symptom → fix). If the app genuinely can't be started here (no dev env \u002F needs a device), SAY SO and give the user the exact run command + what to watch for — never silently skip this.\n- **Zero Stream residue — run exactly this, over ALL file types (docs included):** `grep -rIilE 'stream-chat|stream_chat|@stream-io|getstream|StreamChat|StreamVideo' . --exclude-dir=node_modules --exclude-dir=.git --exclude-dir=dist --exclude-dir=build --exclude-dir=.claude --exclude-dir=Pods --exclude-dir=.dart_tool --exclude-dir=.gradle | grep -vE 'COMETCHAT_MIGRATION.md|scripts\u002Fcometchat-migration'` → must print nothing (repeated `--exclude-dir=` flags on purpose: a `{a,b}` brace list is rejected by the coding agent's command-permission parser, so the check silently never runs). The ONE allowed mention is a single provenance comment above `toCometChatId()`; code identifiers, README lines and env names are residue, not \"expected\". **This includes a \"migrated from \u003Cvendor>\" line in the README or any doc you write** — a provenance note reads as helpful and is still residue; the migration report is where that belongs, and it is already exempt. Rewrite the app's own README so it describes CometChat, naming the vendor nowhere. The same goes for every other doc the repo ships — `CHANGELOG.md`, `docs\u002F`, `changelogs\u002F`, a vendored SDK's own release notes: if a file is not the migration report, it must not name the vendor. Delete the ones that document the vendor's product rather than your app.\n- `scripts\u002Fcometchat-migration\u002Fmigrate.mjs` + `README.md` exist — **even for a demo\u002Fsample app with no data of its own** (it is for the user's real data; step 8 is never skipped).\n- Every CometChat symbol you emitted exists in the family catalog. Every migrated feature is in `features.json` or the docs. Every UNSUPPORTED item is in the report's Removed list with its files.\n- The server token endpoint, the client login and the data script all call the same `toCometChatId()` — from a shared client module, and at login even for already-valid ids (not only inside the data script).\n- **Runtime shape, statically checked:** every element from the root to the conversation list has a height (wrappers included). A user who was signed in before the migration is logged in to CometChat again before the chat renders. No real secret sits in a git-tracked file (`git ls-files` each file you wrote credentials to).\n",{"name":5,"license":15,"metadata":56,"description":7,"compatibility":60},{"tags":57,"author":58,"version":59},"cometchat migration getstream stream stream-chat competitor switch replace port uikit sdk calls data-import","CometChat","1.0.0","FROM Stream Chat (`stream-chat` JS client; stream-chat-react, stream-chat-angular, stream-chat-react-native \u002F stream-chat-expo, stream_chat_flutter, StreamChat\u002FStreamChatUI\u002FStreamChatSwiftUI, io.getstream:stream-chat-android-*), Stream Video, Stream Activity Feeds → TO the CometChat family this pack detects (peers.yaml): React UI Kit v7, Angular v5, React Native v5, iOS v5, Android v6, Flutter v6, plus the headless Chat\u002FCalls SDKs. Node >=18 for the data-migration script.","main","cebc3dce495d7eb80d3b1d5841f877a4a92e162d","plugins\u002Fcometchat\u002Fcometchat-skills\u002Fskills\u002Fcometchat-migrate-from-getstream",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":72,"prompt":82,"zipAvailable":83},[73,76,79],{"tool":74,"command":75},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill cometchat-migrate-from-getstream",{"tool":77,"command":78},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill cometchat-migrate-from-getstream",{"tool":80,"command":81},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill cometchat-migrate-from-getstream","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fcometchat\u002Fcometchat-skills\u002Fskills\u002Fcometchat-migrate-from-getstream\u002FSKILL.md",true,[85,91,95,99,103,107,111],{"path":86,"resourceType":87,"resourceTypeDesc":88,"sizeBytes":89,"sourceHtmlUrl":90},"references\u002Fconcept-map.md","REFERENCE","参考文档",11483,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fcometchat\u002Fcometchat-skills\u002Fskills\u002Fcometchat-migrate-from-getstream\u002Freferences\u002Fconcept-map.md",{"path":92,"resourceType":87,"resourceTypeDesc":88,"sizeBytes":93,"sourceHtmlUrl":94},"references\u002Fdata-migration.md",9320,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fcometchat\u002Fcometchat-skills\u002Fskills\u002Fcometchat-migrate-from-getstream\u002Freferences\u002Fdata-migration.md",{"path":96,"resourceType":87,"resourceTypeDesc":88,"sizeBytes":97,"sourceHtmlUrl":98},"references\u002Fdata-only.md",3261,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fcometchat\u002Fcometchat-skills\u002Fskills\u002Fcometchat-migrate-from-getstream\u002Freferences\u002Fdata-only.md",{"path":100,"resourceType":87,"resourceTypeDesc":88,"sizeBytes":101,"sourceHtmlUrl":102},"references\u002Ffeature-map.md",11183,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fcometchat\u002Fcometchat-skills\u002Fskills\u002Fcometchat-migrate-from-getstream\u002Freferences\u002Ffeature-map.md",{"path":104,"resourceType":87,"resourceTypeDesc":88,"sizeBytes":105,"sourceHtmlUrl":106},"references\u002Finventory.md",9086,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fcometchat\u002Fcometchat-skills\u002Fskills\u002Fcometchat-migrate-from-getstream\u002Freferences\u002Finventory.md",{"path":108,"resourceType":87,"resourceTypeDesc":88,"sizeBytes":109,"sourceHtmlUrl":110},"references\u002Fnative-build.md",2464,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fcometchat\u002Fcometchat-skills\u002Fskills\u002Fcometchat-migrate-from-getstream\u002Freferences\u002Fnative-build.md",{"path":112,"resourceType":87,"resourceTypeDesc":88,"sizeBytes":113,"sourceHtmlUrl":114},"references\u002Freport-template.md",5451,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fcometchat\u002Fcometchat-skills\u002Fskills\u002Fcometchat-migrate-from-getstream\u002Freferences\u002Freport-template.md",[116,125,133,141,149,157],{"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":124},"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":126,"name":127,"nameZh":6,"description":128,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":129,"sourceHtmlUrl":130,"categories":131,"keywords":132,"publishedAt":124},"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":134,"name":135,"nameZh":6,"description":136,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":137,"sourceHtmlUrl":138,"categories":139,"keywords":140,"publishedAt":124},"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":142,"name":143,"nameZh":6,"description":144,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":145,"sourceHtmlUrl":146,"categories":147,"keywords":148,"publishedAt":124},"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":150,"name":151,"nameZh":6,"description":152,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":153,"sourceHtmlUrl":154,"categories":155,"keywords":156,"publishedAt":124},"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":158,"name":159,"nameZh":6,"description":160,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":161,"sourceHtmlUrl":162,"categories":163,"keywords":164,"publishedAt":124},"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",[],[]]