Helps you figure out when to use Zoom's MCP server versus their REST API, or both. If you're building agentic workflows where Claude needs to call Zoom tools, this walks through fit assessment and routing decisions. It explicitly separates deterministic automation (stay in REST) from interactive tool use (go MCP), which matters because a lot of people treat MCP as a blanket API replacement when it's really for dynamic, conversational tasks. The workflow is simple: assess the problem, route to the right skill, call out auth and transport assumptions. Honest take: this is meta tooling, so it's most useful if you're already familiar with MCP concepts and just need the decision tree.
npx skills add https://github.com/anthropics/knowledge-work-plugins --skill design-mcp-workflow