From zoom-suite
Zoom-powered meeting prep — pulls your full history with a person or company from Zoom (prior meeting summaries, open action items, unresolved follow-ups), combines it with web research, and builds a complete pre-meeting intelligence brief: context on prior conversations, talking points, an agenda, anticipated objections, and a follow-up template ready to send. Knows what happened last time — without you having to remember. Triggers on: "prep for my meeting with [name]", "meeting prep", "brief me before my call with [name]", "I have a call with [company]", "what should I know before I meet with [name]", "build an agenda for [topic]", "call prep", "prepare talking points", "research [person] before our meeting".
How this skill is triggered — by the user, by Claude, or both
Slash command
/zoom-suite:comm-zoom-prepThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
> **Requires:** Zoom MCP connector for meeting history lookup. Web search for external research.
Requires: Zoom MCP connector for meeting history lookup. Web search for external research.
Meeting prep that actually knows what happened before. This skill searches the user's Zoom meeting history for all prior interactions with a person or company, pulls the summaries and open items from those calls, and combines that institutional memory with web research to build a complete pre-meeting brief. The result: the user walks in knowing what was discussed last time, what was promised, what's still unresolved — plus fresh intelligence on the person or company.
Search Cloud Brain using mcp__cloud-brain__search_notes with query: "meeting prep preferences".
If preferences ARE found: Confirm in one line: "Using your saved preferences — [name], [role/business context]."
If NOT found: Collect before proceeding:
Save to brain/preferences/meeting-prep-preferences.md.
Extract from the user's request:
If any of these are unclear, ask before proceeding. A one-question clarification is fine — don't interrogate.
Also ask: "What timezone are you in?" (required for Zoom meeting search).
Look up all prior Zoom meetings with this person or company.
Search 1 — by person's name:
Call mcp__zoom__search_meetings with:
q: the person's name or company namefrom: 1 year ago (to capture substantial history)Search 2 — by topic keywords (if applicable): If the meeting topic is distinctive, run a second search with those keywords to catch related meetings the person wasn't in the topic field for.
For each matching meeting found (up to 5 most recent):
Call mcp__zoom__get_meeting_assets with the meeting_uuid to get:
Extract from each past meeting:
Search Cloud Brain for any saved notes about this person or company:
mcp__cloud-brain__search_notes with the person's namemcp__cloud-brain__search_notes with the company nameIf notes exist (mcp__cloud-brain__read_note), extract:
Web research — use WebSearch and WebFetch:
For the person:
For the company:
Research depth should match meeting type:
Compile everything into a single document the user can read in 5 minutes before the meeting.
# Meeting Brief: [Meeting Topic]
**With:** [Person Name] — [Title], [Company]
**Date:** [Date/Time]
**Type:** [Meeting type]
**Goal:** [What the user wants to walk away with]
---
## Prior Meeting History (from Zoom)
[If no prior meetings: "This is your first recorded meeting with [Name]."]
### [Meeting Topic] — [Date]
- **What happened:** [1–2 sentence summary]
- **What was decided/committed:** [Key outcomes]
- **Open items from that meeting:** [Anything that was supposed to happen but outcome unknown]
### [Meeting Topic 2] — [Date]
- ...
**⚠️ Open items to address this meeting:**
- [Item 1 that was unresolved from a prior meeting]
- [Item 2]
---
## About [Person Name]
- **Role:** [Title, Company, tenure if known]
- **Background:** [1–2 sentences on who they are professionally]
- **Recent activity:** [Latest news, posts, or public moves relevant to this meeting]
## About [Company]
- **What they do:** [1–2 sentence description]
- **Recent news:** [Most relevant news item and why it matters for this meeting]
- **Size / stage:** [Relevant context]
---
## Your Agenda (Suggested)
| Time | Topic | Purpose |
|------|-------|---------|
| 0–2 min | Opening / small talk | Build rapport |
| 2–5 min | [Agenda Item 1] | [Goal] |
| 5–15 min | [Agenda Item 2] | [Goal] |
| 15–25 min | [Agenda Item 3] | [Goal] |
| 25–28 min | Next steps | Confirm commitments |
| 28–30 min | Close | |
---
## Talking Points
### Opening
- [Relevant opener based on recent news or last meeting context]
- [Reference to something from prior meeting to show you remember]
### [Topic 1]
- [Key point to make, with supporting evidence or data if available]
- [Anticipated response from them]
### [Topic 2]
- [Key point]
---
## Anticipated Objections / Difficult Questions
| They might say... | Your response |
|---|---|
| "[Likely objection 1]" | [Prepared response] |
| "[Likely objection 2]" | [Prepared response] |
---
## Open Loops to Close
[Items from prior meetings that need to be addressed or confirmed in this meeting]
- [ ] [Open item 1]
- [ ] [Open item 2]
---
## Follow-Up Template (Ready to Send After the Meeting)
> Subject: Great connecting — [Topic/Next Steps]
>
> Hi [Name],
>
> Thanks for [taking the time / the conversation] today. As discussed:
>
> - [Key decision or commitment 1]
> - [Key decision or commitment 2]
>
> My next step is [user action]. I'll [follow up / send over / have that to you] by [date].
>
> [Call to action if applicable]
>
> Best,
> [User Name]
---
*Prepared by COMM-zoom-prep. Zoom history: [N] prior meetings found.*
Save the completed brief:
mcp__cloud-brain__write_notebrain/meeting-prep/[slug]-[YYYY-MM-DD].mdAlso update (or create) the person's contact note in the brain:
brain/contacts/[person-name].mdDeliver the brief and offer a quick coaching check:
"Your meeting brief is ready. Anything specific you want to workshop before the call — an objection script, a specific talking point, or how to open?"
Guides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.
npx claudepluginhub owenmecham/mbg --plugin zoom-suite