[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MFM0X98ZM3B2W593FMMGFC":3,"skill-same:01M6MFM0X98ZM3B2W593FMMGFC":81},{"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":47,"linkOnly":48,"markdownContent":49,"markdownBody":50,"frontMatter":51,"refName":57,"commitSha":58,"skillDirectory":59,"forksCount":60,"repositoryHtmlUrl":61,"repositoryHomepageUrl":62,"ownerHtmlUrl":63,"ownerBlogUrl":64,"ownerDescription":65,"updatedAt":66,"install":67,"resources":80},"01M6MFM0X98ZM3B2W593FMMGFC","cometchat-react-v7-push",null,"Add web push notifications to a React app with the CometChat v7 SDK — FCM via Firebase, registered through CometChatNotifications, with the Dashboard FCM provider as the sender. THIN + docs-first: the full setup is FETCHED from CometChat's notifications docs; this skill bakes only the hardening deltas + the token lifecycle. Triggers: 'add push notifications', 'web push', 'FCM push', 'notify on new message when app closed', 'cometchat push react'.","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1571,"MIT","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fcometchat\u002Fcometchat-skills\u002Fskills\u002Fcometchat-react-v7-push\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,45,46],"cometchat react v7 push","push","react","cometchat","when","new","push notifications","uikit","triggers","firebase","lifecycle","provider","as","add","full","token","message","dashboard","notifications","only","notify","deltas","app","2026-11-10 10:12:30",false,"---\nname: cometchat-react-v7-push\ndescription: \"Add web push notifications to a React app with the CometChat v7 SDK — FCM via Firebase, registered through CometChatNotifications, with the Dashboard FCM provider as the sender. THIN + docs-first: the full setup is FETCHED from CometChat's notifications docs; this skill bakes only the hardening deltas + the token lifecycle. Triggers: 'add push notifications', 'web push', 'FCM push', 'notify on new message when app closed', 'cometchat push react'.\"\nlicense: \"MIT\"\ncompatibility: \"React >=18; @cometchat\u002Fchat-uikit-react ^7 (7.2.x); @cometchat\u002Fchat-sdk-javascript ^4.1.9 (ships CometChatNotifications); firebase ^10.3.1 (FCM web SDK)\"\nmetadata:\n  author: \"CometChat\"\n  version: \"1.0.0\"\n  tags: \"cometchat react push notifications fcm firebase web v7\"\n---\n\n> **Ground truth — DOCS-FIRST.** Push is an EXTERNAL integration (Firebase\u002FFCM + a service worker + a Dashboard FCM provider), not a UI Kit component. The full, current setup lives in **CometChat's notifications docs — FETCH them, don't bake a recipe here**: via `cometchat-react-v7-core\u002Freferences\u002Fdocs-map.md` → `\u002Fnotifications\u002Fpush-overview` · `\u002Fnotifications\u002Fweb-push-notifications` · `\u002Fnotifications\u002Fpreferences`. This skill is THIN: it points you at those docs as the SOURCE and bakes ONLY the hardening deltas + the exact SDK symbols (verified vs installed `@cometchat\u002Fchat-sdk-javascript`). **Symbols are baked; the step-by-step is fetched.**\n\n## Companion skills (read first)\n- `cometchat-react-v7-core` — install, credentials, `init→login→render`. This skill ASSUMES it (push registers AFTER login, on the SAME SDK).\n\n## Use this skill when\n\"add push notifications\", \"web push\", \"notify me on a new message when the app is closed\", \"FCM push\". For a NON-web platform (Android\u002FiOS\u002FRN\u002FFlutter) push differs — that's not this skill.\n\n## Build it — FETCH the docs, then apply the deltas\n1. **FETCH the setup from the docs** (source of truth): `{DOCS_BASE}\u002Fnotifications\u002Fweb-push-notifications.md` (+ `push-overview.md`) via `docs-map.md`. Follow its Firebase project + FCM setup, the `firebase-messaging-sw.js` service worker, and the client registration flow. **Build FROM the docs; if the docs are wrong\u002Fmissing a detail, that's a DOCS gap — flag it (RULES §20), don't bake a permanent workaround.**\n2. **Dashboard prerequisite:** set up the **FCM provider in the CometChat Dashboard** (it is the SENDER). Self-hosted VAPID \u002F a custom webhook is NOT the v7 web path. Confirm this is done or push delivers nothing.\n3. **Install:** `npm i firebase@^10.3.1` (the FCM web SDK). `CometChatNotifications` ships with the already-installed `@cometchat\u002Fchat-sdk-javascript` — no extra CometChat package.\n\n## Baked SDK symbols (verified vs installed SDK 4.2.1 — do NOT guess these)\n```ts\nimport { CometChat, CometChatNotifications } from \"@cometchat\u002Fchat-sdk-javascript\";\n\u002F\u002F Register AFTER login, with the FCM token you got from firebase getToken():\nawait CometChatNotifications.registerPushToken(\n  fcmToken,                                    \u002F\u002F string — from firebase messaging getToken({ vapidKey })\n  CometChatNotifications.PushPlatforms.FCM_WEB,   \u002F\u002F enum member\n  providerId                                   \u002F\u002F optional — your Dashboard FCM provider id\n);\n\u002F\u002F On logout (before CometChatUIKit.logout()):\nawait CometChatNotifications.unregisterPushToken();\n```\n> Signature (installed source): `registerPushToken(pushToken: string, platform: PushPlatforms, providerId?: string)` · `unregisterPushToken()`. Fetch anything beyond these from the notifications docs.\n\n## Hardening deltas (BAKED — the things the docs tend to under-emphasize)\n- **Service-worker placement is per-bundler.** `firebase-messaging-sw.js` must be served from the ORIGIN ROOT: **Vite \u002F CRA → `public\u002Ffirebase-messaging-sw.js`** (copied to the web root); **Next.js → `public\u002Ffirebase-messaging-sw.js`** (App or Pages router); **Astro → `public\u002Ffirebase-messaging-sw.js`**. A SW under `src\u002F` or a hashed asset path will NOT register. HTTPS (or `localhost`) is required.\n- **Request permission ON A USER GESTURE, not on load.** Call `Notification.requestPermission()` from a click\u002Ftap (a browser blocks\u002Fannoys otherwise). Only call `getToken()` after permission is `granted`.\n- **Token lifecycle = tie it to login\u002Flogout.** `registerPushToken(...)` AFTER `CometChatUIKit.login()` resolves; `unregisterPushToken()` BEFORE `CometChatUIKit.logout()`. Re-register on token refresh (`onTokenRefresh`\u002F`getToken` again). Skipping unregister on logout leaks notifications to the wrong user.\n- **iOS web push is PWA-only.** On iOS\u002FiPadOS, web push works ONLY in an **installed PWA** (Add to Home Screen) on **iOS 16.4+** — not in a normal Safari tab. Tell the user; don't promise Safari-tab push on iOS.\n- **The Dashboard FCM provider is the sender.** No self-hosted VAPID server \u002F webhook for v7 web — configure the provider in the Dashboard (step 2).\n\n## Common pitfalls (BAKED)\n- SW not at the origin root → registration silently fails, no push. · Requesting permission on load → blocked\u002Fdenied. · Forgetting `unregisterPushToken()` on logout → cross-user leakage. · Expecting Safari-tab push on iOS. · No Dashboard FCM provider → nothing delivers even with correct client code.\n\n## Verify it works (honest — push can't be auto-smoked)\nStatic verification only: the SDK symbols resolve + the app compiles + the SW registers (check the browser Application → Service Workers). **Live delivery is a manual, device-dependent check** (real HTTPS origin + a registered SW + the Dashboard FCM provider + `granted` permission → send a message with the app backgrounded). This is the one skill whose live gate is inherently **blocked-external** — do NOT claim delivery works from a build alone.\n\n## Close (after it builds)\nEnd with the shared 3-option selectable menu and WAIT for the pick — **(1) add another feature** (suggest a few not-yet-wired) · **(2) customize theming** · **(3) test it manually** (stop; let the user check). Same contract as the `cometchat-react-v7-core` close (`RULES.md` §19).\n","> **Ground truth — DOCS-FIRST.** Push is an EXTERNAL integration (Firebase\u002FFCM + a service worker + a Dashboard FCM provider), not a UI Kit component. The full, current setup lives in **CometChat's notifications docs — FETCH them, don't bake a recipe here**: via `cometchat-react-v7-core\u002Freferences\u002Fdocs-map.md` → `\u002Fnotifications\u002Fpush-overview` · `\u002Fnotifications\u002Fweb-push-notifications` · `\u002Fnotifications\u002Fpreferences`. This skill is THIN: it points you at those docs as the SOURCE and bakes ONLY the hardening deltas + the exact SDK symbols (verified vs installed `@cometchat\u002Fchat-sdk-javascript`). **Symbols are baked; the step-by-step is fetched.**\n\n## Companion skills (read first)\n- `cometchat-react-v7-core` — install, credentials, `init→login→render`. This skill ASSUMES it (push registers AFTER login, on the SAME SDK).\n\n## Use this skill when\n\"add push notifications\", \"web push\", \"notify me on a new message when the app is closed\", \"FCM push\". For a NON-web platform (Android\u002FiOS\u002FRN\u002FFlutter) push differs — that's not this skill.\n\n## Build it — FETCH the docs, then apply the deltas\n1. **FETCH the setup from the docs** (source of truth): `{DOCS_BASE}\u002Fnotifications\u002Fweb-push-notifications.md` (+ `push-overview.md`) via `docs-map.md`. Follow its Firebase project + FCM setup, the `firebase-messaging-sw.js` service worker, and the client registration flow. **Build FROM the docs; if the docs are wrong\u002Fmissing a detail, that's a DOCS gap — flag it (RULES §20), don't bake a permanent workaround.**\n2. **Dashboard prerequisite:** set up the **FCM provider in the CometChat Dashboard** (it is the SENDER). Self-hosted VAPID \u002F a custom webhook is NOT the v7 web path. Confirm this is done or push delivers nothing.\n3. **Install:** `npm i firebase@^10.3.1` (the FCM web SDK). `CometChatNotifications` ships with the already-installed `@cometchat\u002Fchat-sdk-javascript` — no extra CometChat package.\n\n## Baked SDK symbols (verified vs installed SDK 4.2.1 — do NOT guess these)\n```ts\nimport { CometChat, CometChatNotifications } from \"@cometchat\u002Fchat-sdk-javascript\";\n\u002F\u002F Register AFTER login, with the FCM token you got from firebase getToken():\nawait CometChatNotifications.registerPushToken(\n  fcmToken,                                    \u002F\u002F string — from firebase messaging getToken({ vapidKey })\n  CometChatNotifications.PushPlatforms.FCM_WEB,   \u002F\u002F enum member\n  providerId                                   \u002F\u002F optional — your Dashboard FCM provider id\n);\n\u002F\u002F On logout (before CometChatUIKit.logout()):\nawait CometChatNotifications.unregisterPushToken();\n```\n> Signature (installed source): `registerPushToken(pushToken: string, platform: PushPlatforms, providerId?: string)` · `unregisterPushToken()`. Fetch anything beyond these from the notifications docs.\n\n## Hardening deltas (BAKED — the things the docs tend to under-emphasize)\n- **Service-worker placement is per-bundler.** `firebase-messaging-sw.js` must be served from the ORIGIN ROOT: **Vite \u002F CRA → `public\u002Ffirebase-messaging-sw.js`** (copied to the web root); **Next.js → `public\u002Ffirebase-messaging-sw.js`** (App or Pages router); **Astro → `public\u002Ffirebase-messaging-sw.js`**. A SW under `src\u002F` or a hashed asset path will NOT register. HTTPS (or `localhost`) is required.\n- **Request permission ON A USER GESTURE, not on load.** Call `Notification.requestPermission()` from a click\u002Ftap (a browser blocks\u002Fannoys otherwise). Only call `getToken()` after permission is `granted`.\n- **Token lifecycle = tie it to login\u002Flogout.** `registerPushToken(...)` AFTER `CometChatUIKit.login()` resolves; `unregisterPushToken()` BEFORE `CometChatUIKit.logout()`. Re-register on token refresh (`onTokenRefresh`\u002F`getToken` again). Skipping unregister on logout leaks notifications to the wrong user.\n- **iOS web push is PWA-only.** On iOS\u002FiPadOS, web push works ONLY in an **installed PWA** (Add to Home Screen) on **iOS 16.4+** — not in a normal Safari tab. Tell the user; don't promise Safari-tab push on iOS.\n- **The Dashboard FCM provider is the sender.** No self-hosted VAPID server \u002F webhook for v7 web — configure the provider in the Dashboard (step 2).\n\n## Common pitfalls (BAKED)\n- SW not at the origin root → registration silently fails, no push. · Requesting permission on load → blocked\u002Fdenied. · Forgetting `unregisterPushToken()` on logout → cross-user leakage. · Expecting Safari-tab push on iOS. · No Dashboard FCM provider → nothing delivers even with correct client code.\n\n## Verify it works (honest — push can't be auto-smoked)\nStatic verification only: the SDK symbols resolve + the app compiles + the SW registers (check the browser Application → Service Workers). **Live delivery is a manual, device-dependent check** (real HTTPS origin + a registered SW + the Dashboard FCM provider + `granted` permission → send a message with the app backgrounded). This is the one skill whose live gate is inherently **blocked-external** — do NOT claim delivery works from a build alone.\n\n## Close (after it builds)\nEnd with the shared 3-option selectable menu and WAIT for the pick — **(1) add another feature** (suggest a few not-yet-wired) · **(2) customize theming** · **(3) test it manually** (stop; let the user check). Same contract as the `cometchat-react-v7-core` close (`RULES.md` §19).\n",{"name":5,"license":15,"metadata":52,"description":7,"compatibility":56},{"tags":53,"author":54,"version":55},"cometchat react push notifications fcm firebase web v7","CometChat","1.0.0","React >=18; @cometchat\u002Fchat-uikit-react ^7 (7.2.x); @cometchat\u002Fchat-sdk-javascript ^4.1.9 (ships CometChatNotifications); firebase ^10.3.1 (FCM web SDK)","main","cebc3dce495d7eb80d3b1d5841f877a4a92e162d","plugins\u002Fcometchat\u002Fcometchat-skills\u002Fskills\u002Fcometchat-react-v7-push",490,"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 02:12:02",{"source":8,"skillName":5,"commands":68,"prompt":78,"zipAvailable":79},[69,72,75],{"tool":70,"command":71},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill cometchat-react-v7-push",{"tool":73,"command":74},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill cometchat-react-v7-push",{"tool":76,"command":77},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill cometchat-react-v7-push","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fcometchat\u002Fcometchat-skills\u002Fskills\u002Fcometchat-react-v7-push\u002FSKILL.md",true,[],[82,91,98,105,131,156],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":86,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":90},"01M746ZWACVKMZ1BJXJZHYJSSX","migrate-to-e2e","Moves an existing Playwright, Cypress, Selenium, Appium, Detox, Maestro, or TesterArmy suite to e2e one slice at a time, with the old suite running beside the new one until each ported test is proven. Keeps a MIGRATION.md progress file so any later session resumes where the last stopped. Optionally plants a defect to show both suites catch it. Use for \u002Fmigrate-to-e2e, \"migrate our tests to e2e\", \"port these Maestro flows\", \"move our TesterArmy tests\", or when a project has an e2e config and an older suite still running.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftester-army\u002Fe2e\u002Fskills\u002Fmigrate-to-e2e\u002FSKILL.md",[],[],"2026-11-11 15:11:14",{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":86,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":90},"01M746ZPTAX1Q0FBKAB1CYND7E","e2e","Writes, runs, and debugs end-to-end tests for web and mobile apps with e2e, the agentic test runner, which mixes agent.act goals with exact locator assertions on a Playwright browser or an iOS or Android device. Also drives a project's running app live over the e2e MCP server to look at a screen, check a UI change, take a screenshot or record a video, and try a locator; and runs bug bashes, parallel e2e explore runs with each bug proven by a repro test. Use when a project depends on e2e or has an e2e.config.ts, when asked for end-to-end, browser, mobile, or agentic UI tests, to check a change in the running app, to QA or bug bash an app or branch, or when an e2e run fails.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftester-army\u002Fe2e\u002Fskills\u002Fe2e\u002FSKILL.md",[],[],{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":86,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":90},"01M746ZJN784HVHMDP9MQGCSGG","create-verification-skill","Generate a project-local verify-\u003Capp> skill on top of e2e, so any coding agent can launch the app, check it is worth driving, exercise a feature the way a user does, keep evidence, and bug bash it. Writes the skill, a feature map with one explore charter per feature, and proves it once. Use for \u002Fcreate-verification-skill, \"make a verification skill for this repo\", or when a project has no scripted way to prove UI behavior.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftester-army\u002Fe2e\u002Fskills\u002Fcreate-verification-skill\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":86,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":47},"01M716A6ETNB9B1SQ3GXZC75VR","deja-search","deja-vu memory — search the user's past AI coding sessions with the deja CLI. Holds what they already settled and never wrote into the repo (naming rules, banned or already-tried tools, required checks before merge, preferred values, who owns what). Use before your first edit in a task, before you call a change done or ready to merge, before you recommend a tool, library, design or reviewer, before re-debugging an error that may already be solved, when they say 'didn't we fix this before', 'what did we decide about X' or 'I already have that', and before telling them something on this machine does not exist.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fvshulcz\u002Fdeja-vu\u002Fskills\u002Fdeja-search\u002FSKILL.md",[],[112,113,114,115,116,117,118,119,120,121,122,28,123,124,125,126,127,128,129,130],"search","deja search","never","error","ready","memory","re","decide","fix","design","debugging","you","done","reviewer","io","change","cli","merge","past",{"skillNo":132,"name":133,"nameZh":6,"description":134,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":86,"licenseFileUrl":6,"sourceHtmlUrl":135,"categories":136,"keywords":137,"publishedAt":47},"01M716A3J2W5SENSE9VGMXB375","deja-reflect","End-of-session reflection and memory curation with deja-vu. Review what was decided, what commands broke and what repaired them, and record durable project rules or decisions with deja remember so the next session starts with them.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fvshulcz\u002Fdeja-vu\u002Fskills\u002Fdeja-reflect\u002FSKILL.md",[],[138,139,140,126,141,142,143,144,145,146,147,148,149,150,117,151,152,153,154,155],"deja reflect","reflect","review","with","record","github","next","https","node","Rules","decisions","brew","remember","project rules","project","session","end","reflection",{"skillNo":157,"name":158,"nameZh":6,"description":159,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":86,"licenseFileUrl":6,"sourceHtmlUrl":160,"categories":161,"keywords":171,"publishedAt":47},"01M715T3RR4BAYSR57HPPTJ0PF","revid","Make, edit, export and post AI videos with Revid (revid.ai) through the Revid MCP server. Use whenever the user wants a short-form or long-form video made (from an idea, a script, a URL, an article, a PDF, a tweet, a product page, their own clips, or a song), wants to find what is going viral on TikTok, YouTube, Instagram or X before making something, wants to edit or re-export an existing Revid project, generate a standalone AI image or clip, make a series episode, or publish and schedule a finished video to connected social accounts. Covers setup (hosted MCP with OAuth, or an API key), the 36 tools, credits, polling and the rules for publishing. Routes to the more specific revid-* skills when one fits.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftmakersas\u002Frevid-skills\u002Fskills\u002Frevid\u002FSKILL.md",[162,165,168],{"categoryNo":163,"categoryName":164,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":166,"categoryName":167,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":169,"categoryName":170,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",[158,172,173,174,175,176,177,152,178,118,179,180,181,182,28,183,184,185,186,187],"URL","Video","short-form","standalone","PDF","viral","tiktok","short","social","MCP","song","image","mcp server","schedule","api","publish"]