[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MF7YKJG6BCVD6SSTS3RCPF":3,"skill-same:01M6MF7YKJG6BCVD6SSTS3RCPF":75},{"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":41,"linkOnly":42,"markdownContent":43,"markdownBody":44,"frontMatter":45,"refName":51,"commitSha":52,"skillDirectory":53,"forksCount":54,"repositoryHtmlUrl":55,"repositoryHomepageUrl":56,"ownerHtmlUrl":57,"ownerBlogUrl":58,"ownerDescription":59,"updatedAt":60,"install":61,"resources":74},"01M6MF7YKJG6BCVD6SSTS3RCPF","cometchat-angular-v5-production",null,"Ship a CometChat Angular integration safely — server-minted auth tokens instead of the Auth Key, environment file replacement, key hygiene, build config and a pre-launch checklist. Triggers: 'is this production ready', 'auth token instead of auth key angular', 'secure my cometchat setup', 'production build config', 'going live checklist'.","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-production\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40],"cometchat angular v5 production","Production","angular","cometchat","auth tokens","triggers","production ready","tokens","environment","deployment","pre-launch","ship","security","live","my","verified","token","config","secure","server","auth","ready","2026-11-10 10:12:30",false,"---\nname: cometchat-angular-v5-production\ndescription: \"Ship a CometChat Angular integration safely — server-minted auth tokens instead of the Auth Key, environment file replacement, key hygiene, build config and a pre-launch checklist. Triggers: 'is this production ready', 'auth token instead of auth key angular', 'secure my cometchat setup', 'production build config', 'going live checklist'.\"\nlicense: \"MIT\"\ncompatibility: \"@cometchat\u002Fchat-uikit-angular ^5 (5.1.0–5.2.2 verified); Angular 17-21\"\nmetadata:\n  author: \"CometChat\"\n  version: \"1.0.0\"\n  tags: \"cometchat angular production v5 security auth-token hardening deployment\"\n---\n\n> **Ground truth:** `@cometchat\u002Fchat-uikit-angular@5` (5.1.0–5.2.2 verified). The auth-token API is FETCHED from `{DOCS_BASE}\u002Fui-kit\u002Fangular\u002Fmethods.md` and `\u002Fintegration.md` (base + paths in `cometchat-angular-v5-core\u002Freferences\u002Fdocs-map.md`). **The Angular UI Kit docs have no dedicated production-hardening page** — the checklist below is the pack's own guidance, derived from the credential rules in `RULES.md` §4 and what the kit ships; it is labelled as such rather than presented as documented. Treat that as a tracked DOCS GAP.\n\n## Companion skills (read first)\n- `cometchat-angular-v5-core` — `references\u002Fsetup-credentials.md` covers the dev credential flow this replaces.\n- `cometchat-security` — the enterprise auth model this client-side hardening plugs into: wiring your IdP \u002F SSO into the token flow (your IdP → your server → mint the CometChat auth token; CometChat is **not** an IdP), token expiry\u002Frefresh + re-login, RBAC roles + group (SBAC) scopes, and Auth Key vs auth token vs REST API Key. Load it for a security review or any SSO question.\n\n## Use this skill when\nMoving off the development setup: going live, a security review, or \"is this safe to ship\".\n\n## The one thing that matters\n**Never ship the Auth Key in the browser bundle.**\n\nThe Auth Key can mint a session for **any user in your app**. Anything in `environment.ts` is compiled into JavaScript your users download, so an Auth Key there is public. Anyone can read it, log in as any UID, and read every conversation.\n\n| | Development | Production |\n| --- | --- | --- |\n| Login | `CometChatUIKit.login(uid)` | `CometChatUIKit.loginWithAuthToken(token)` |\n| Auth Key | in `environment.ts` | **absent from the bundle** |\n| Token source | n\u002Fa | your backend, per authenticated user |\n| REST API Key | never client-side | server only |\n\n## The production login flow\n1. Your app authenticates the user (your own auth — CometChat is not an identity provider).\n2. Your **server** calls CometChat's REST API with the **REST API Key** to mint an auth token for that user's UID.\n3. The server returns the token to the browser over an authenticated request.\n4. The app calls `loginWithAuthToken(token)`.\n\n```ts\nimport { inject } from '@angular\u002Fcore';\nimport { HttpClient } from '@angular\u002Fcommon\u002Fhttp';\nimport { firstValueFrom } from 'rxjs';\nimport { CometChatUIKit } from '@cometchat\u002Fchat-uikit-angular';\n\nconst http = inject(HttpClient);\n\nasync function loginForCurrentUser() {\n  \u002F\u002F your endpoint, protected by your own session\n  const { authToken } = await firstValueFrom(\n    http.get\u003C{ authToken: string }>('\u002Fapi\u002Fcometchat-token', { withCredentials: true }),\n  );\n  return CometChatUIKit.loginWithAuthToken(authToken);\n}\n```\n\nThe endpoint must derive the UID from the **server-side session**, never from a request parameter. Accepting `?uid=` lets any caller impersonate anyone.\n\n## Environment files\n```ts\n\u002F\u002F src\u002Fenvironments\u002Fenvironment.prod.ts\nexport const environment = {\n  production: true,\n  cometchat: { appId: 'APP_ID', region: 'REGION', authKey: '' },   \u002F\u002F empty on purpose\n};\n```\nApp ID and Region are not secrets — they identify the app. The Auth Key is the secret, and it is empty here. Confirm `fileReplacements` is wired in the production configuration, then **grep the built bundle** for the key to be certain:\n```bash\nng build --configuration production && grep -r \"YOUR_AUTH_KEY\" dist\u002F || echo \"clean\"\n```\nRun that in CI. A misconfigured `fileReplacements` fails silently and ships the dev file.\n\n## Also before launch\n- **Users are created server-side**, as part of your signup — not from the browser.\n- **Log out properly**: `await CometChatUIKit.logout()`, then clear derived state and unregister push tokens (`cometchat-angular-v5-push`).\n- **HTTPS everywhere** — required for calls (`getUserMedia`) and push.\n- **Pin the kit** to an exact or `~` range so a minor cannot change component behaviour under you.\n- **Set a log level**: `CometChatUIKit.setLogLevel(...)` — quieter in production.\n- **Handle errors visibly**: every list EXCEPT `\u003Ccometchat-call-logs>` has an `(error)` output — verified vs 5.1.0, its only outputs are `itemClick` and `callButtonClicked`; it takes an `onError` INPUT callback instead, so `(error)` there binds a DOM listener that never fires. Conversations \u002F Users \u002F Groups \u002F GroupMembers \u002F MessageList all do have `(error)`; wrap the surface in `\u003Ccometchat-error-boundary>`.\n- **Teardown** — `ngOnDestroy` on every subscription and listener; leaks are worse in a long-lived SPA.\n- **Region must match** the dashboard app, in every configuration you build.\n\n## Pre-launch checklist\n- [ ] Auth Key absent from the production bundle (grep-verified in CI)\n- [ ] `loginWithAuthToken` in production; UID from the server session\n- [ ] REST API Key server-side only\n- [ ] `fileReplacements` verified by building, not by reading config — note the production build FAILS on the default 1 MB budget until you raise it (`cometchat-angular-v5-core` Install); the grep below never runs otherwise\n- [ ] HTTPS, valid certificate\n- [ ] Logout clears session, state and push tokens\n- [ ] Kit version pinned\n- [ ] Error boundary + error outputs handled\n- [ ] Dashboard extensions\u002FAI enabled for the production app, not just dev\n- [ ] Tested against the production app's credentials\n\n## Common pitfalls\n1. **Auth Key in the production bundle** — the critical one.\n2. **Token endpoint trusting a client-supplied UID** — impersonation.\n3. **`fileReplacements` assumed rather than verified** — dev config ships.\n4. **Dashboard configured on the dev app only** — features silently missing in production.\n5. **No logout teardown** — the next user inherits the session or the push token.\n\n## Verify it works\nProduction build contains no Auth Key · login works via token · a tampered UID is rejected by the server · logout fully clears · calls and push work over HTTPS · features enabled on the production app.\n","> **Ground truth:** `@cometchat\u002Fchat-uikit-angular@5` (5.1.0–5.2.2 verified). The auth-token API is FETCHED from `{DOCS_BASE}\u002Fui-kit\u002Fangular\u002Fmethods.md` and `\u002Fintegration.md` (base + paths in `cometchat-angular-v5-core\u002Freferences\u002Fdocs-map.md`). **The Angular UI Kit docs have no dedicated production-hardening page** — the checklist below is the pack's own guidance, derived from the credential rules in `RULES.md` §4 and what the kit ships; it is labelled as such rather than presented as documented. Treat that as a tracked DOCS GAP.\n\n## Companion skills (read first)\n- `cometchat-angular-v5-core` — `references\u002Fsetup-credentials.md` covers the dev credential flow this replaces.\n- `cometchat-security` — the enterprise auth model this client-side hardening plugs into: wiring your IdP \u002F SSO into the token flow (your IdP → your server → mint the CometChat auth token; CometChat is **not** an IdP), token expiry\u002Frefresh + re-login, RBAC roles + group (SBAC) scopes, and Auth Key vs auth token vs REST API Key. Load it for a security review or any SSO question.\n\n## Use this skill when\nMoving off the development setup: going live, a security review, or \"is this safe to ship\".\n\n## The one thing that matters\n**Never ship the Auth Key in the browser bundle.**\n\nThe Auth Key can mint a session for **any user in your app**. Anything in `environment.ts` is compiled into JavaScript your users download, so an Auth Key there is public. Anyone can read it, log in as any UID, and read every conversation.\n\n| | Development | Production |\n| --- | --- | --- |\n| Login | `CometChatUIKit.login(uid)` | `CometChatUIKit.loginWithAuthToken(token)` |\n| Auth Key | in `environment.ts` | **absent from the bundle** |\n| Token source | n\u002Fa | your backend, per authenticated user |\n| REST API Key | never client-side | server only |\n\n## The production login flow\n1. Your app authenticates the user (your own auth — CometChat is not an identity provider).\n2. Your **server** calls CometChat's REST API with the **REST API Key** to mint an auth token for that user's UID.\n3. The server returns the token to the browser over an authenticated request.\n4. The app calls `loginWithAuthToken(token)`.\n\n```ts\nimport { inject } from '@angular\u002Fcore';\nimport { HttpClient } from '@angular\u002Fcommon\u002Fhttp';\nimport { firstValueFrom } from 'rxjs';\nimport { CometChatUIKit } from '@cometchat\u002Fchat-uikit-angular';\n\nconst http = inject(HttpClient);\n\nasync function loginForCurrentUser() {\n  \u002F\u002F your endpoint, protected by your own session\n  const { authToken } = await firstValueFrom(\n    http.get\u003C{ authToken: string }>('\u002Fapi\u002Fcometchat-token', { withCredentials: true }),\n  );\n  return CometChatUIKit.loginWithAuthToken(authToken);\n}\n```\n\nThe endpoint must derive the UID from the **server-side session**, never from a request parameter. Accepting `?uid=` lets any caller impersonate anyone.\n\n## Environment files\n```ts\n\u002F\u002F src\u002Fenvironments\u002Fenvironment.prod.ts\nexport const environment = {\n  production: true,\n  cometchat: { appId: 'APP_ID', region: 'REGION', authKey: '' },   \u002F\u002F empty on purpose\n};\n```\nApp ID and Region are not secrets — they identify the app. The Auth Key is the secret, and it is empty here. Confirm `fileReplacements` is wired in the production configuration, then **grep the built bundle** for the key to be certain:\n```bash\nng build --configuration production && grep -r \"YOUR_AUTH_KEY\" dist\u002F || echo \"clean\"\n```\nRun that in CI. A misconfigured `fileReplacements` fails silently and ships the dev file.\n\n## Also before launch\n- **Users are created server-side**, as part of your signup — not from the browser.\n- **Log out properly**: `await CometChatUIKit.logout()`, then clear derived state and unregister push tokens (`cometchat-angular-v5-push`).\n- **HTTPS everywhere** — required for calls (`getUserMedia`) and push.\n- **Pin the kit** to an exact or `~` range so a minor cannot change component behaviour under you.\n- **Set a log level**: `CometChatUIKit.setLogLevel(...)` — quieter in production.\n- **Handle errors visibly**: every list EXCEPT `\u003Ccometchat-call-logs>` has an `(error)` output — verified vs 5.1.0, its only outputs are `itemClick` and `callButtonClicked`; it takes an `onError` INPUT callback instead, so `(error)` there binds a DOM listener that never fires. Conversations \u002F Users \u002F Groups \u002F GroupMembers \u002F MessageList all do have `(error)`; wrap the surface in `\u003Ccometchat-error-boundary>`.\n- **Teardown** — `ngOnDestroy` on every subscription and listener; leaks are worse in a long-lived SPA.\n- **Region must match** the dashboard app, in every configuration you build.\n\n## Pre-launch checklist\n- [ ] Auth Key absent from the production bundle (grep-verified in CI)\n- [ ] `loginWithAuthToken` in production; UID from the server session\n- [ ] REST API Key server-side only\n- [ ] `fileReplacements` verified by building, not by reading config — note the production build FAILS on the default 1 MB budget until you raise it (`cometchat-angular-v5-core` Install); the grep below never runs otherwise\n- [ ] HTTPS, valid certificate\n- [ ] Logout clears session, state and push tokens\n- [ ] Kit version pinned\n- [ ] Error boundary + error outputs handled\n- [ ] Dashboard extensions\u002FAI enabled for the production app, not just dev\n- [ ] Tested against the production app's credentials\n\n## Common pitfalls\n1. **Auth Key in the production bundle** — the critical one.\n2. **Token endpoint trusting a client-supplied UID** — impersonation.\n3. **`fileReplacements` assumed rather than verified** — dev config ships.\n4. **Dashboard configured on the dev app only** — features silently missing in production.\n5. **No logout teardown** — the next user inherits the session or the push token.\n\n## Verify it works\nProduction build contains no Auth Key · login works via token · a tampered UID is rejected by the server · logout fully clears · calls and push work over HTTPS · features enabled on the production app.\n",{"name":5,"license":15,"metadata":46,"description":7,"compatibility":50},{"tags":47,"author":48,"version":49},"cometchat angular production v5 security auth-token hardening deployment","CometChat","1.0.0","@cometchat\u002Fchat-uikit-angular ^5 (5.1.0–5.2.2 verified); Angular 17-21","main","cebc3dce495d7eb80d3b1d5841f877a4a92e162d","plugins\u002Fcometchat\u002Fcometchat-skills\u002Fskills\u002Fcometchat-angular-v5-production",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":62,"prompt":72,"zipAvailable":73},[63,66,69],{"tool":64,"command":65},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill cometchat-angular-v5-production",{"tool":67,"command":68},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill cometchat-angular-v5-production",{"tool":70,"command":71},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill cometchat-angular-v5-production","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fcometchat\u002Fcometchat-skills\u002Fskills\u002Fcometchat-angular-v5-production\u002FSKILL.md",true,[],[76,85,93,101,109,117],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":80,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":84},"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":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":89,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":84},"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":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":97,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":84},"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":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":105,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":84},"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":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":113,"sourceHtmlUrl":114,"categories":115,"keywords":116,"publishedAt":84},"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":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":121,"sourceHtmlUrl":122,"categories":123,"keywords":124,"publishedAt":84},"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",[],[]]