virtual-agent/ios
Zoom Virtual Agent iOS integration via WKWebView. Use for Swift/Objective-C script injection, message handlers, support_handoff relay, and URL routing policies.
- License 许可
- MIT
- 最近更新
- 2026-11-07
- Stars
- ★ 0
- Forks
- 1
01 前言 Front Matter
- name
- virtual-agent/ios
- triggers
- [ "virtual agent ios", "wkwebview zva", "support_handoff ios", "zoomCampaignSdk:ready ios", "wkusercontentcontroller" ]
- description
- Zoom Virtual Agent iOS integration via WKWebView. Use for Swift/Objective-C script injection, message handlers, support_handoff relay, and URL routing policies.
- user-invocable
- false
02 资源文件 4
- 参考文档concepts/webview-lifecycle.md451 B
- 参考文档examples/js-bridge-patterns.md936 B
- 参考文档references/ios-reference-map.md641 B
- 参考文档troubleshooting/common-issues.md583 B
03 SKILL.md 正文
Zoom Virtual Agent - iOS
Official docs:
Quick Links
- concepts/webview-lifecycle.md
- examples/js-bridge-patterns.md
- references/ios-reference-map.md
- troubleshooting/common-issues.md
Integration Model
- Load campaign URL in
WKWebView. - Inject
window.zoomCampaignSdkConfigusingWKUserScript. - Register message handlers for exit/common/handoff flows.
- Handle URL behavior in navigation delegates (
in-app,SFSafariViewController, or system browser).
Hard Guardrails
- Register scripts and handlers before web interaction.
- Handle iOS 14.5+ download behavior where needed.
- Keep deprecated
openURLcommand support as fallback only.
Chaining
- Product-level patterns: ../SKILL.md
- Contact Center mobile scope: ../../contact-center/ios/SKILL.md
04 同仓库更多 Skills
web-scrape
Turn web pages into LLM-ready markdown via the Firecrawl API (renders JS, anti-bot handling). Use when browser_open/fetch fails on JS-heavy pages, or when you need clean markdown/structured extraction from a site. Requires FIRECRAWL_API_KEY.
design-taste-frontend
tasteskill v2, the anti-slop frontend skill. Art direction for websites, distilled from a study of 247 curated gallery sites (One Page Love, Awwwards Sites of the Day). Deals researched directions (idea, composition, type, palette, photographs, section blueprints) from a library, enforces a strict no-slop house style with a real-browser inspector, and runs a look-and-fix loop on screenshots. Use this whenever you build, design, redesign, restyle, polish or review a landing page, marketing site, portfolio, product page, one-pager, hero or any public-facing web page, in any stack (HTML/CSS, React, Next.js, Vue, Svelte, Astro, Tailwind) — also when the user says a page looks generic, templated, "AI-made", sloppy, or asks to make it look designed, premium, award-level or less like every other site. Not for dashboards or app screens.
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
requesting-code-review
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).