Zoom Apps SDK in Codex for an In-Client Capability Check
Plan a Zoom App that opens inside the client, initializes the Apps SDK, and checks available capabilities before displaying an optional feature.
中文Setup for Codex (Zoom plugin)
Use a scratch web project and the Zoom plugin. A real in-client check needs a Zoom test app, approved development domain, and installation in a test client.
- In Codex, open /plugins and install Zoom. Use the full plugin package so its sibling skills and references are available.
- Invoke the bundled skill as $zoom-apps-sdk in a scratch workspace. Keep the example on the local or demo inputs described below.
Example task
Ask $zoom-apps-sdk to design a component for meeting context using a mock return value containing supportedApis=['getRunningContext'] and context='inMeeting'. Render a static agenda. Keep the optional Layers button hidden unless its capability appears.Expected result
The agenda remains visible in the mock meeting context, the optional button is hidden, and the plan specifies testing with the developer app inside the Zoom client.
Upstream documentation
Original SKILL.md on GitHub · MIT license · Source reviewed
Frequently asked question
Can a standalone browser prove that a Zoom App initialized?
It can verify your screen and fallback states. Confirm actual Apps SDK initialization and running context from the development app inside the Zoom client.