Plan Zoom Product

anthropics/knowledge-work-plugins/partner-built/zoom-plugin/skills/plan-zoom-product

作者 anthropicsae1513ea94dc無授權條款36K 個星標收錄於 2026年11月20日更新於 2026年11月20日儲存庫今天更新

Choose the right Zoom building surface for a use case and explain the tradeoffs clearly. Use when deciding between REST API, Webhooks, WebSockets, Meeting SDK, Video SDK, Zoom Apps SDK, Phone, Contact Center, or MCP for a specific product idea or integration goal.

AI 產生的概覽

針對具體產品構想,推薦合適的 Zoom 建構方式(REST API、Webhooks、各類 SDK、Phone、MCP)並說明取捨。

功能
接收產品構想、應用程式類型或整合目標,先判斷問題屬於自動化、嵌入式會議、自訂視訊、用戶端內應用行為、事件推送、AI 工具,還是客服/電話/聯絡中心情境。接著提出首選的 Zoom 建構介面及所需的最少配套元件,說明為何其他替代方案較不適合,並以具體的下一步計畫作結。輸出包含建議方案、所需元件、關鍵取捨與限制、實作順序,以及相關技能連結。
適用情境
當需要針對某個產品構想或整合目標,在 Zoom REST API、Webhooks、WebSockets、Meeting SDK、Video SDK、Zoom Apps SDK、Phone、Contact Center 或 MCP 之間做選擇時使用。也適用於需要為 Zoom 整合方案提出有依據的架構選擇與後續步驟時。
執行需求
僅為指令,不含腳本。可能引用 CONNECTORS.md 以確認已連接哪些工具。

/plan-zoom-product

If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.

Choose between Zoom REST API, Webhooks, WebSockets, Meeting SDK, Video SDK, Zoom Apps SDK, Phone, Contact Center, or MCP for a specific use case.

Usage

text
/plan-zoom-product $ARGUMENTS

Workflow

  1. Identify the user's actual goal.
  2. Classify whether the problem is automation, embedded meetings, custom video, in-client app behavior, event delivery, AI tooling, or support/phone/contact-center work.
  3. If the request is ambiguous, ask one short clarifier before locking the recommendation.
  4. Recommend the primary Zoom surface and list the minimum supporting pieces.
  5. Explain why the rejected alternatives are worse for this case.
  6. End with a concrete next-step plan.

Output

  • Recommended Zoom surface
  • Supporting components required
  • Key tradeoffs and constraints
  • Suggested implementation sequence
  • Relevant skill links for the next step

Related Skills

  • start
  • choose-zoom-approach
  • design-mcp-workflow

來源與署名

來源:anthropics/knowledge-work-plugins位於partner-built/zoom-plugin/skills/plan-zoom-product提交ae1513e

授權條款: 無授權條款

內容歸原作者所有。SourceWeft 從公開儲存庫中收錄這些內容。

在 README 中新增徽章

向讀者展示該技能已收錄於 SourceWeft,徽章連結到本頁。

「Listed on SourceWeft」徽章預覽
[![Listed on SourceWeft](https://sourceweft.com/badge/skills/gh-anthropics-knowledge-work-plugins-plan-zoom-product.svg)](https://sourceweft.com/skills/gh-anthropics-knowledge-work-plugins-plan-zoom-product?utm_source=readme&utm_medium=badge)

檢舉或申請下架

更多來自 anthropics/knowledge-work-plugins 的技能

Account Research

anthropics

精選

Research a target company and optionally a specific contact - company overview, recent news, likely priorities, and fit against your ICP. Cross-references existing CRM records. Use when the user asks to "research [company]", "look into [company]", "prospect research on [company]", "look up [person]", "intel on [prospect]", "who is [person] at [company]", or "tell me about [company]" when the company is a prospect rather than an existing account.

研究與分析36K今天更新

已新增到 1 個工作區

Competitive Brief

anthropics

精選

產出競爭分析簡報,涵蓋競品定位、功能比較、贏單/輸單模式與市場趨勢。

商業與財務36K今天更新

已新增到 1 個工作區

Synthesize Research

anthropics

精選

將訪談紀錄、問卷與回饋綜整為結構化的研究發現、主題與建議。

研究與分析36K今天更新

已新增到 1 個工作區

Competitive Intelligence

anthropics

精選

Competitive analysis two ways - the in-deal play against a named competitor, and win/loss patterns, competitor mentions, and battlecards across the book. Use when the user asks "competitive intel", "research competitors", "how do we compare to [competitor]", "what's new with [competitor]", "battlecard for [competitor]", "how do we beat [competitor]", "what's the play against [competitor] in [deal]", "where are we losing to [competitor]", "win/loss patterns", "competitive analysis", "refresh the battlecards", or on a weekly schedule.

研究與分析36K今天更新

已新增到 1 個工作區

Weekly Prep Brief

anthropics

精選

為未來一週的外部客戶與潛在客戶通話產生每週簡報,包含每場會議的公司與聯絡人研究。

效率與工作流36K今天更新

已新增到 1 個工作區

Contact Research

anthropics

精選

從 Common Room 資料研究某個人的聯絡人檔案,並產出帶有互動訊號的結構化檔案。

研究與分析36K今天更新

已新增到 1 個工作區