[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7E8CEZ2C5K8CWH6WC3PP66S":3,"skill-same:01M7E8CEZ2C5K8CWH6WC3PP66S":85},{"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":57,"commitSha":58,"skillDirectory":59,"forksCount":14,"repositoryHtmlUrl":60,"repositoryHomepageUrl":6,"ownerHtmlUrl":61,"ownerBlogUrl":62,"ownerDescription":63,"updatedAt":64,"install":65,"resources":78},"01M7E8CEZ2C5K8CWH6WC3PP66S","bootstrap",null,"Project bootstrapping orchestrator for repos that depend on Vercel-linked resources (databases, auth, and managed integrations). Use when setting up or repairing a repository so linking, environment provisioning, env pulls, and first-run db\u002Fdev commands happen in the correct safe order.","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\u002Fbootstrap\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: bootstrap\ndescription: Project bootstrapping orchestrator for repos that depend on Vercel-linked resources (databases, auth, and managed integrations). Use when setting up or repairing a repository so linking, environment provisioning, env pulls, and first-run db\u002Fdev commands happen in the correct safe order.\nmetadata:\n  priority: 8\n  docs:\n    - \"https:\u002F\u002Fvercel.com\u002Fdocs\u002Fgetting-started-with-vercel\"\n    - \"https:\u002F\u002Fnextjs.org\u002Fdocs\u002Fgetting-started\u002Finstallation\"\n  sitemap: \"https:\u002F\u002Fvercel.com\u002Fsitemap\u002Fdocs.xml\"\n  pathPatterns:\n    - '.env.example'\n    - '.env.sample'\n    - '.env.template'\n    - 'README*'\n    - 'docs\u002F**\u002Fsetup*'\n    - 'package.json'\n    - 'drizzle.config.*'\n    - 'prisma\u002Fschema.prisma'\n    - 'auth.*'\n    - 'src\u002F**\u002Fauth.*'\n  bashPatterns:\n    - '\\\\bcp\\\\s+\\\\.env\\\\.(?:example|sample|template)\\\\s+\\\\.env\\\\.local\\\\b'\n    - '\\\\b(?:npm|pnpm|bun|yarn)\\\\s+run\\\\s+db:(?:push|seed|migrate|generate)\\\\b'\n    - '\\\\b(?:npm|pnpm|bun|yarn)\\\\s+run\\\\s+dev\\\\b'\n    - '\\\\bvercel\\\\s+link\\\\b'\n    - '\\\\bvercel\\\\s+integration\\\\s+(?:add|install)\\\\b'\n    - '\\\\bvercel\\\\s+env\\\\s+pull\\\\b'\n  importPatterns:\n    - '@neondatabase\u002Fserverless'\n    - 'drizzle-orm'\n    - '@upstash\u002Fredis'\n    - '@vercel\u002Fblob'\n    - '@vercel\u002Fedge-config'\n    - 'next-auth'\n    - '@auth\u002Fcore'\n    - 'better-auth'\n---\n\n# Project Bootstrap Orchestrator\n\nExecute bootstrap in strict order. Do not run migrations or development server until project linking and environment verification are complete.\n\n## Rules\n\n- Do not run `db:push`, `db:migrate`, `db:seed`, or `dev` until Vercel linking is complete and env keys are verified.\n- Prefer Vercel-managed provisioning (`vercel integration ...`) for shared resources.\n- Use provider CLIs only as fallback when Vercel integration flow is unavailable.\n- Never echo secret values in terminal output, logs, or summaries.\n\n## Preflight\n\n1. Confirm Vercel CLI is installed and authenticated.\n\n```bash\nvercel --version\nvercel whoami\n```\n\n2. Confirm repo linkage by checking `.vercel\u002Fproject.json`.\n3. If not linked, inspect available teams\u002Fprojects before asking the user to choose:\n\n```bash\nvercel teams ls\nvercel projects ls --scope \u003Cteam>\nvercel link --yes --scope \u003Cteam> --project \u003Cproject>\n```\n\n4. Find the env template in priority order: `.env.example`, `.env.sample`, `.env.template`.\n5. Create local env file if missing:\n\n```bash\ncp .env.example .env.local\n```\n\n## Resource Setup: Postgres\n\n### Preferred path (Vercel-managed Neon)\n\n1. Read integration setup guidance:\n\n```bash\nvercel integration guide neon\n```\n\n2. Add Neon integration to the Vercel scope:\n\n```bash\nvercel integration add neon --scope \u003Cteam>\n```\n\n3. Verify expected environment variable names exist in Vercel and pull locally:\n\n```bash\nvercel env ls\nvercel env pull .env.local --yes\n```\n\n### Fallback path 1 (Dashboard)\n\n1. Provision Neon through the Vercel dashboard integration UI.\n2. Re-run `vercel env pull .env.local --yes`.\n\n### Fallback path 2 (Neon CLI)\n\nUse Neon CLI only when Vercel-managed provisioning is unavailable. After creating resources, add required env vars in Vercel and pull again.\n\n## AUTH_SECRET Generation\n\nGenerate a high-entropy secret without printing it, then store it in Vercel and refresh local env:\n\n```bash\nAUTH_SECRET=\"$(node -e \"console.log(require('node:crypto').randomBytes(32).toString('base64url'))\")\"\nprintf \"%s\" \"$AUTH_SECRET\" | vercel env add AUTH_SECRET development preview production\nunset AUTH_SECRET\nvercel env pull .env.local --yes\n```\n\n## Env Verification\n\nCompare required keys from template file against `.env.local` keys (names only, never values):\n\n```bash\ntemplate_file=\"\"\nfor candidate in .env.example .env.sample .env.template; do\n  if [ -f \"$candidate\" ]; then\n    template_file=\"$candidate\"\n    break\n  fi\ndone\n\ncomm -23 \\\n  \u003C(grep -E '^[A-Za-z_][A-Za-z0-9_]*=' \"$template_file\" | cut -d '=' -f 1 | sort -u) \\\n  \u003C(grep -E '^[A-Za-z_][A-Za-z0-9_]*=' .env.local | cut -d '=' -f 1 | sort -u)\n```\n\nProceed only when missing key list is empty.\n\n## App Setup\n\nAfter linkage + env verification:\n\n```bash\nnpm run db:push\nnpm run db:seed\nnpm run dev\n```\n\nUse the repository package manager (`npm`, `pnpm`, `bun`, or `yarn`) and run only scripts that exist in `package.json`.\n\n## UI Baseline for Next.js + shadcn Projects\n\nAfter linkage and env verification, establish the UI foundation before feature work:\n1. Add a baseline primitive set: `npx shadcn@latest add button card input label textarea select switch tabs dialog alert-dialog sheet dropdown-menu badge separator skeleton table`\n2. Apply the Geist font fix in `layout.tsx` and `globals.css`.\n3. Confirm the app shell uses `bg-background text-foreground`.\n4. Default to dark mode for product, admin, and AI apps unless the repo is clearly marketing-first.\n\n## Bootstrap Verification\n\nConfirm each checkpoint:\n\n- `vercel whoami` succeeds.\n- `.vercel\u002Fproject.json` exists and matches chosen project.\n- Postgres integration path completed (Vercel integration, dashboard, or provider CLI fallback).\n- `vercel env pull .env.local --yes` succeeds.\n- Required env key diff is empty.\n- Database command status is recorded (`db:push`, `db:seed`, `db:migrate`, `db:generate` as applicable).\n- `dev` command starts without immediate config\u002Fauth\u002Fenv failure.\n\nIf verification fails, stop and report exact failing step plus remediation.\n\n## Summary Format\n\nReturn a final bootstrap summary in this format:\n\n```md\n## Bootstrap Result\n- **Linked Project**: \u003Cteam>\u002F\u003Cproject>\n- **Resource Path**: vercel-integration-neon | dashboard-neon | neon-cli\n- **Env Keys**: \u003Ccount> required, \u003Ccount> present, \u003Ccount> missing\n- **Secrets**: AUTH_SECRET set in Vercel (value never shown)\n- **Migration Status**: not-run | success | failed (\u003Cstep>)\n- **Dev Result**: not-run | started | failed\n```\n\n## Bootstrap Next Steps\n\n- If env keys are still missing, add the missing keys in Vercel and re-run `vercel env pull .env.local --yes`.\n- If DB commands fail, fix connectivity\u002Fschema issues and re-run only the failed db step.\n- If `dev` fails, resolve runtime errors, then restart with your package manager's `run dev`.\n\n## next-forge Projects\n\nIf the project was scaffolded with `npx next-forge init` (detected by `pnpm-workspace.yaml` + `packages\u002Fauth` + `packages\u002Fdatabase` + `@repo\u002F*` imports):\n\n1. Env files are per-app (`apps\u002Fapp\u002F.env.local`, `apps\u002Fweb\u002F.env.local`, `apps\u002Fapi\u002F.env.local`) plus `packages\u002Fdatabase\u002F.env`.\n2. Run `pnpm migrate` (not `db:push`) — it runs `prisma format` + `prisma generate` + `prisma db push`.\n3. Minimum env vars: `DATABASE_URL`, `CLERK_SECRET_KEY`, `NEXT_PUBLIC_CLERK_PUBLISHABLE_KEY`, `NEXT_PUBLIC_APP_URL`, `NEXT_PUBLIC_WEB_URL`, `NEXT_PUBLIC_API_URL`.\n4. Optional services (Stripe, Resend, PostHog, etc.) can be skipped initially — but remove their `@repo\u002F*` imports from app `env.ts` files to avoid validation errors.\n5. Deploy as 3 separate Vercel projects with root directories `apps\u002Fapp`, `apps\u002Fapi`, `apps\u002Fweb`.\n\n=> skill: next-forge — Full next-forge monorepo guide\n","# Project Bootstrap Orchestrator\n\nExecute bootstrap in strict order. Do not run migrations or development server until project linking and environment verification are complete.\n\n## Rules\n\n- Do not run `db:push`, `db:migrate`, `db:seed`, or `dev` until Vercel linking is complete and env keys are verified.\n- Prefer Vercel-managed provisioning (`vercel integration ...`) for shared resources.\n- Use provider CLIs only as fallback when Vercel integration flow is unavailable.\n- Never echo secret values in terminal output, logs, or summaries.\n\n## Preflight\n\n1. Confirm Vercel CLI is installed and authenticated.\n\n```bash\nvercel --version\nvercel whoami\n```\n\n2. Confirm repo linkage by checking `.vercel\u002Fproject.json`.\n3. If not linked, inspect available teams\u002Fprojects before asking the user to choose:\n\n```bash\nvercel teams ls\nvercel projects ls --scope \u003Cteam>\nvercel link --yes --scope \u003Cteam> --project \u003Cproject>\n```\n\n4. Find the env template in priority order: `.env.example`, `.env.sample`, `.env.template`.\n5. Create local env file if missing:\n\n```bash\ncp .env.example .env.local\n```\n\n## Resource Setup: Postgres\n\n### Preferred path (Vercel-managed Neon)\n\n1. Read integration setup guidance:\n\n```bash\nvercel integration guide neon\n```\n\n2. Add Neon integration to the Vercel scope:\n\n```bash\nvercel integration add neon --scope \u003Cteam>\n```\n\n3. Verify expected environment variable names exist in Vercel and pull locally:\n\n```bash\nvercel env ls\nvercel env pull .env.local --yes\n```\n\n### Fallback path 1 (Dashboard)\n\n1. Provision Neon through the Vercel dashboard integration UI.\n2. Re-run `vercel env pull .env.local --yes`.\n\n### Fallback path 2 (Neon CLI)\n\nUse Neon CLI only when Vercel-managed provisioning is unavailable. After creating resources, add required env vars in Vercel and pull again.\n\n## AUTH_SECRET Generation\n\nGenerate a high-entropy secret without printing it, then store it in Vercel and refresh local env:\n\n```bash\nAUTH_SECRET=\"$(node -e \"console.log(require('node:crypto').randomBytes(32).toString('base64url'))\")\"\nprintf \"%s\" \"$AUTH_SECRET\" | vercel env add AUTH_SECRET development preview production\nunset AUTH_SECRET\nvercel env pull .env.local --yes\n```\n\n## Env Verification\n\nCompare required keys from template file against `.env.local` keys (names only, never values):\n\n```bash\ntemplate_file=\"\"\nfor candidate in .env.example .env.sample .env.template; do\n  if [ -f \"$candidate\" ]; then\n    template_file=\"$candidate\"\n    break\n  fi\ndone\n\ncomm -23 \\\n  \u003C(grep -E '^[A-Za-z_][A-Za-z0-9_]*=' \"$template_file\" | cut -d '=' -f 1 | sort -u) \\\n  \u003C(grep -E '^[A-Za-z_][A-Za-z0-9_]*=' .env.local | cut -d '=' -f 1 | sort -u)\n```\n\nProceed only when missing key list is empty.\n\n## App Setup\n\nAfter linkage + env verification:\n\n```bash\nnpm run db:push\nnpm run db:seed\nnpm run dev\n```\n\nUse the repository package manager (`npm`, `pnpm`, `bun`, or `yarn`) and run only scripts that exist in `package.json`.\n\n## UI Baseline for Next.js + shadcn Projects\n\nAfter linkage and env verification, establish the UI foundation before feature work:\n1. Add a baseline primitive set: `npx shadcn@latest add button card input label textarea select switch tabs dialog alert-dialog sheet dropdown-menu badge separator skeleton table`\n2. Apply the Geist font fix in `layout.tsx` and `globals.css`.\n3. Confirm the app shell uses `bg-background text-foreground`.\n4. Default to dark mode for product, admin, and AI apps unless the repo is clearly marketing-first.\n\n## Bootstrap Verification\n\nConfirm each checkpoint:\n\n- `vercel whoami` succeeds.\n- `.vercel\u002Fproject.json` exists and matches chosen project.\n- Postgres integration path completed (Vercel integration, dashboard, or provider CLI fallback).\n- `vercel env pull .env.local --yes` succeeds.\n- Required env key diff is empty.\n- Database command status is recorded (`db:push`, `db:seed`, `db:migrate`, `db:generate` as applicable).\n- `dev` command starts without immediate config\u002Fauth\u002Fenv failure.\n\nIf verification fails, stop and report exact failing step plus remediation.\n\n## Summary Format\n\nReturn a final bootstrap summary in this format:\n\n```md\n## Bootstrap Result\n- **Linked Project**: \u003Cteam>\u002F\u003Cproject>\n- **Resource Path**: vercel-integration-neon | dashboard-neon | neon-cli\n- **Env Keys**: \u003Ccount> required, \u003Ccount> present, \u003Ccount> missing\n- **Secrets**: AUTH_SECRET set in Vercel (value never shown)\n- **Migration Status**: not-run | success | failed (\u003Cstep>)\n- **Dev Result**: not-run | started | failed\n```\n\n## Bootstrap Next Steps\n\n- If env keys are still missing, add the missing keys in Vercel and re-run `vercel env pull .env.local --yes`.\n- If DB commands fail, fix connectivity\u002Fschema issues and re-run only the failed db step.\n- If `dev` fails, resolve runtime errors, then restart with your package manager's `run dev`.\n\n## next-forge Projects\n\nIf the project was scaffolded with `npx next-forge init` (detected by `pnpm-workspace.yaml` + `packages\u002Fauth` + `packages\u002Fdatabase` + `@repo\u002F*` imports):\n\n1. Env files are per-app (`apps\u002Fapp\u002F.env.local`, `apps\u002Fweb\u002F.env.local`, `apps\u002Fapi\u002F.env.local`) plus `packages\u002Fdatabase\u002F.env`.\n2. Run `pnpm migrate` (not `db:push`) — it runs `prisma format` + `prisma generate` + `prisma db push`.\n3. Minimum env vars: `DATABASE_URL`, `CLERK_SECRET_KEY`, `NEXT_PUBLIC_CLERK_PUBLISHABLE_KEY`, `NEXT_PUBLIC_APP_URL`, `NEXT_PUBLIC_WEB_URL`, `NEXT_PUBLIC_API_URL`.\n4. Optional services (Stripe, Resend, PostHog, etc.) can be skipped initially — but remove their `@repo\u002F*` imports from app `env.ts` files to avoid validation errors.\n5. Deploy as 3 separate Vercel projects with root directories `apps\u002Fapp`, `apps\u002Fapi`, `apps\u002Fweb`.\n\n=> skill: next-forge — Full next-forge monorepo guide\n",{"name":5,"metadata":24,"description":7},{"docs":25,"sitemap":28,"priority":29,"bashPatterns":30,"pathPatterns":37,"importPatterns":48},[26,27],"https:\u002F\u002Fvercel.com\u002Fdocs\u002Fgetting-started-with-vercel","https:\u002F\u002Fnextjs.org\u002Fdocs\u002Fgetting-started\u002Finstallation","https:\u002F\u002Fvercel.com\u002Fsitemap\u002Fdocs.xml",8,[31,32,33,34,35,36],"\\\\bcp\\\\s+\\\\.env\\\\.(?:example|sample|template)\\\\s+\\\\.env\\\\.local\\\\b","\\\\b(?:npm|pnpm|bun|yarn)\\\\s+run\\\\s+db:(?:push|seed|migrate|generate)\\\\b","\\\\b(?:npm|pnpm|bun|yarn)\\\\s+run\\\\s+dev\\\\b","\\\\bvercel\\\\s+link\\\\b","\\\\bvercel\\\\s+integration\\\\s+(?:add|install)\\\\b","\\\\bvercel\\\\s+env\\\\s+pull\\\\b",[38,39,40,41,42,43,44,45,46,47],".env.example",".env.sample",".env.template","README*","docs\u002F**\u002Fsetup*","package.json","drizzle.config.*","prisma\u002Fschema.prisma","auth.*","src\u002F**\u002Fauth.*",[49,50,51,52,53,54,55,56],"@neondatabase\u002Fserverless","drizzle-orm","@upstash\u002Fredis","@vercel\u002Fblob","@vercel\u002Fedge-config","next-auth","@auth\u002Fcore","better-auth","main","dde9a06ab10bce3fe52058c783826590231f7df3","plugins\u002F.tmp\u002Fplugins\u002Fplugins\u002Fvercel\u002Fskills\u002Fbootstrap","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":66,"prompt":76,"zipAvailable":77},[67,70,73],{"tool":68,"command":69},"npx","npx skills add wxdwu\u002Fnew-api --skill bootstrap",{"tool":71,"command":72},"bunx","bunx skills add wxdwu\u002Fnew-api --skill bootstrap",{"tool":74,"command":75},"pnpm","pnpm dlx skills add wxdwu\u002Fnew-api --skill bootstrap","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fwxdwu\u002Fnew-api\u002Fblob\u002Fmain\u002Fplugins\u002F.tmp\u002Fplugins\u002Fplugins\u002Fvercel\u002Fskills\u002Fbootstrap\u002FSKILL.md",true,[79],{"path":80,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":83,"sourceHtmlUrl":84},"agents\u002Fopenai.yaml","REFERENCE","参考文档",173,"https:\u002F\u002Fgithub.com\u002Fwxdwu\u002Fnew-api\u002Fblob\u002Fmain\u002Fplugins\u002F.tmp\u002Fplugins\u002Fplugins\u002Fvercel\u002Fskills\u002Fbootstrap\u002Fagents\u002Fopenai.yaml",[86,93,100,107,114,121],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"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":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":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"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":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":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"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":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":113,"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":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":120,"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":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":125,"categories":126,"keywords":127,"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",[],[]]