Plan Zoom Product in Codex: Choose the APIs for a Meeting Report
Work from a product requirement to the Zoom surface it needs. Use the planning command to pick a primary integration and the minimum supporting pieces.
中文Setup for Codex (Zoom plugin)
Codex with the Zoom plugin. A planning-only example can use a written scenario. An authenticated development account is relevant once you implement and test provider calls.
- Open /plugins in Codex and install Zoom when available in your marketplace.
- From a project session, choose /plan-zoom-product or explicitly select its bundled skill.
- Describe the audience, what triggers the feature, and the information it must show. Ask for a primary surface and the smallest useful prototype.
Example task
Use /plan-zoom-product for a fictional university that wants a daily aggregate report of yesterday’s Zoom workshops. It needs totals only and accepts a scheduled delay. Compare a scheduled API read with real-time event delivery, recommend a primary surface, and give one prototype acceptance check. Use written example data for the plan.Expected result
The plan recommends a scheduled REST API read if the demo account has the required reporting access, since the report is daily. It identifies the reporting fields and timestamp boundary to verify and suggests checking one day against a known fixture.
Upstream documentation
Original SKILL.md on GitHub · MIT license · Source reviewed
Frequently asked question
When would a daily report need Zoom events as well?
Consider event delivery if the report also needs to trigger a response immediately when a workshop ends. Keep the aggregation routine separate so it can handle delayed events and give a stable daily total.