AGENT SKILL

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
所属仓库
TanNhatCMS/jarvis
最近更新
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

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:

Reference samples:

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:

  1. concepts/architecture-and-lifecycle.md
  2. scenarios/high-level-scenarios.md
  3. examples/getting-started-pattern.md
  4. examples/multi-client-pattern.md
  5. references/rivet-reference-map.md
  6. references/versioning-and-compatibility.md
  7. references/samples-validation.md
  8. references/source-map.md
  9. references/environment-variables.md
  10. troubleshooting/common-issues.md
  11. RUNBOOK.md
  12. rivet-sdk.md

Common Lifecycle Pattern

  1. Choose modules and auth model per module (Client Credentials, User OAuth, S2S OAuth, Video SDK JWT).
  2. Instantiate client(s) with credentials, webhook secret, and per-module port.
  3. Register event handlers (webEventConsumer.event(...) or shortcuts).
  4. Implement API calls through client.endpoints.*.
  5. Start receiver(s) and expose webhook endpoint(s) (/zoom/events) to Zoom.
  6. Persist tokens/state for OAuth workloads and enforce signature verification.
  7. 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 videosdk module 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

Environment Variables

Operations

  • RUNBOOK.md - 5-minute preflight and debugging checklist.

04 同仓库更多 Skills

TanNhatCMS
TanNhatCMS/jarvis

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.

★ 0
TanNhatCMS
TanNhatCMS/jarvis

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.

★ 0
TanNhatCMS
TanNhatCMS/jarvis

test-driven-development

Use when implementing any feature or bugfix, before writing implementation code

★ 0
TanNhatCMS
TanNhatCMS/jarvis

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

★ 0
TanNhatCMS
TanNhatCMS/jarvis

requesting-code-review

Use when completing tasks, implementing major features, or before merging to verify work meets requirements

★ 0
TanNhatCMS
TanNhatCMS/jarvis

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).

★ 0