Skip to content
Business
Skill

/design-mcp-workflow

Design a Zoom MCP workflow for Claude. Use when deciding whether Zoom MCP fits a task, when planning tool-based AI workflows, or when separating MCP responsibilities from REST API responsibilities.

From plugin
knowledge-work-plugins
24k192 skills5 agents15 commands40 MCP
Install
$ npx -y skills add anthropics/knowledge-work-plugins --skill design-mcp-workflow --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/design-mcp-workflow

Context preview

The summary Claude sees to decide when to auto-load this skill.

Design a Zoom MCP workflow for Claude. Use when deciding whether Zoom MCP fits a task, when planning tool-based AI workflows, or when separating MCP responsibilities from REST API responsibilities.

SKILL.md

design-mcp-workflow.SKILL.md
name: design-mcp-workflow
description: Design a Zoom MCP workflow for Claude. Use when deciding whether Zoom MCP fits a task, when planning tool-based AI workflows, or when separating MCP responsibilities from REST API responsibilities.
user-invocable: false

Design MCP Workflow

Use this skill when the user wants Claude or another MCP-capable client to interact with Zoom via tool calls instead of only deterministic API code.

Covers

  • MCP fit assessment
  • REST API vs MCP boundaries
  • Hybrid architectures
  • Connector expectations
  • Whiteboard-specific MCP routing

Workflow

1. Decide whether the problem is agentic tooling, deterministic automation, or both. 2. Route MCP-only tasks to [zoom-mcp](../zoom-mcp/SKILL.md). 3. Route hybrid tasks to both [zoom-mcp](../zoom-mcp/SKILL.md) and [rest-api](../rest-api/SKILL.md). 4. If Whiteboard is central, route to [zoom-mcp/whiteboard](../zoom-mcp/whiteboard/SKILL.md). 5. Call out transport, auth, and client capability assumptions explicitly.

Common Mistakes

  • Using MCP for deterministic backend jobs that should stay in REST
  • Treating MCP as a replacement for all API design
  • Ignoring client transport support and auth requirements
Ships withknowledge-work-plugins

Plugins that turn Claude into a specialist for your role, team, and company. Built for Claude Cowork, also compatible with Claude Code.

Get the whole plugin

Other skills on knowledge-work-plugins.