[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7E8K5F5MPC1NHGE700GEZBK":3,"skill-same:01M7E8K5F5MPC1NHGE700GEZBK":130},{"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":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":84,"commitSha":85,"skillDirectory":86,"forksCount":14,"repositoryHtmlUrl":87,"repositoryHomepageUrl":6,"ownerHtmlUrl":88,"ownerBlogUrl":89,"ownerDescription":90,"updatedAt":91,"install":92,"resources":105},"01M7E8K5F5MPC1NHGE700GEZBK","vercel-services",null,"Vercel Services — deploy multiple services within a single Vercel project. Use for monorepo layouts or when combining a backend (Python, Go) with a frontend (Next.js, Vite) in one deployment.","wxdwu\u002Fnew-api","wxdwu","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F80968397?v=4","01M7E6AEMB59N90BKXD77EC83D","Xudong Wu","01M7E6AEMY2BXCDVZ9MJJHFQ4C",0,"AGPL-3.0","https:\u002F\u002Fgithub.com\u002Fwxdwu\u002Fnew-api\u002Fblob\u002Fmain\u002Fplugins\u002F.tmp\u002Fplugins\u002Fplugins\u002Fvercel\u002Fskills\u002Fvercel-services\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: vercel-services\ndescription: \"Vercel Services — deploy multiple services within a single Vercel project. Use for monorepo layouts or when combining a backend (Python, Go) with a frontend (Next.js, Vite) in one deployment.\"\nmetadata:\n  priority: 7\n  docs:\n    - \"https:\u002F\u002Fvercel.com\u002Fdocs\u002Fservices\"\n  sitemap: \"https:\u002F\u002Fvercel.com\u002Fsitemap\u002Fdocs.xml\"\n  pathPatterns:\n    - 'backend\u002F**'\n    - 'backend\u002Fmain.py'\n    - 'backend\u002Fmain.go'\n    - 'backend\u002Fgo.mod'\n    - 'backend\u002Fpyproject.toml'\n    - 'backend\u002Frequirements.txt'\n    - 'frontend\u002F**'\n    - 'apps\u002F*\u002Fbackend\u002F**'\n    - 'apps\u002F*\u002Ffrontend\u002F**'\n    - 'services\u002F*\u002Fvercel.json'\n    - '*\u002Fpyproject.toml'\n    - '*\u002Fgo.mod'\n  bashPatterns:\n    - '\\bvercel\\s+dev\\b.*-L'\n    - '\\bpip\\s+install\\b.*fastapi'\n    - '\\buv\\s+(sync|pip|run)\\b'\n    - '\\bgo\\s+(run|build|mod)\\b'\n    - '\\bpython\\s+-m\\s+uvicorn\\b'\n    - '\\buvicorn\\b'\n  importPatterns:\n    - \"fastapi\"\n  promptSignals:\n    phrases:\n      - \"services api\"\n      - \"vercel services\"\n      - \"multi-service\"\n      - \"python backend\"\n      - \"go backend\"\n      - \"fastapi\"\n      - \"deploy backend\"\n      - \"backend and frontend\"\n      - \"multiple services\"\n    allOf:\n      - [backend, frontend]\n      - [python, vercel]\n      - [go, vercel]\n      - [backend, deploy]\n      - [service, monorepo]\n      - [fastapi, deploy]\n    anyOf:\n      - \"backend\"\n      - \"monorepo\"\n      - \"service\"\n      - \"python\"\n      - \"golang\"\n    noneOf:\n      - \"turborepo cache\"\n      - \"turbo.json\"\n      - \"aws lambda\"\n      - \"docker compose\"\n    minScore: 6\n---\n\n# Deploy multi-service projects with Vercel\n\nServices let you deploy multiple independently-built units within a single Vercel project. The typical use case is combining different runtimes (e.g. Python + JavaScript) in one deployment with shared routing and environment variables, but services work for any combination — multiple services of the same runtime, different frameworks, or a mix.\n\nThis skill covers **project structure and configuration**. For the actual deployment, defer to the **deployments-cicd** skill.\n\n## How It Works\n\nA service is an independently built unit within your project, deployed to the same domain under a unique subpath. At build time, Vercel builds each service separately. At request time, Vercel routes incoming requests to the correct service based on the URL path prefix (longest prefix wins).\n\n- Services are enabled via the `experimentalServices` field in `vercel.json` (see reference project).\n- `vercel dev -L` auto-detects frameworks and runs all services locally as one application, handling routing automatically. The `-L` flag (short for `--local`) runs without authenticating with Vercel Cloud.\n- Only `vercel.json` lives at the root. Each service manages its own dependencies independently.\n\n## Configuration\n\nDefine services in `vercel.json`:\n\n```json\n{\n  \"experimentalServices\": {\n    \"web\": {\n      \"entrypoint\": \"apps\u002Fweb\",\n      \"routePrefix\": \"\u002F\"\n    },\n    \"api\": {\n      \"entrypoint\": \"backend\u002Fmain.py\",\n      \"routePrefix\": \"\u002Fserver\"\n    }\n  }\n}\n```\n\nThe project's Framework Preset must be set to **Services** in the Vercel dashboard.\n\n### Configuration fields\n\n| Field          | Required | Description                                                |\n|----------------|----------|------------------------------------------------------------|\n| `entrypoint`   | Yes      | Path to the service entrypoint file or directory.          |\n| `routePrefix`  | Yes      | URL path prefix for routing (e.g. `\u002F`, `\u002Fapi`, `\u002Fsvc\u002Fgo`). |\n| `framework`    | No       | Framework slug. Pins detection; auto-detected if unset.    |\n| `memory`       | No       | Max available RAM in MB (128–10,240).                      |\n| `maxDuration`  | No       | Execution timeout in seconds (1–900).                      |\n| `includeFiles` | No       | Glob patterns for files to include in the deployment.      |\n| `excludeFiles` | No       | Glob patterns for files to exclude from the deployment.    |\n\nDo not add unknown fields — they will cause the build to fail.\n\n## Supported runtimes and frameworks\n\nServices is in beta. **Python** and **Go** are tested and production-ready. Other runtimes may work but are not yet validated.\n\n### Python\n\nWorks with FastAPI, Flask, Django, or any ASGI\u002FWSGI application. Framework is auto-detected. Set `entrypoint` to the application file (e.g. `\"backend\u002Fmain.py\"`). Dependencies go in `pyproject.toml` in the service directory.\n\n### Go\n\nSet `entrypoint` to the service **directory** (e.g. `\"backend\"`), not a file. **Must** set `\"framework\": \"go\"` explicitly in `vercel.json` — auto-detection does not work for Go services. Dependencies in `go.mod` in the service directory.\n\n### Other runtimes (untested)\n\nVercel supports Node.js, Bun, Rust, Ruby, Wasm, and Edge runtimes for functions. These can theoretically be used as services but are not yet validated.\n\n## Routing\n\nVercel evaluates route prefixes from longest to shortest (most specific first), with the primary service (`\u002F`) as the catch-all. Vercel automatically mounts services at their `routePrefix`, so service handlers should **not** include the prefix in their routes.\n\nFor frontend frameworks mounted on a subpath (not `\u002F`), configure the framework's own base path (e.g. `basePath` in `next.config.js`) to match `routePrefix`.\n\n## Environment variables\n\nVercel auto-generates URL variables so services can find each other:\n\n| Variable                        | Example value                            | Availability | Use case                              |\n|---------------------------------|------------------------------------------|--------------|---------------------------------------|\n| `{SERVICENAME}_URL`             | `https:\u002F\u002Fyour-deploy.vercel.app\u002Fsvc\u002Fapi` | Server-side  | Server-to-server requests             |\n| `NEXT_PUBLIC_{SERVICENAME}_URL` | `\u002Fsvc\u002Fapi`                               | Client-side  | Browser requests (relative, no CORS)  |\n\n`SERVICENAME` is the key name from `experimentalServices`, uppercased. If you define an env var with the same name in project settings, your value takes precedence.\n\n## Usage\n\n1. Read `references\u002Ffastapi-vite\u002F` for the canonical project layout.\n2. Adapt the structure to the user's chosen runtimes — services can use any supported runtime, not just the ones in the reference.\n3. Define service routes **without** the route prefix — Vercel strips the prefix before forwarding.\n4. Validate that each service in `vercel.json` has `entrypoint` and `routePrefix`. Only set `framework` when auto-detection fails (required for Go).\n\n## Output\n\nAfter scaffolding, present the created file structure to the user. After deployment, present the deployment URL (refer to the **deployments-cicd** skill for details).\n\n## Troubleshooting\n\n### 404 on routes after deployment\n\nThe project needs the Services framework preset:\n\n1. Go to Project Settings → Build & Deployment → Framework Preset\n2. Select **Services** from the dropdown\n3. Redeploy\n\n### Routes return unexpected results\n\n1. Ensure all services are picked up by `vercel dev` — check logs. If a service is missing, verify `vercel.json`. Try setting `framework` explicitly.\n2. Validate route prefix behavior: handlers declare routes without `routePrefix` (e.g. `\u002Fhealth`), but requests from other services use the full prefix (e.g. `\u002Fapi\u002Fhealth`).\n3. For frontend services on a subpath, confirm the framework's base path config matches `routePrefix`.\n","# Deploy multi-service projects with Vercel\n\nServices let you deploy multiple independently-built units within a single Vercel project. The typical use case is combining different runtimes (e.g. Python + JavaScript) in one deployment with shared routing and environment variables, but services work for any combination — multiple services of the same runtime, different frameworks, or a mix.\n\nThis skill covers **project structure and configuration**. For the actual deployment, defer to the **deployments-cicd** skill.\n\n## How It Works\n\nA service is an independently built unit within your project, deployed to the same domain under a unique subpath. At build time, Vercel builds each service separately. At request time, Vercel routes incoming requests to the correct service based on the URL path prefix (longest prefix wins).\n\n- Services are enabled via the `experimentalServices` field in `vercel.json` (see reference project).\n- `vercel dev -L` auto-detects frameworks and runs all services locally as one application, handling routing automatically. The `-L` flag (short for `--local`) runs without authenticating with Vercel Cloud.\n- Only `vercel.json` lives at the root. Each service manages its own dependencies independently.\n\n## Configuration\n\nDefine services in `vercel.json`:\n\n```json\n{\n  \"experimentalServices\": {\n    \"web\": {\n      \"entrypoint\": \"apps\u002Fweb\",\n      \"routePrefix\": \"\u002F\"\n    },\n    \"api\": {\n      \"entrypoint\": \"backend\u002Fmain.py\",\n      \"routePrefix\": \"\u002Fserver\"\n    }\n  }\n}\n```\n\nThe project's Framework Preset must be set to **Services** in the Vercel dashboard.\n\n### Configuration fields\n\n| Field          | Required | Description                                                |\n|----------------|----------|------------------------------------------------------------|\n| `entrypoint`   | Yes      | Path to the service entrypoint file or directory.          |\n| `routePrefix`  | Yes      | URL path prefix for routing (e.g. `\u002F`, `\u002Fapi`, `\u002Fsvc\u002Fgo`). |\n| `framework`    | No       | Framework slug. Pins detection; auto-detected if unset.    |\n| `memory`       | No       | Max available RAM in MB (128–10,240).                      |\n| `maxDuration`  | No       | Execution timeout in seconds (1–900).                      |\n| `includeFiles` | No       | Glob patterns for files to include in the deployment.      |\n| `excludeFiles` | No       | Glob patterns for files to exclude from the deployment.    |\n\nDo not add unknown fields — they will cause the build to fail.\n\n## Supported runtimes and frameworks\n\nServices is in beta. **Python** and **Go** are tested and production-ready. Other runtimes may work but are not yet validated.\n\n### Python\n\nWorks with FastAPI, Flask, Django, or any ASGI\u002FWSGI application. Framework is auto-detected. Set `entrypoint` to the application file (e.g. `\"backend\u002Fmain.py\"`). Dependencies go in `pyproject.toml` in the service directory.\n\n### Go\n\nSet `entrypoint` to the service **directory** (e.g. `\"backend\"`), not a file. **Must** set `\"framework\": \"go\"` explicitly in `vercel.json` — auto-detection does not work for Go services. Dependencies in `go.mod` in the service directory.\n\n### Other runtimes (untested)\n\nVercel supports Node.js, Bun, Rust, Ruby, Wasm, and Edge runtimes for functions. These can theoretically be used as services but are not yet validated.\n\n## Routing\n\nVercel evaluates route prefixes from longest to shortest (most specific first), with the primary service (`\u002F`) as the catch-all. Vercel automatically mounts services at their `routePrefix`, so service handlers should **not** include the prefix in their routes.\n\nFor frontend frameworks mounted on a subpath (not `\u002F`), configure the framework's own base path (e.g. `basePath` in `next.config.js`) to match `routePrefix`.\n\n## Environment variables\n\nVercel auto-generates URL variables so services can find each other:\n\n| Variable                        | Example value                            | Availability | Use case                              |\n|---------------------------------|------------------------------------------|--------------|---------------------------------------|\n| `{SERVICENAME}_URL`             | `https:\u002F\u002Fyour-deploy.vercel.app\u002Fsvc\u002Fapi` | Server-side  | Server-to-server requests             |\n| `NEXT_PUBLIC_{SERVICENAME}_URL` | `\u002Fsvc\u002Fapi`                               | Client-side  | Browser requests (relative, no CORS)  |\n\n`SERVICENAME` is the key name from `experimentalServices`, uppercased. If you define an env var with the same name in project settings, your value takes precedence.\n\n## Usage\n\n1. Read `references\u002Ffastapi-vite\u002F` for the canonical project layout.\n2. Adapt the structure to the user's chosen runtimes — services can use any supported runtime, not just the ones in the reference.\n3. Define service routes **without** the route prefix — Vercel strips the prefix before forwarding.\n4. Validate that each service in `vercel.json` has `entrypoint` and `routePrefix`. Only set `framework` when auto-detection fails (required for Go).\n\n## Output\n\nAfter scaffolding, present the created file structure to the user. After deployment, present the deployment URL (refer to the **deployments-cicd** skill for details).\n\n## Troubleshooting\n\n### 404 on routes after deployment\n\nThe project needs the Services framework preset:\n\n1. Go to Project Settings → Build & Deployment → Framework Preset\n2. Select **Services** from the dropdown\n3. Redeploy\n\n### Routes return unexpected results\n\n1. Ensure all services are picked up by `vercel dev` — check logs. If a service is missing, verify `vercel.json`. Try setting `framework` explicitly.\n2. Validate route prefix behavior: handlers declare routes without `routePrefix` (e.g. `\u002Fhealth`), but requests from other services use the full prefix (e.g. `\u002Fapi\u002Fhealth`).\n3. For frontend services on a subpath, confirm the framework's base path config matches `routePrefix`.\n",{"name":5,"metadata":24,"description":7},{"docs":25,"sitemap":27,"priority":28,"bashPatterns":29,"pathPatterns":36,"promptSignals":49,"importPatterns":83},[26],"https:\u002F\u002Fvercel.com\u002Fdocs\u002Fservices","https:\u002F\u002Fvercel.com\u002Fsitemap\u002Fdocs.xml",7,[30,31,32,33,34,35],"\\bvercel\\s+dev\\b.*-L","\\bpip\\s+install\\b.*fastapi","\\buv\\s+(sync|pip|run)\\b","\\bgo\\s+(run|build|mod)\\b","\\bpython\\s+-m\\s+uvicorn\\b","\\buvicorn\\b",[37,38,39,40,41,42,43,44,45,46,47,48],"backend\u002F**","backend\u002Fmain.py","backend\u002Fmain.go","backend\u002Fgo.mod","backend\u002Fpyproject.toml","backend\u002Frequirements.txt","frontend\u002F**","apps\u002F*\u002Fbackend\u002F**","apps\u002F*\u002Ffrontend\u002F**","services\u002F*\u002Fvercel.json","*\u002Fpyproject.toml","*\u002Fgo.mod",{"allOf":50,"anyOf":66,"noneOf":68,"phrases":73,"minScore":82},[51,54,57,59,61,64],[52,53],"backend","frontend",[55,56],"python","vercel",[58,56],"go",[52,60],"deploy",[62,63],"service","monorepo",[65,60],"fastapi",[52,63,62,55,67],"golang",[69,70,71,72],"turborepo cache","turbo.json","aws lambda","docker compose",[74,75,76,77,78,65,79,80,81],"services api","vercel services","multi-service","python backend","go backend","deploy backend","backend and frontend","multiple services",6,[65],"main","dde9a06ab10bce3fe52058c783826590231f7df3","plugins\u002F.tmp\u002Fplugins\u002Fplugins\u002Fvercel\u002Fskills\u002Fvercel-services","https:\u002F\u002Fgithub.com\u002Fwxdwu\u002Fnew-api","https:\u002F\u002Fgithub.com\u002Fwxdwu","24120128@bjtu.edu.cn","I am Xudong Wu，a student in beijing jiaotong University, \"I am eager to learn on GitHub and contribute my part to this community.","2026-10-05 17:26:50",{"source":8,"skillName":5,"commands":93,"prompt":103,"zipAvailable":104},[94,97,100],{"tool":95,"command":96},"npx","npx skills add wxdwu\u002Fnew-api --skill vercel-services",{"tool":98,"command":99},"bunx","bunx skills add wxdwu\u002Fnew-api --skill vercel-services",{"tool":101,"command":102},"pnpm","pnpm dlx skills add wxdwu\u002Fnew-api --skill vercel-services","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fwxdwu\u002Fnew-api\u002Fblob\u002Fmain\u002Fplugins\u002F.tmp\u002Fplugins\u002Fplugins\u002Fvercel\u002Fskills\u002Fvercel-services\u002FSKILL.md",true,[106,112,116,120,126],{"path":107,"resourceType":108,"resourceTypeDesc":109,"sizeBytes":110,"sourceHtmlUrl":111},"agents\u002Fopenai.yaml","REFERENCE","参考文档",144,"https:\u002F\u002Fgithub.com\u002Fwxdwu\u002Fnew-api\u002Fblob\u002Fmain\u002Fplugins\u002F.tmp\u002Fplugins\u002Fplugins\u002Fvercel\u002Fskills\u002Fvercel-services\u002Fagents\u002Fopenai.yaml",{"path":113,"resourceType":108,"resourceTypeDesc":109,"sizeBytes":114,"sourceHtmlUrl":115},"references\u002Ffastapi-vite\u002Fbackend\u002Fpyproject.toml",165,"https:\u002F\u002Fgithub.com\u002Fwxdwu\u002Fnew-api\u002Fblob\u002Fmain\u002Fplugins\u002F.tmp\u002Fplugins\u002Fplugins\u002Fvercel\u002Fskills\u002Fvercel-services\u002Freferences\u002Ffastapi-vite\u002Fbackend\u002Fpyproject.toml",{"path":117,"resourceType":108,"resourceTypeDesc":109,"sizeBytes":118,"sourceHtmlUrl":119},"references\u002Ffastapi-vite\u002Ffrontend\u002Fpackage.json",320,"https:\u002F\u002Fgithub.com\u002Fwxdwu\u002Fnew-api\u002Fblob\u002Fmain\u002Fplugins\u002F.tmp\u002Fplugins\u002Fplugins\u002Fvercel\u002Fskills\u002Fvercel-services\u002Freferences\u002Ffastapi-vite\u002Ffrontend\u002Fpackage.json",{"path":121,"resourceType":122,"resourceTypeDesc":123,"sizeBytes":124,"sourceHtmlUrl":125},"references\u002Ffastapi-vite\u002Ffrontend\u002Fvite.config.ts","SCRIPT","脚本",133,"https:\u002F\u002Fgithub.com\u002Fwxdwu\u002Fnew-api\u002Fblob\u002Fmain\u002Fplugins\u002F.tmp\u002Fplugins\u002Fplugins\u002Fvercel\u002Fskills\u002Fvercel-services\u002Freferences\u002Ffastapi-vite\u002Ffrontend\u002Fvite.config.ts",{"path":127,"resourceType":108,"resourceTypeDesc":109,"sizeBytes":128,"sourceHtmlUrl":129},"references\u002Ffastapi-vite\u002Fvercel.json",208,"https:\u002F\u002Fgithub.com\u002Fwxdwu\u002Fnew-api\u002Fblob\u002Fmain\u002Fplugins\u002F.tmp\u002Fplugins\u002Fplugins\u002Fvercel\u002Fskills\u002Fvercel-services\u002Freferences\u002Ffastapi-vite\u002Fvercel.json",[131,138,145,152,159,166],{"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":15,"licenseFileUrl":6,"sourceHtmlUrl":135,"categories":136,"keywords":137,"publishedAt":19},"01M7E8SVA2N0JA09RW1XJYXCWX","Zotero","Use Zotero Desktop from Codex to enable\u002Fprobe the local API, search a local Zotero library, list items\u002Fcollections\u002Ftags, export BibTeX, insert citation keys into LaTeX or Markdown drafts, read indexed full text when requested, and import BibTeX\u002FRIS records into Zotero through the connector server. Use when the user mentions Zotero, citations, references.bib, BibTeX export, local Zotero API, localhost:23119, or adding citations from a Zotero library.","https:\u002F\u002Fgithub.com\u002Fwxdwu\u002Fnew-api\u002Fblob\u002Fmain\u002Fplugins\u002F.tmp\u002Fplugins\u002Fplugins\u002Fzotero\u002Fskills\u002Fzotero\u002FSKILL.md",[],[],{"skillNo":139,"name":140,"nameZh":6,"description":141,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":142,"categories":143,"keywords":144,"publishedAt":19},"01M7E8ST1FJAD5PWTW2FN1NSK0","zoom-apps-sdk","Use when using Apps SDK.","https:\u002F\u002Fgithub.com\u002Fwxdwu\u002Fnew-api\u002Fblob\u002Fmain\u002Fplugins\u002F.tmp\u002Fplugins\u002Fplugins\u002Fzoom\u002Fskills\u002Fzoom-apps-sdk\u002FSKILL.md",[],[],{"skillNo":146,"name":147,"nameZh":6,"description":148,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":149,"categories":150,"keywords":151,"publishedAt":19},"01M7E8SRW074NNNCZRCZA5T3Z1","setup-zoom-websockets","Use when building Zoom WebSockets.","https:\u002F\u002Fgithub.com\u002Fwxdwu\u002Fnew-api\u002Fblob\u002Fmain\u002Fplugins\u002F.tmp\u002Fplugins\u002Fplugins\u002Fzoom\u002Fskills\u002Fwebsockets\u002FSKILL.md",[],[],{"skillNo":153,"name":154,"nameZh":6,"description":155,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":156,"categories":157,"keywords":158,"publishedAt":19},"01M7E8SPCFMD3YVPRX2MW8X3RA","setup-zoom-webhooks","Use when building Zoom webhooks.","https:\u002F\u002Fgithub.com\u002Fwxdwu\u002Fnew-api\u002Fblob\u002Fmain\u002Fplugins\u002F.tmp\u002Fplugins\u002Fplugins\u002Fzoom\u002Fskills\u002Fwebhooks\u002FSKILL.md",[],[],{"skillNo":160,"name":161,"nameZh":6,"description":162,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":163,"categories":164,"keywords":165,"publishedAt":19},"01M7E8SMCH4RPCX8YSBNGWQCMP","zoom-virtual-agent-web","Zoom Virtual Agent SDK for web embeds. Use for campaign or entry ID chat launch, event-driven controls, user context updates, and CSP-safe deployment.","https:\u002F\u002Fgithub.com\u002Fwxdwu\u002Fnew-api\u002Fblob\u002Fmain\u002Fplugins\u002F.tmp\u002Fplugins\u002Fplugins\u002Fzoom\u002Fskills\u002Fvirtual-agent\u002Fweb\u002FSKILL.md",[],[],{"skillNo":167,"name":168,"nameZh":6,"description":169,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":170,"categories":171,"keywords":172,"publishedAt":19},"01M7E8SJCAY323E36Z8SAP8H4M","zoom-virtual-agent-ios","Zoom Virtual Agent iOS integration via WKWebView. Use for Swift\u002FObjective-C script injection, message handlers, support_handoff relay, and URL routing policies.","https:\u002F\u002Fgithub.com\u002Fwxdwu\u002Fnew-api\u002Fblob\u002Fmain\u002Fplugins\u002F.tmp\u002Fplugins\u002Fplugins\u002Fzoom\u002Fskills\u002Fvirtual-agent\u002Fios\u002FSKILL.md",[],[]]