[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MF7CG7PJSXYBHK0KBRFJ9C":3,"skill-same:01M6MF7CG7PJSXYBHK0KBRFJ9C":82},{"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":42,"linkOnly":43,"markdownContent":44,"markdownBody":45,"frontMatter":46,"refName":52,"commitSha":53,"skillDirectory":54,"forksCount":55,"repositoryHtmlUrl":56,"repositoryHomepageUrl":57,"ownerHtmlUrl":58,"ownerBlogUrl":59,"ownerDescription":60,"updatedAt":61,"install":62,"resources":75},"01M6MF7CG7PJSXYBHK0KBRFJ9C","cometchat-angular-v5-migration",null,"Upgrade an Angular app from CometChat UI Kit v4 → v5 (`@cometchat\u002Fchat-uikit-angular` ^4 → ^5). Reads the repo's CometChat usage, applies the breaking-change map (deps, composite components removed, bare→Component renames, CometChatThemeService → CSS variables, event inputs → Outputs, DataSource → composition, localization renames), fetches the exhaustive guide, and verifies the build. Triggers: 'upgrade my v4 uikit to v5', 'migrate cometchat angular v4 to v5', 'upgrade @cometchat\u002Fchat-uikit-angular to v5', 'cometchat angular v4 to v5', 'bump cometchat angular uikit'.","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-angular-v5-migration\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41],"cometchat angular v5 migration","migration","angular","cometchat","new","bare","component","change","components","migrate","Variables","upgrade","map","kit","bump","css variables","css","official","resources","Composition","deps","app","shared","2026-11-10 10:12:30",false,"---\nname: cometchat-angular-v5-migration\ndescription: \"Upgrade an Angular app from CometChat UI Kit v4 → v5 (`@cometchat\u002Fchat-uikit-angular` ^4 → ^5). Reads the repo's CometChat usage, applies the breaking-change map (deps, composite components removed, bare→Component renames, CometChatThemeService → CSS variables, event inputs → Outputs, DataSource → composition, localization renames), fetches the exhaustive guide, and verifies the build. Triggers: 'upgrade my v4 uikit to v5', 'migrate cometchat angular v4 to v5', 'upgrade @cometchat\u002Fchat-uikit-angular to v5', 'cometchat angular v4 to v5', 'bump cometchat angular uikit'.\"\nlicense: \"MIT\"\ncompatibility: \"Angular 17-21; FROM @cometchat\u002Fchat-uikit-angular ^4 (4.3.36) → ^5 (5.1.0–5.2.2 verified); @cometchat\u002Fchat-sdk-javascript ^4.1.13 (peer; 5.2.x needs ^4.2.0); @cometchat\u002Fcards-angular ^1.0.0 (new peer, undocumented in the official guide); @cometchat\u002Fuikit-elements\u002F-resources\u002F-shared removed\"\nmetadata:\n  author: \"CometChat\"\n  version: \"1.0.0\"\n  tags: \"cometchat angular migration upgrade v4 v5 uikit\"\n---\n\n> **Ground truth:** migrates an Angular app **FROM `@cometchat\u002Fchat-uikit-angular@4` TO `@5`**. v5 target symbols are catalog-verified vs installed 5.1.0; the v4→v5 breaking-change map is BAKED in `references\u002Fmigration-guide.md` (distilled from the official \"Upgrading From V4\" guide + a real v4.3.36→v5.1.0 export diff — 146 genuine removals, 33 bare→`Component` renames, kept separate). The exhaustive per-component prop table is FETCHED from `cometchat-angular-v5-components\u002Freferences\u002Fcatalog.md` + the docs `.md` twins. **APPEND\u002Ftransform the user's code — never wipe it; work on a branch and confirm before bulk edits** (`RULES.md`).\n\n## Companion skills (read first)\n- `cometchat-angular-v5-core` — the v5 init\u002Flogin\u002Frender the migrated app lands on. This skill ASSUMES it.\n- `cometchat-angular-v5-components` — the v5 component catalog (the target names + real inputs\u002Foutputs).\n- `cometchat-angular-v5-placement` — how to rebuild a v4 composite from v5 modules (§2 of the migration guide points here per composite).\n\n## Use this skill when\n\"upgrade my v4 UI Kit to v5\", \"migrate CometChat Angular v4→v5\", \"bump `@cometchat\u002Fchat-uikit-angular` to v5\". Precondition: the project currently has `@cometchat\u002Fchat-uikit-angular@4`.\n\n## Migration workflow (BAKED)\n1. **Detect the starting point.** Confirm `package.json` has `@cometchat\u002Fchat-uikit-angular@4` (already `@5` → STOP, nothing to migrate). Note whether the app uses composite components (`...WithMessages`\u002F`...WithDetails`), `CometChatThemeService`, `*Style` inputs, `DataSource`\u002F`ChatConfigurator`, or custom localization keys — each drives a later step. **Work on a branch; transform in place, never delete the user's code.**\n2. **Update dependencies.** `npm install @cometchat\u002Fchat-uikit-angular@5 @cometchat\u002Fchat-sdk-javascript@^4.1.13 @cometchat\u002Fcards-angular@^1.0.0` then `npm uninstall @cometchat\u002Fuikit-elements @cometchat\u002Fuikit-resources @cometchat\u002Fuikit-shared`. `@cometchat\u002Fcards-angular` is a genuine new 5.1.0 peer the official guide never mentions — install it or the build fails on a missing peer, not a CometChat error.\n3. **Scan the repo for v4 usage.** Grep for every symbol in `references\u002Fmigration-guide.md` §2 (composites, no-equivalent standalones, `DataSource`\u002Fdecorators, the ~35 `*Style` objects) and §2b (the 33 bare-name renames) — produce the concrete change list before editing anything. A bare name is not automatically \"removed\"; check §2b first.\n4. **Apply the breaking-change map** (`references\u002Fmigration-guide.md`): §2\u002F§2b symbol removals + renames, §3 theming (`CometChatThemeService` + `*Style` → CSS variables + the real `ThemeService`, **not** the official guide's own hand-rolled `matchMedia` example — see the warning in §3), §4 event-input → Output rename, §5 `DataSource`\u002F`ChatConfigurator` → `MessageBubbleConfigService` or \"nothing, it's auto-rendered,\" §6 drop `CUSTOM_ELEMENTS_SCHEMA` + convert to standalone, §7 optional `ChatStateService` adoption, §8 localization method renames.\n   **The baked map is a closed list, not a prop reference — FETCH the rest** (`RULES.md` § Fetch discipline; **never** `node_modules\u002F**\u002F*.d.ts`), routed from `cometchat-angular-v5-core\u002Freferences\u002Fdocs-map.md`: the **official guide** `{DOCS_BASE}\u002Fui-kit\u002Fangular\u002Fcustomization\u002Fmigration-guide.md` for anything the map omits; a **component's** exact inputs\u002Foutputs\u002Fslots from its own `.md` twin (Angular has no `migration-property-changes` page — there is no single prop-diff table); an **SDK method** for a capability with no v5 component (`{SDK_DOCS_BASE}\u002Fsdk\u002Fjavascript\u002Fgroups-overview.md` et al.) — that is where the host-composed group surfaces in step 5 come from.\n5. **Rebuild every composite from modules.** v5 has no composite components at all — `CometChatConversationsWithMessages` etc. must become a hand-stitched surface. Use `cometchat-angular-v5-placement\u002Freferences\u002Fcore-surface.md` (1:1) or `combined-app.md` (tabbed) as the target shape, not a literal prop-for-prop port — the composite's *configuration options* (which v4 had many of) don't exist in v5; its *behavior* is what you're reproducing.\n6. **Verify.** Build\u002Ftypecheck passes; NO v4 symbols remain (grep `references\u002Fmigration-guide.md` §2's full list); every kit component is in its consumer's `imports: []`; the app renders after init→login resolves (`cometchat-angular-v5-core\u002Freferences\u002Flifecycle.md`). Reuse `cometchat-angular-v5-core` \"Verify it works\".\n\n## Common pitfalls (BAKED)\n- **Porting the official guide's own theming example.** It shows a hand-rolled `matchMedia` listener for OS-follow — that predates the real v5 mechanism. `ThemeService.initFromPreference()` already does this; don't reintroduce v4-era manual theme-tracking code (§3).\n- **Treating a bare v4 name as removed when it's only renamed.** Check §2b (33 bare→`Component` renames) before concluding a component is gone — most \"missing\" names are one word away from their v5 form.\n- **Missing `@cometchat\u002Fcards-angular`.** Genuinely undocumented in the official migration guide; the install fails on a peer-dependency error that looks unrelated to the migration.\n- **Forgetting `imports: []` after dropping `CUSTOM_ELEMENTS_SCHEMA`.** v4's schema tolerated unregistered elements; v5's standalone components render **nothing, silently** if omitted from `imports: []` — the single most common v5 failure mode, and migrated code is exactly where it's missed (`cometchat-angular-v5-core\u002FSKILL.md`).\n- **Rebuilding a composite as a literal prop-for-prop port.** v4 composites had large configuration surfaces (`*Style` objects, callback inputs) with no v5 equivalent — port the *behavior*, not the *configuration*, using `cometchat-angular-v5-placement`'s real recipes as the target.\n- **Assuming every `DataSourceDecorator` needs `MessageBubbleConfigService`.** Some were registering a *built-in extension* (polls, stickers, translation) — v5 auto-renders most of those once enabled in the dashboard, with nothing to register (`cometchat-angular-v5-features\u002FSKILL.md`; verify against `needs_stitching` in `features.angular-v5.json`, never assume).\n\n## Verify it works\nBuild\u002Ftypecheck is green; a repo-wide grep finds NO §2 v4 symbols (composites, `CometChatThemeService`, `DataSource`\u002F`ChatConfigurator`, any `*Style` object, any bare §2b name unqualified); every kit component is in `imports: []`; the app renders once init→login resolves; migrated theming follows the OS via `ThemeService`, not a leftover `matchMedia` listener. Full per-component prop reference: `cometchat-angular-v5-components\u002Freferences\u002Fcatalog.md` + the docs `.md` twins.\n","> **Ground truth:** migrates an Angular app **FROM `@cometchat\u002Fchat-uikit-angular@4` TO `@5`**. v5 target symbols are catalog-verified vs installed 5.1.0; the v4→v5 breaking-change map is BAKED in `references\u002Fmigration-guide.md` (distilled from the official \"Upgrading From V4\" guide + a real v4.3.36→v5.1.0 export diff — 146 genuine removals, 33 bare→`Component` renames, kept separate). The exhaustive per-component prop table is FETCHED from `cometchat-angular-v5-components\u002Freferences\u002Fcatalog.md` + the docs `.md` twins. **APPEND\u002Ftransform the user's code — never wipe it; work on a branch and confirm before bulk edits** (`RULES.md`).\n\n## Companion skills (read first)\n- `cometchat-angular-v5-core` — the v5 init\u002Flogin\u002Frender the migrated app lands on. This skill ASSUMES it.\n- `cometchat-angular-v5-components` — the v5 component catalog (the target names + real inputs\u002Foutputs).\n- `cometchat-angular-v5-placement` — how to rebuild a v4 composite from v5 modules (§2 of the migration guide points here per composite).\n\n## Use this skill when\n\"upgrade my v4 UI Kit to v5\", \"migrate CometChat Angular v4→v5\", \"bump `@cometchat\u002Fchat-uikit-angular` to v5\". Precondition: the project currently has `@cometchat\u002Fchat-uikit-angular@4`.\n\n## Migration workflow (BAKED)\n1. **Detect the starting point.** Confirm `package.json` has `@cometchat\u002Fchat-uikit-angular@4` (already `@5` → STOP, nothing to migrate). Note whether the app uses composite components (`...WithMessages`\u002F`...WithDetails`), `CometChatThemeService`, `*Style` inputs, `DataSource`\u002F`ChatConfigurator`, or custom localization keys — each drives a later step. **Work on a branch; transform in place, never delete the user's code.**\n2. **Update dependencies.** `npm install @cometchat\u002Fchat-uikit-angular@5 @cometchat\u002Fchat-sdk-javascript@^4.1.13 @cometchat\u002Fcards-angular@^1.0.0` then `npm uninstall @cometchat\u002Fuikit-elements @cometchat\u002Fuikit-resources @cometchat\u002Fuikit-shared`. `@cometchat\u002Fcards-angular` is a genuine new 5.1.0 peer the official guide never mentions — install it or the build fails on a missing peer, not a CometChat error.\n3. **Scan the repo for v4 usage.** Grep for every symbol in `references\u002Fmigration-guide.md` §2 (composites, no-equivalent standalones, `DataSource`\u002Fdecorators, the ~35 `*Style` objects) and §2b (the 33 bare-name renames) — produce the concrete change list before editing anything. A bare name is not automatically \"removed\"; check §2b first.\n4. **Apply the breaking-change map** (`references\u002Fmigration-guide.md`): §2\u002F§2b symbol removals + renames, §3 theming (`CometChatThemeService` + `*Style` → CSS variables + the real `ThemeService`, **not** the official guide's own hand-rolled `matchMedia` example — see the warning in §3), §4 event-input → Output rename, §5 `DataSource`\u002F`ChatConfigurator` → `MessageBubbleConfigService` or \"nothing, it's auto-rendered,\" §6 drop `CUSTOM_ELEMENTS_SCHEMA` + convert to standalone, §7 optional `ChatStateService` adoption, §8 localization method renames.\n   **The baked map is a closed list, not a prop reference — FETCH the rest** (`RULES.md` § Fetch discipline; **never** `node_modules\u002F**\u002F*.d.ts`), routed from `cometchat-angular-v5-core\u002Freferences\u002Fdocs-map.md`: the **official guide** `{DOCS_BASE}\u002Fui-kit\u002Fangular\u002Fcustomization\u002Fmigration-guide.md` for anything the map omits; a **component's** exact inputs\u002Foutputs\u002Fslots from its own `.md` twin (Angular has no `migration-property-changes` page — there is no single prop-diff table); an **SDK method** for a capability with no v5 component (`{SDK_DOCS_BASE}\u002Fsdk\u002Fjavascript\u002Fgroups-overview.md` et al.) — that is where the host-composed group surfaces in step 5 come from.\n5. **Rebuild every composite from modules.** v5 has no composite components at all — `CometChatConversationsWithMessages` etc. must become a hand-stitched surface. Use `cometchat-angular-v5-placement\u002Freferences\u002Fcore-surface.md` (1:1) or `combined-app.md` (tabbed) as the target shape, not a literal prop-for-prop port — the composite's *configuration options* (which v4 had many of) don't exist in v5; its *behavior* is what you're reproducing.\n6. **Verify.** Build\u002Ftypecheck passes; NO v4 symbols remain (grep `references\u002Fmigration-guide.md` §2's full list); every kit component is in its consumer's `imports: []`; the app renders after init→login resolves (`cometchat-angular-v5-core\u002Freferences\u002Flifecycle.md`). Reuse `cometchat-angular-v5-core` \"Verify it works\".\n\n## Common pitfalls (BAKED)\n- **Porting the official guide's own theming example.** It shows a hand-rolled `matchMedia` listener for OS-follow — that predates the real v5 mechanism. `ThemeService.initFromPreference()` already does this; don't reintroduce v4-era manual theme-tracking code (§3).\n- **Treating a bare v4 name as removed when it's only renamed.** Check §2b (33 bare→`Component` renames) before concluding a component is gone — most \"missing\" names are one word away from their v5 form.\n- **Missing `@cometchat\u002Fcards-angular`.** Genuinely undocumented in the official migration guide; the install fails on a peer-dependency error that looks unrelated to the migration.\n- **Forgetting `imports: []` after dropping `CUSTOM_ELEMENTS_SCHEMA`.** v4's schema tolerated unregistered elements; v5's standalone components render **nothing, silently** if omitted from `imports: []` — the single most common v5 failure mode, and migrated code is exactly where it's missed (`cometchat-angular-v5-core\u002FSKILL.md`).\n- **Rebuilding a composite as a literal prop-for-prop port.** v4 composites had large configuration surfaces (`*Style` objects, callback inputs) with no v5 equivalent — port the *behavior*, not the *configuration*, using `cometchat-angular-v5-placement`'s real recipes as the target.\n- **Assuming every `DataSourceDecorator` needs `MessageBubbleConfigService`.** Some were registering a *built-in extension* (polls, stickers, translation) — v5 auto-renders most of those once enabled in the dashboard, with nothing to register (`cometchat-angular-v5-features\u002FSKILL.md`; verify against `needs_stitching` in `features.angular-v5.json`, never assume).\n\n## Verify it works\nBuild\u002Ftypecheck is green; a repo-wide grep finds NO §2 v4 symbols (composites, `CometChatThemeService`, `DataSource`\u002F`ChatConfigurator`, any `*Style` object, any bare §2b name unqualified); every kit component is in `imports: []`; the app renders once init→login resolves; migrated theming follows the OS via `ThemeService`, not a leftover `matchMedia` listener. Full per-component prop reference: `cometchat-angular-v5-components\u002Freferences\u002Fcatalog.md` + the docs `.md` twins.\n",{"name":5,"license":15,"metadata":47,"description":7,"compatibility":51},{"tags":48,"author":49,"version":50},"cometchat angular migration upgrade v4 v5 uikit","CometChat","1.0.0","Angular 17-21; FROM @cometchat\u002Fchat-uikit-angular ^4 (4.3.36) → ^5 (5.1.0–5.2.2 verified); @cometchat\u002Fchat-sdk-javascript ^4.1.13 (peer; 5.2.x needs ^4.2.0); @cometchat\u002Fcards-angular ^1.0.0 (new peer, undocumented in the official guide); @cometchat\u002Fuikit-elements\u002F-resources\u002F-shared removed","main","cebc3dce495d7eb80d3b1d5841f877a4a92e162d","plugins\u002Fcometchat\u002Fcometchat-skills\u002Fskills\u002Fcometchat-angular-v5-migration",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":63,"prompt":73,"zipAvailable":74},[64,67,70],{"tool":65,"command":66},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill cometchat-angular-v5-migration",{"tool":68,"command":69},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill cometchat-angular-v5-migration",{"tool":71,"command":72},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill cometchat-angular-v5-migration","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fcometchat\u002Fcometchat-skills\u002Fskills\u002Fcometchat-angular-v5-migration\u002FSKILL.md",true,[76],{"path":77,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":80,"sourceHtmlUrl":81},"references\u002Fmigration-guide.md","REFERENCE","参考文档",19890,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fcometchat\u002Fcometchat-skills\u002Fskills\u002Fcometchat-angular-v5-migration\u002Freferences\u002Fmigration-guide.md",[83,92,100,108,116,124],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":87,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":91},"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":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":91},"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":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":91},"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":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":91},"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":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":91},"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":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":128,"sourceHtmlUrl":129,"categories":130,"keywords":131,"publishedAt":91},"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",[],[]]