zoom-meeting-sdk-electron
Zoom Meeting SDK for Electron desktop applications. Use when embedding Zoom meetings in an Electron app with the Node addon wrapper, JWT auth, join/start flows, settings controllers, and raw data integration.
- License 许可
- MIT
- 最近更新
- 2026-09-22
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- zoom-meeting-sdk-electron
- description
- Zoom Meeting SDK for Electron desktop applications. Use when embedding Zoom meetings in an Electron app with the Node addon wrapper, JWT auth, join/start flows, settings controllers, and raw data integration.
02 资源文件 14
- 参考文档agents/openai.yaml336 B
- 参考文档concepts/high-level-scenarios.md818 B
- 参考文档concepts/lifecycle-workflow.md937 B
- 参考文档concepts/sdk-architecture-pattern.md726 B
- 参考文档examples/authentication-pattern.md485 B
- 参考文档examples/join-meeting-pattern.md509 B
- 参考文档examples/raw-data-pattern.md561 B
- 参考文档examples/setup-guide.md771 B
- 参考文档references/electron-reference.md541 B
- 参考文档references/module-map.md765 B
- 参考文档RUNBOOK.md2.3 KB
- 参考文档troubleshooting/common-issues.md823 B
- 参考文档troubleshooting/deprecated-and-contradictions.md1.2 KB
- 参考文档troubleshooting/version-drift.md467 B
03 SKILL.md 正文
Zoom Meeting SDK (Electron)
Use this skill when building Electron desktop apps that embed Zoom Meeting SDK capabilities through the Electron wrapper.
Start Here
- Lifecycle Workflow - init -> auth -> join/start -> in-meeting -> cleanup
- SDK Architecture Pattern - service/controller/event model in Electron
- Setup Guide - dependency and build expectations
- Authentication Pattern - SDK JWT generation and auth callbacks
- Join Meeting Pattern - start/join meeting execution flow
- SKILL.md - full navigation
Core Notes
- Electron wrapper is built on top of native Meeting SDK with Node addon bridges.
- Keep SDK key/secret server-side; generate SDK JWT on backend.
- Feature support differs by platform/version; check module docs before implementation.
- Raw data and IPC patterns require explicit security hardening in production.
References
Related Skills
Merged from meeting-sdk/electron/SKILL.md
Zoom Meeting SDK Electron - Documentation Index
Start Here
Concepts
Examples
References
Troubleshooting
Operations
- RUNBOOK.md - 5-minute preflight and debugging checklist.
04 同仓库更多 Skills
skill-installer
Install Codex skills into $CODEX_HOME/skills from a curated list or a GitHub repo path. Use when a user asks to list installable skills, install a curated skill, or install a skill from another repo (including private repos).
skill-creator
Create or update a Codex skill with appropriately scoped instructions and any needed supporting resources.
review-agent
Perform a read-only, defect-first review of a specified code change and return every actionable finding. Use when another agent delegates review of uncommitted changes, a base-branch diff, a commit, or custom review instructions.
plugin-creator
Create and scaffold plugin directories for Codex with a required `.codex-plugin/plugin.json`, optional plugin folders/files, valid manifest defaults, and personal-marketplace entries by default. Use when Codex needs to create a new personal plugin, add optional plugin structure, generate or update marketplace entries for plugin ordering and availability metadata, or update an existing local plugin during development with the CLI-driven cachebuster and reinstall flow.
openai-docs
Use for Codex models/pricing, scheduled tasks, skills, settings, setup, troubleshooting, customization, automations, and self-knowledge—including 'you,' 'your,' 'this app,' or 'this coding agent' when they refer to Codex—and for OpenAI APIs/products and ChatGPT Work. Also use for model choice/migration, prompting, SDKs, Responses, Realtime, agents, evals, and Chat/Work/Codex comparisons. Do not use for generic app/software tasks that merely mention Codex.
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output should be a bitmap asset rather than repo-native code or vector. Do not use when the task is better handled by editing existing SVG/vector/code-native assets, extending an established icon or logo system, or building the visual directly in HTML/CSS/canvas.