[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MFHVW4RMADA46F31WN9ZD1":3,"skill-same:01M6MFHVW4RMADA46F31WN9ZD1":79},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":45,"linkOnly":46,"markdownContent":47,"markdownBody":48,"frontMatter":49,"refName":55,"commitSha":56,"skillDirectory":57,"forksCount":58,"repositoryHtmlUrl":59,"repositoryHomepageUrl":60,"ownerHtmlUrl":61,"ownerBlogUrl":62,"ownerDescription":63,"updatedAt":64,"install":65,"resources":78},"01M6MFHVW4RMADA46F31WN9ZD1","cometchat-react-native-troubleshooting",null,"Diagnose a broken CometChat React Native integration — blank chat screen, gestures not responding, Android build failures, calls not ringing, notifications not arriving, custom UI not showing. Symptom to root cause to fix. Triggers: CometChat React Native not working, blank chat screen RN, gestures not working chat, android build fails CometChat, calls not ringing RN, my custom view isn't showing.","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-react-native-troubleshooting\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44],"cometchat react native troubleshooting","cometchat","troubleshooting","react native","react","native","broken","fix","errors","debugging","notifications","screen","react-native","android build","my","ui","diagnostics","gestures","view","diagnose","calls","2026-11-10 10:12:30",false,"---\nname: cometchat-react-native-troubleshooting\ndescription: \"Diagnose a broken CometChat React Native integration — blank chat screen, gestures not responding, Android build failures, calls not ringing, notifications not arriving, custom UI not showing. Symptom to root cause to fix. Triggers: CometChat React Native not working, blank chat screen RN, gestures not working chat, android build fails CometChat, calls not ringing RN, my custom view isn't showing.\"\nlicense: \"MIT\"\ncompatibility: \"React Native >=0.77; @cometchat\u002Fchat-uikit-react-native ^5.4.0\"\nmetadata:\n  author: \"CometChat\"\n  version: \"1.0.0\"\n  tags: \"chat cometchat react-native troubleshooting diagnostics errors debugging\"\n---\n\n> **Ground truth:** `@cometchat\u002Fchat-uikit-react-native@5` + catalog `rn-v5.json`.\n> Docs: `\u002Fui-kit\u002Freact-native\u002Ftroubleshooting`.\n\n## Companion skills (read first)\n- `cometchat-react-native-core` — install, provider chain, init→login→render. Assumed, not repeated here.\n\n## Use this skill when\n- anything is broken and the error does not say why — which on React Native is most of the time\n\n## Prerequisites & install\nNone.\n\n## Read this first: RN failures usually name the wrong thing\nThree properties make React Native bugs hard to read, and all three appear below:\n- **native modules fail at MOUNT, not at build** — so the app starts, then a screen explodes\n- **the error names a peer dependency**, not CometChat — `gesture-handler`, `svg`, `video`\n- **an unknown prop is silently ignored** — no error, nothing renders\n\nSo \"it says nothing about CometChat\" is not evidence the problem is elsewhere.\n\n## Symptom → root cause → fix\n\n### Blank chat screen, no error\n| Cause | Fix |\n|---|---|\n| rendering before `login()` resolved | gate render on a `loggedIn` flag; `init` → `login` → render |\n| `initFromSettings()` failed | you **cannot** catch it — `CometChatUIKit.initFromSettings()` swallows init errors (its rejection handler is a no-op), so `await`\u002F`.catch()` see nothing. Instead assert on the NEXT step: `await login(...)` (which DOES reject) or check `await CometChatUIKit.getLoggedInUser()`; a bad appId\u002Fregion surfaces there as an auth failure |\n| an ancestor is not `flex: 1` | every ancestor `flex: 1`; a scrolling column also needs `minHeight: 0` |\n\n### The UI renders but nothing responds to touch\n**`GestureHandlerRootView` is missing, or is not outermost, or lacks `flex: 1`.**\nNo error is thrown. On bare RN also confirm `import 'react-native-gesture-handler'` is the **first\nline of `index.js`** — wrong ordering there often works in debug and crashes in release.\n\n### `NativeModule ... null` \u002F \"cannot read property of null\" on a chat screen\nA native peer is missing or unlinked. Install the full peer list (`core`), then `pod install` (bare)\nor a fresh development build (Expo). **Metro reload does not pick up native changes — rebuild.**\n\n### Android build fails, error never mentions CometChat\n`@react-native-async-storage\u002Fasync-storage` must be `^2.1.2` — the Chat SDK requires it at load and the Calls SDK peer-requires 2.x. Unpinned resolves to 3.x, which fails `npm install @cometchat\u002Fcalls-sdk-react-native@5` with ERESOLVE. Check: `npm ls @react-native-async-storage\u002Fasync-storage`.\n\n### Expo: works in Expo Go until a chat screen opens\nExpo Go **cannot** load custom native modules. Use a development build (`npx expo run:ios`). There is\nno workaround.\n\n### My custom view does not appear\n**Slot props are PascalCase on RN** — `ItemView`, not `itemView`. React's casing is silently ignored:\nno error, nothing renders. Same class of bug as a typo'd prop name.\n\n### Two headers stacked on the message screen\nThe navigator's header plus `CometChatMessageHeader`. Set `headerShown: false` on that screen.\n\n### The composer is hidden when the keyboard opens\nA fixed height somewhere in the ancestor chain, or the message screen is nested **inside** the tab\nnavigator so the tab bar overlaps it. Put the message screen on the stack **above** the tabs.\n\n### Sending a message throws on iOS (React Native >= 0.87)\nReact Native **0.87 removed `InteractionManager` from core**, and `CometChatMessageComposer` (kit\nthrough 5.5.0) still calls `InteractionManager.runAfterInteractions()` in four **iOS-only** branches\nof its send path. Tapping send throws and the message never leaves the device. Android is unaffected;\nso is RN \u003C= 0.86, where the export is deprecated but still resolves — which is why the same code\nsends fine on an older app and dies on a fresh template.\n\n| Where | What you see |\n|---|---|\n| dev build | `Uncaught Error: InteractionManager has been removed from react-native core. Please refactor long tasks into smaller ones, and use 'requestIdleCallback' instead.` in `CometChatMessageComposer` -> `sendTextMessage` |\n| release build | the same line reads `undefined` -> `TypeError: Cannot read property 'runAfterInteractions' of undefined` |\n| CI | **nothing** — it typechecks, bundles and builds on both platforms; only a person tapping send sees it |\n\nUntil the kit drops the call, restore a minimal implementation **before the kit loads** — the first\nimport in `index.js`:\n\n```js\n\u002F\u002F interactionManagerCompat.js — delete when the kit stops calling InteractionManager.\nconst ReactNative = require('react-native');\n\nconst missing = () => {\n  try {\n    return !ReactNative.InteractionManager;\n  } catch {\n    return true; \u002F\u002F RN >= 0.87 in __DEV__: the getter throws.\n  }\n};\n\nif (missing()) {\n  Object.defineProperty(ReactNative, 'InteractionManager', {\n    configurable: true,\n    get: () => ({\n      runAfterInteractions: (task) => {\n        const run = () => (typeof task === 'function' ? task() : task && task.gen && task.gen());\n        let settle;\n        const ran = new Promise((resolve) => { settle = resolve; });\n        const timer = setTimeout(() => { run(); settle(); }, 0);   \u002F\u002F resolve AFTER the task runs\n        return {\n          then: (onResolve, onReject) => ran.then(onResolve, onReject),\n          done: (onDone) => { ran.then(onDone); },\n          cancel: () => clearTimeout(timer),\n        };\n      },\n      createInteractionHandle: () => 0,\n      clearInteractionHandle: () => {},\n      setDeadline: () => {},\n      addListener: () => ({ remove: () => {} }),\n    }),\n  });\n}\n```\n\n### `ReferenceError: Property '\u003Cname>' doesn't exist` right after a `try`\u002F`catch`\nHermes loses a `catch (error)` binding that is only read inside a closure created in the same block —\n`catch (error) { setLogs((prev) => [describe(error), ...prev]) }` throws the first time the catch\nruns, while the identical code with the value read first works. It typechecks and bundles either way.\nRead the caught value into a local, then use the local inside the closure.\n\n### Calls do not ring\n| Cause | Fix |\n|---|---|\n| `CometChatIncomingCall` mounted inside one screen | mount it **once above the navigator** |\n| calls SDK installed but pods not run | `pod install` \u002F rebuild — otherwise it crashes at first call |\n| camera\u002Fmic permission not declared | add them (`calls`), then rebuild |\n| testing on a simulator | simulators capture no camera or mic — use real devices |\n\n### Notifications never arrive\nRegistered before `login()` resolved · wrong platform constant · token rotated and never re-registered\n· missing `google-services.json` \u002F `GoogleService-Info.plist` · iOS simulator. See `push`.\n\n### A feature was \"enabled\" but nothing changed\n| Cause | Fix |\n|---|---|\n| dashboard toggled, code prop not set | AI features need **both**; the props default to off |\n| it is already core in v5 | reactions and mentions are on by default — nothing to enable |\n| the kit auto-renders it | `auto_rendered_ui` features need no client code |\n\n### A symbol does not compile\nCheck `catalogs\u002Frn-v5.json`. Likely a React name: `UIKitSettingsBuilder`, `login(uid)`,\n`onItemClick`, `CometChatErrorBoundary`, `CometChatDetails`, `CometChatMessagePlugin`. See the\nReact→RN table in `core\u002Freferences\u002Fdocs-map.md`.\n\n## First moves, in order\n1. Does `init` resolve, and does `login` resolve after it? Log both.\n2. Is `GestureHandlerRootView` outermost with `flex: 1`?\n3. Is every ancestor of the kit component `flex: 1`?\n4. Did you **rebuild** after the last native change, rather than reload?\n5. Does every emitted symbol exist in the catalog?\n\n## Verify it works\n- The symptom is reproducibly gone on a device, not only in a simulator.\n- `npm run verify:fences:rn-v5` is green.\n- If the fix was a native change, a **clean** build still works.\n\n## `tsc --noEmit` reports errors inside the UI Kit, not your app\n\nThe kit's `package.json` has `main: \"src\u002Findex\"` and ships **uncompiled `.tsx`** — there is no `lib\u002F` and\nno `types` field. So `tsc` follows the import into the kit's own source and reports ~30 errors under\n`node_modules\u002F@cometchat\u002Fchat-uikit-react-native\u002Fsrc\u002F*.tsx` while your own code is clean.\n\n`skipLibCheck` does **not** help (it only skips `.d.ts`, and there are none here), and\n`exclude: [\"node_modules\"]` does not either (TypeScript still follows imports). Metro strips types, so the\nbundle and the app are fine — this only bites a CI typecheck. Scope the check to your own sources:\n\n```bash\ntsc --noEmit -p tsconfig.json 2>&1 | grep -v 'node_modules\u002F@cometchat\u002F'\n```\n","> **Ground truth:** `@cometchat\u002Fchat-uikit-react-native@5` + catalog `rn-v5.json`.\n> Docs: `\u002Fui-kit\u002Freact-native\u002Ftroubleshooting`.\n\n## Companion skills (read first)\n- `cometchat-react-native-core` — install, provider chain, init→login→render. Assumed, not repeated here.\n\n## Use this skill when\n- anything is broken and the error does not say why — which on React Native is most of the time\n\n## Prerequisites & install\nNone.\n\n## Read this first: RN failures usually name the wrong thing\nThree properties make React Native bugs hard to read, and all three appear below:\n- **native modules fail at MOUNT, not at build** — so the app starts, then a screen explodes\n- **the error names a peer dependency**, not CometChat — `gesture-handler`, `svg`, `video`\n- **an unknown prop is silently ignored** — no error, nothing renders\n\nSo \"it says nothing about CometChat\" is not evidence the problem is elsewhere.\n\n## Symptom → root cause → fix\n\n### Blank chat screen, no error\n| Cause | Fix |\n|---|---|\n| rendering before `login()` resolved | gate render on a `loggedIn` flag; `init` → `login` → render |\n| `initFromSettings()` failed | you **cannot** catch it — `CometChatUIKit.initFromSettings()` swallows init errors (its rejection handler is a no-op), so `await`\u002F`.catch()` see nothing. Instead assert on the NEXT step: `await login(...)` (which DOES reject) or check `await CometChatUIKit.getLoggedInUser()`; a bad appId\u002Fregion surfaces there as an auth failure |\n| an ancestor is not `flex: 1` | every ancestor `flex: 1`; a scrolling column also needs `minHeight: 0` |\n\n### The UI renders but nothing responds to touch\n**`GestureHandlerRootView` is missing, or is not outermost, or lacks `flex: 1`.**\nNo error is thrown. On bare RN also confirm `import 'react-native-gesture-handler'` is the **first\nline of `index.js`** — wrong ordering there often works in debug and crashes in release.\n\n### `NativeModule ... null` \u002F \"cannot read property of null\" on a chat screen\nA native peer is missing or unlinked. Install the full peer list (`core`), then `pod install` (bare)\nor a fresh development build (Expo). **Metro reload does not pick up native changes — rebuild.**\n\n### Android build fails, error never mentions CometChat\n`@react-native-async-storage\u002Fasync-storage` must be `^2.1.2` — the Chat SDK requires it at load and the Calls SDK peer-requires 2.x. Unpinned resolves to 3.x, which fails `npm install @cometchat\u002Fcalls-sdk-react-native@5` with ERESOLVE. Check: `npm ls @react-native-async-storage\u002Fasync-storage`.\n\n### Expo: works in Expo Go until a chat screen opens\nExpo Go **cannot** load custom native modules. Use a development build (`npx expo run:ios`). There is\nno workaround.\n\n### My custom view does not appear\n**Slot props are PascalCase on RN** — `ItemView`, not `itemView`. React's casing is silently ignored:\nno error, nothing renders. Same class of bug as a typo'd prop name.\n\n### Two headers stacked on the message screen\nThe navigator's header plus `CometChatMessageHeader`. Set `headerShown: false` on that screen.\n\n### The composer is hidden when the keyboard opens\nA fixed height somewhere in the ancestor chain, or the message screen is nested **inside** the tab\nnavigator so the tab bar overlaps it. Put the message screen on the stack **above** the tabs.\n\n### Sending a message throws on iOS (React Native >= 0.87)\nReact Native **0.87 removed `InteractionManager` from core**, and `CometChatMessageComposer` (kit\nthrough 5.5.0) still calls `InteractionManager.runAfterInteractions()` in four **iOS-only** branches\nof its send path. Tapping send throws and the message never leaves the device. Android is unaffected;\nso is RN \u003C= 0.86, where the export is deprecated but still resolves — which is why the same code\nsends fine on an older app and dies on a fresh template.\n\n| Where | What you see |\n|---|---|\n| dev build | `Uncaught Error: InteractionManager has been removed from react-native core. Please refactor long tasks into smaller ones, and use 'requestIdleCallback' instead.` in `CometChatMessageComposer` -> `sendTextMessage` |\n| release build | the same line reads `undefined` -> `TypeError: Cannot read property 'runAfterInteractions' of undefined` |\n| CI | **nothing** — it typechecks, bundles and builds on both platforms; only a person tapping send sees it |\n\nUntil the kit drops the call, restore a minimal implementation **before the kit loads** — the first\nimport in `index.js`:\n\n```js\n\u002F\u002F interactionManagerCompat.js — delete when the kit stops calling InteractionManager.\nconst ReactNative = require('react-native');\n\nconst missing = () => {\n  try {\n    return !ReactNative.InteractionManager;\n  } catch {\n    return true; \u002F\u002F RN >= 0.87 in __DEV__: the getter throws.\n  }\n};\n\nif (missing()) {\n  Object.defineProperty(ReactNative, 'InteractionManager', {\n    configurable: true,\n    get: () => ({\n      runAfterInteractions: (task) => {\n        const run = () => (typeof task === 'function' ? task() : task && task.gen && task.gen());\n        let settle;\n        const ran = new Promise((resolve) => { settle = resolve; });\n        const timer = setTimeout(() => { run(); settle(); }, 0);   \u002F\u002F resolve AFTER the task runs\n        return {\n          then: (onResolve, onReject) => ran.then(onResolve, onReject),\n          done: (onDone) => { ran.then(onDone); },\n          cancel: () => clearTimeout(timer),\n        };\n      },\n      createInteractionHandle: () => 0,\n      clearInteractionHandle: () => {},\n      setDeadline: () => {},\n      addListener: () => ({ remove: () => {} }),\n    }),\n  });\n}\n```\n\n### `ReferenceError: Property '\u003Cname>' doesn't exist` right after a `try`\u002F`catch`\nHermes loses a `catch (error)` binding that is only read inside a closure created in the same block —\n`catch (error) { setLogs((prev) => [describe(error), ...prev]) }` throws the first time the catch\nruns, while the identical code with the value read first works. It typechecks and bundles either way.\nRead the caught value into a local, then use the local inside the closure.\n\n### Calls do not ring\n| Cause | Fix |\n|---|---|\n| `CometChatIncomingCall` mounted inside one screen | mount it **once above the navigator** |\n| calls SDK installed but pods not run | `pod install` \u002F rebuild — otherwise it crashes at first call |\n| camera\u002Fmic permission not declared | add them (`calls`), then rebuild |\n| testing on a simulator | simulators capture no camera or mic — use real devices |\n\n### Notifications never arrive\nRegistered before `login()` resolved · wrong platform constant · token rotated and never re-registered\n· missing `google-services.json` \u002F `GoogleService-Info.plist` · iOS simulator. See `push`.\n\n### A feature was \"enabled\" but nothing changed\n| Cause | Fix |\n|---|---|\n| dashboard toggled, code prop not set | AI features need **both**; the props default to off |\n| it is already core in v5 | reactions and mentions are on by default — nothing to enable |\n| the kit auto-renders it | `auto_rendered_ui` features need no client code |\n\n### A symbol does not compile\nCheck `catalogs\u002Frn-v5.json`. Likely a React name: `UIKitSettingsBuilder`, `login(uid)`,\n`onItemClick`, `CometChatErrorBoundary`, `CometChatDetails`, `CometChatMessagePlugin`. See the\nReact→RN table in `core\u002Freferences\u002Fdocs-map.md`.\n\n## First moves, in order\n1. Does `init` resolve, and does `login` resolve after it? Log both.\n2. Is `GestureHandlerRootView` outermost with `flex: 1`?\n3. Is every ancestor of the kit component `flex: 1`?\n4. Did you **rebuild** after the last native change, rather than reload?\n5. Does every emitted symbol exist in the catalog?\n\n## Verify it works\n- The symptom is reproducibly gone on a device, not only in a simulator.\n- `npm run verify:fences:rn-v5` is green.\n- If the fix was a native change, a **clean** build still works.\n\n## `tsc --noEmit` reports errors inside the UI Kit, not your app\n\nThe kit's `package.json` has `main: \"src\u002Findex\"` and ships **uncompiled `.tsx`** — there is no `lib\u002F` and\nno `types` field. So `tsc` follows the import into the kit's own source and reports ~30 errors under\n`node_modules\u002F@cometchat\u002Fchat-uikit-react-native\u002Fsrc\u002F*.tsx` while your own code is clean.\n\n`skipLibCheck` does **not** help (it only skips `.d.ts`, and there are none here), and\n`exclude: [\"node_modules\"]` does not either (TypeScript still follows imports). Metro strips types, so the\nbundle and the app are fine — this only bites a CI typecheck. Scope the check to your own sources:\n\n```bash\ntsc --noEmit -p tsconfig.json 2>&1 | grep -v 'node_modules\u002F@cometchat\u002F'\n```\n",{"name":5,"license":15,"metadata":50,"description":7,"compatibility":54},{"tags":51,"author":52,"version":53},"chat cometchat react-native troubleshooting diagnostics errors debugging","CometChat","1.0.0","React Native >=0.77; @cometchat\u002Fchat-uikit-react-native ^5.4.0","main","cebc3dce495d7eb80d3b1d5841f877a4a92e162d","plugins\u002Fcometchat\u002Fcometchat-skills\u002Fskills\u002Fcometchat-react-native-troubleshooting",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":66,"prompt":76,"zipAvailable":77},[67,70,73],{"tool":68,"command":69},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill cometchat-react-native-troubleshooting",{"tool":71,"command":72},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill cometchat-react-native-troubleshooting",{"tool":74,"command":75},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill cometchat-react-native-troubleshooting","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fcometchat\u002Fcometchat-skills\u002Fskills\u002Fcometchat-react-native-troubleshooting\u002FSKILL.md",true,[],[80,89,97,105,113,121],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":84,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":88},"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":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":93,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":88},"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":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":101,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":88},"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":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":109,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":88},"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":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":117,"sourceHtmlUrl":118,"categories":119,"keywords":120,"publishedAt":88},"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":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":125,"sourceHtmlUrl":126,"categories":127,"keywords":128,"publishedAt":88},"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",[],[]]