CtrlK
BlogDocsLog inGet started
Tessl Logo

zoom-apps-sdk

Use when using Apps SDK.

52

Quality

57%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/zoom/skills/zoom-apps-sdk/SKILL.md
SKILL.md
Quality
Evals
Security

Zoom Apps SDK

Use this skill when the app runs inside the Zoom client. If the user only needs to embed a meeting in an external app, route to Meeting SDK instead.

Workflow

  1. Confirm the running context: meeting, webinar, main client, phone, collaborate mode, immersive mode, camera mode, or Layers API.
  2. Configure Marketplace app settings, allowed domains, redirect URIs, and in-client OAuth before implementing SDK calls.
  3. Initialize zoomSdk and gate features by capability and running context.
  4. Design client communication and data flow: frontend SDK calls, backend REST calls, in-client OAuth tokens, and webhook handoff.
  5. Implement advanced client features only after the base app loads reliably: Layers API, breakout rooms, guest mode, collaborate mode, or ZMail.
  6. Debug blank panels, domain allowlist issues, CSP, missing capabilities, running-context mismatch, and OAuth redirect problems independently.

References

  • Full preserved guide: references/full-guide.md
  • Architecture: concepts/architecture.md
  • Running contexts: concepts/running-contexts.md
  • Meeting SDK versus Zoom Apps: concepts/meeting-sdk-vs-zoom-apps.md
  • Layers API: references/layers-api.md
  • In-client OAuth: examples/in-client-oauth.md
  • Common issues: troubleshooting/common-issues.md
Repository
openai/plugins
Last updated
First committed

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.