rivet-sdk
Reference skill for Zoom Rivet SDK. Use after routing to a Rivet-based server workflow when implementing auth handling, webhook consumers, API wrappers, multi-module composition, or Lambda receiver patterns.
- License 许可
- MIT
- 最近更新
- 2026-11-07
- Stars
- ★ 0
- Forks
- 1
01 前言 Front Matter
- name
- rivet-sdk
- triggers
- [ "rivet", "zoom rivet", "@zoom/rivet", "rivet javascript", "rivet sdk", "rivet webhook", "rivet oauth", "rivet lambda", "rivet team chat", "rivet chatbot" ]
- description
- Reference skill for Zoom Rivet SDK. Use after routing to a Rivet-based server workflow when implementing auth handling, webhook consumers, API wrappers, multi-module composition, or Lambda receiver patterns.
- user-invocable
- false
02 资源文件 13
- 参考文档concepts/architecture-and-lifecycle.md3.3 KB
- 参考文档CONNECTORS.md2.4 KB
- 参考文档examples/getting-started-pattern.md1.3 KB
- 参考文档examples/multi-client-pattern.md1.7 KB
- 参考文档references/environment-variables.md2.2 KB
- 参考文档references/rivet-reference-map.md1.1 KB
- 参考文档references/samples-validation.md1.7 KB
- 参考文档references/source-map.md893 B
- 参考文档references/versioning-and-compatibility.md1.2 KB
- 参考文档rivet-sdk.md614 B
- 参考文档RUNBOOK.md2.7 KB
- 参考文档scenarios/high-level-scenarios.md2.0 KB
- 参考文档troubleshooting/common-issues.md1.4 KB
03 SKILL.md 正文
<!-- Provenance: adapted from anthropics/knowledge-work-plugins (Apache-2.0, (c) Anthropic). Original skill: https://github.com/anthropics/knowledge-work-plugins/tree/main/partner-built/zoom-plugin/skills/rivet-sdk. Changes for Muse AI: Claude/Cowork product refs -> Muse AI; MCP -> connector; CLAUDE.md -> MUSE.md; ${CLAUDE_PLUGIN_ROOT} -> this skill's directory; /plugin:command refs -> skill refs. -->
Zoom Rivet SDK
Background reference for Zoom Rivet as a JavaScript and TypeScript server framework for Zoom integrations.
Implementation guidance for Zoom Rivet (JavaScript/TypeScript) as a server-side framework for:
- OAuth and token handling
- Webhook event consumption
- Typed REST API endpoint wrappers
- Multi-module server composition
Official docs:
- https://developers.zoom.us/docs/rivet/
- https://developers.zoom.us/docs/rivet/javascript/
- https://zoom.github.io/rivet-javascript/
Reference samples:
- https://github.com/zoom/rivet-javascript-sample
- https://github.com/zoom/isv-rivet-starter
- https://github.com/zoom/Rivet-Server-Sample
- https://github.com/zoom/rivet-javascript
Routing Guardrail
- Rivet SDK is a Node.js framework that bundles Zoom auth handling, webhook receivers, and typed API wrappers.
- Rivet is recommended for faster server-side scaffolding, but it is not mandatory.
- At planning start, confirm preference:
Do you want Rivet SDK, or direct OAuth + REST without Rivet?- Use Rivet when the user wants a Node.js server that combines Zoom auth + webhooks + API calls with minimal glue code.
- If the user only needs direct API calls from an existing backend, chain with ../rest-api/SKILL.md.
- If the user is focused on Zoom Team Chat app cards/commands behavior, chain with ../team-chat/SKILL.md.
- If the user needs SDK embed (Meeting SDK/Video SDK client runtime), route to ../meeting-sdk/SKILL.md or ../video-sdk/SKILL.md.
Quick Links
Start here:
- concepts/architecture-and-lifecycle.md
- scenarios/high-level-scenarios.md
- examples/getting-started-pattern.md
- examples/multi-client-pattern.md
- references/rivet-reference-map.md
- references/versioning-and-compatibility.md
- references/samples-validation.md
- references/source-map.md
- references/environment-variables.md
- troubleshooting/common-issues.md
- RUNBOOK.md
- rivet-sdk.md
Common Lifecycle Pattern
- Choose modules and auth model per module (Client Credentials, User OAuth, S2S OAuth, Video SDK JWT).
- Instantiate client(s) with credentials, webhook secret, and per-module port.
- Register event handlers (
webEventConsumer.event(...)or shortcuts). - Implement API calls through
client.endpoints.*. - Start receiver(s) and expose webhook endpoint(s) (
/zoom/events) to Zoom. - Persist tokens/state for OAuth workloads and enforce signature verification.
- Monitor module-specific failures and rotate secrets/version with changelog cadence.
High-Level Scenarios
- Team Chat slash-command bot + Team Chat data API enrichment.
- Multi-module backend (Users + Meetings + Team Chat + Phone) sharing one process.
- Video SDK telemetry backend using
videosdkmodule event stream + API surfaces. - ISV orchestration layer with tenant-aware token storage and per-module webhooks.
- AWS Lambda webhook processor with Rivet
AwsLambdaReceiver.
See scenarios/high-level-scenarios.md for details.
Chaining
- OAuth architecture and grant selection: ../oauth/SKILL.md
- API endpoint semantics and request payload details: ../rest-api/SKILL.md
- Team Chat app cards, command and bot UX: ../team-chat/SKILL.md
- Video SDK API-specific behavior and BYOS context: ../video-sdk/SKILL.md
Environment Variables
- See references/environment-variables.md for standardized
.envkeys and where to find each value.
Operations
- RUNBOOK.md - 5-minute preflight and debugging checklist.
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).