Agent Skills
› anthropics/knowledge-work-plugins
› design-mcp-workflow
design-mcp-workflow
GitHub用于设计 Zoom MCP 工作流，评估任务是否适合使用 MCP 工具调用而非仅 REST API。涵盖边界划分、混合架构设计及路由策略，避免将确定性后端任务误用为 MCP。
Trigger Scenarios
决定 Zoom MCP 是否适合特定任务时
规划基于工具的 AI 工作流时
需要区分 MCP 职责与 REST API 职责时
Install
npx skills add anthropics/knowledge-work-plugins --skill design-mcp-workflow -g -y
SKILL.md
Frontmatter
{
"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
- Decide whether the problem is agentic tooling, deterministic automation, or both.
- Route MCP-only tasks to zoom-mcp.
- Route hybrid tasks to both zoom-mcp and rest-api.
- If Whiteboard is central, route to zoom-mcp/whiteboard.
- 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
Version History
- 6f13415 Current 2026-07-05 18:31
