/zoom-setup
Connect Zoom for meeting recordings, scheduling and transcript context. Use when the user says 'connect Zoom', 'pull my Zoom recordings'. Not for Granola-sourced notes; use `granola-setup`. Not for Teams; use `ms-teams-setup`.
$ npx -y skills add davekilleen/Dex --skill zoom-setup --agent claude-codeHow 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
/zoom-setup
Context preview
The summary Claude sees to decide when to auto-load this skill.
Connect Zoom for meeting recordings, scheduling and transcript context. Use when the user says 'connect Zoom', 'pull my Zoom recordings'. Not for Granola-sourced notes; use `granola-setup`. Not for Teams; use `ms-teams-setup`.
SKILL.md
zoom-setup.SKILL.mdname: zoom-setup
description: "Connect Zoom for meeting recordings, scheduling and transcript context. Use when the user says 'connect Zoom', 'pull my Zoom recordings'. Not for Granola-sourced notes; use `granola-setup`. Not for Teams; use `ms-teams-setup`."
integration:
id: zoom
name: Zoom
mcp_server: zoom-mcp
auth: oauth2
category: meetings
sync_direction: bidirectional
enhances:
- skill: meeting-prep
capability: "Shows last Zoom with each attendee, surfaces recording summaries"
- skill: process-meetings
capability: "Zoom recordings as alternative meeting source alongside Granola"
- skill: week-review
capability: "Meeting time stats from Zoom (hours, count, distribution)"
new_capabilities:
- name: Recording Search
trigger: "During /meeting-prep, search Zoom recordings for past meetings with attendees"
- name: Zoom Scheduling
trigger: "Schedule Zoom meetings directly from Dex with confirmation"Zoom Setup
Connect your Zoom account to Dex so your meeting prep, reviews, and process-meetings workflows get direct access to Zoom recordings, transcripts, and scheduling.
What This Enables
Once connected, Dex can:
**Read:**
- List recordings and transcripts from past meetings
- Search meeting content by keyword or participant
- Get participant lists and meeting metadata
- Pull meeting summaries and action items from recordings
**Write (always with your confirmation):**
- Schedule Zoom meetings (Dex will always confirm before creating)
- Add meeting notes or summaries to Zoom
**Skill Enhancements:**
- **Meeting Prep** (`/meeting-prep`) shows: "Your last Zoom with Sarah: Jan 15. Recording summary available."
- **Process Meetings** (`/process-meetings`) can process Zoom recordings directly as an alternative to Granola
- **Week Review** (`/week-review`) includes meeting time stats from Zoom
**New Capabilities:**
- **Recording Search:** During `/meeting-prep`, search Zoom recordings for past meetings with attendees and surface summaries
Privacy
Dex accesses your Zoom account to read recordings and schedule meetings. No recordings are stored locally. Recordings are fetched, summarized, and discarded after the session. Only YOUR account is accessible (scoped to your OAuth login). The OAuth token stays local on your machine and is gitignored.
When to Run
- User types `/zoom-setup`
- User asks about connecting Zoom
- User wants Zoom recording context in meeting prep
- During `/integrate-mcp` if Zoom is mentioned
---
Setup Flow
Step 1: Check if Already Connected
1. Check `System/integrations/config.yaml` for `zoom.enabled: true` 2. If enabled, try a test query via Zoom MCP (e.g., list recent recordings) 3. If healthy and responding, skip to **Step 5** (Configure Preferences) 4. If the tool is not available or errors, continue to Step 2
Step 2: Smart Granola Detection
Before explaining the full setup, check if Granola is already connected:
1. Read `System/integrations/config.yaml` for a `granola` section 2. Check if Granola MCP tools are available (try `granola_check_available()`)
**If Granola IS connected:**
You already have Granola connected -- it captures your Zoom meetings automatically.
Zoom integration would add:
- Meeting scheduling directly from Dex
- Access to Zoom cloud recordings (if Granola misses one)
- Participant metadata (invited vs. attended)
Still want to connect? [Yes / Skip for now]
If user says "Skip for now", confirm and exit: > "No problem. Granola has your meeting capture covered. Run `/zoom-setup` anytime if you want scheduling or recording access later."
**If user says "Yes" (Granola connected), continue with adjusted messaging:**
**Let's connect Zoom to Dex.**
Since Granola handles meeting capture, Zoom adds scheduling and direct recording access.
**What you'll need:**
- A Zoom account (Pro or higher for cloud recordings)
- About 3 minutes for the OAuth flow
**Ready to go?**
**If Granola is NOT connected:**
**Let's connect Zoom to Dex.**
This gives Dex access to your Zoom recordings, transcripts, and scheduling.
**What you'll need:**
- A Zoom account (Pro or higher for cloud recordings)
- About 3 minutes for the OAuth flow
**What Dex will be able to do:**
- Access your Zoom recordings and transcripts
- Search meeting content by keyword or participant
- Schedule Zoom meetings (with your confirmation)
- Enrich meeting prep with recording summaries
**Ready to go?**
Wait for confirmation.
Step 3: Add the Zoom MCP Server
Check the user's MCP configuration. If `zoom-mcp` is not listed:
1. Explain what we're adding:
I need to add the Zoom connector to your Dex configuration.
This uses an MCP bridge that connects to Zoom's APIs via OAuth.
Your credentials stay on your machine.
2. Add to the user's `.mcp.json` (use the `/dex-add-mcp` skill or manual edit):
{
"zoom-mcp": {
"command": "npx",
"args": ["-y", "zoom-mcp"],
"env": {}
}
}3. Tell the user the MCP server needs to restart for changes to take effect.
Step 4: Authenticate via OAuth
1. Run the Zoom MCP server -- this starts the OAuth flow 2. A browser window opens for Zoom sign-in 3. The user authorizes the requested scopes (recordings, meetings, users) 4. The token is saved locally
**If OAuth succeeds:**
Connected! I can see your Zoom account.
**If it fails:**
The OAuth flow didn't complete. A few things to check:
1. **Did the browser open?** If not, try copying the URL from the terminal output
2. **Did you approve all permissions?** Dex needs recording and meeting access
3. **Zoom Pro required?** Cloud recordings require a Pro (or higher) Zoom plan
4. **Corporate SSO?** Your Zoom admin may restrict OAuth apps
Want to retry?
Retry up to 2 times, then offer to skip and come back later.
Step 5: Configure Preferences
Once connected, determine feature defaults based on Granola status:
**Feature defaults
Read more
name: zoom-setup
description: "Connect Zoom for meeting recordings, scheduling and transcript context. Use when the user says 'connect Zoom', 'pull my Zoom recordings'. Not for Granola-sourced notes; use `granola-setup`. Not for Teams; use `ms-teams-setup`."
integration:
id: zoom
name: Zoom
mcp_server: zoom-mcp
auth: oauth2
category: meetings
sync_direction: bidirectional
enhances:
- skill: meeting-prep
capability: "Shows last Zoom with each attendee, surfaces recording summaries"
- skill: process-meetings
capability: "Zoom recordings as alternative meeting source alongside Granola"
- skill: week-review
capability: "Meeting time stats from Zoom (hours, count, distribution)"
new_capabilities:
- name: Recording Search
trigger: "During /meeting-prep, search Zoom recordings for past meetings with attendees"
- name: Zoom Scheduling
trigger: "Schedule Zoom meetings directly from Dex with confirmation"Zoom Setup
Connect your Zoom account to Dex so your meeting prep, reviews, and process-meetings workflows get direct access to Zoom recordings, transcripts, and scheduling.
What This Enables
Once connected, Dex can:
**Read:**
- List recordings and transcripts from past meetings
- Search meeting content by keyword or participant
- Get participant lists and meeting metadata
- Pull meeting summaries and action items from recordings
**Write (always with your confirmation):**
- Schedule Zoom meetings (Dex will always confirm before creating)
- Add meeting notes or summaries to Zoom
**Skill Enhancements:**
- **Meeting Prep** (`/meeting-prep`) shows: "Your last Zoom with Sarah: Jan 15. Recording summary available."
- **Process Meetings** (`/process-meetings`) can process Zoom recordings directly as an alternative to Granola
- **Week Review** (`/week-review`) includes meeting time stats from Zoom
**New Capabilities:**
- **Recording Search:** During `/meeting-prep`, search Zoom recordings for past meetings with attendees and surface summaries
Privacy
Dex accesses your Zoom account to read recordings and schedule meetings. No recordings are stored locally. Recordings are fetched, summarized, and discarded after the session. Only YOUR account is accessible (scoped to your OAuth login). The OAuth token stays local on your machine and is gitignored.
When to Run
- User types `/zoom-setup`
- User asks about connecting Zoom
- User wants Zoom recording context in meeting prep
- During `/integrate-mcp` if Zoom is mentioned
---
Setup Flow
Step 1: Check if Already Connected
1. Check `System/integrations/config.yaml` for `zoom.enabled: true` 2. If enabled, try a test query via Zoom MCP (e.g., list recent recordings) 3. If healthy and responding, skip to **Step 5** (Configure Preferences) 4. If the tool is not available or errors, continue to Step 2
Step 2: Smart Granola Detection
Before explaining the full setup, check if Granola is already connected:
1. Read `System/integrations/config.yaml` for a `granola` section 2. Check if Granola MCP tools are available (try `granola_check_available()`)
**If Granola IS connected:**
You already have Granola connected -- it captures your Zoom meetings automatically. Zoom integration would add: - Meeting scheduling directly from Dex - Access to Zoom cloud recordings (if Granola misses one) - Participant metadata (invited vs. attended) Still want to connect? [Yes / Skip for now]
If user says "Skip for now", confirm and exit: > "No problem. Granola has your meeting capture covered. Run `/zoom-setup` anytime if you want scheduling or recording access later."
**If user says "Yes" (Granola connected), continue with adjusted messaging:**
**Let's connect Zoom to Dex.** Since Granola handles meeting capture, Zoom adds scheduling and direct recording access. **What you'll need:** - A Zoom account (Pro or higher for cloud recordings) - About 3 minutes for the OAuth flow **Ready to go?**
**If Granola is NOT connected:**
**Let's connect Zoom to Dex.** This gives Dex access to your Zoom recordings, transcripts, and scheduling. **What you'll need:** - A Zoom account (Pro or higher for cloud recordings) - About 3 minutes for the OAuth flow **What Dex will be able to do:** - Access your Zoom recordings and transcripts - Search meeting content by keyword or participant - Schedule Zoom meetings (with your confirmation) - Enrich meeting prep with recording summaries **Ready to go?**
Wait for confirmation.
Step 3: Add the Zoom MCP Server
Check the user's MCP configuration. If `zoom-mcp` is not listed:
1. Explain what we're adding:
I need to add the Zoom connector to your Dex configuration. This uses an MCP bridge that connects to Zoom's APIs via OAuth. Your credentials stay on your machine.
2. Add to the user's `.mcp.json` (use the `/dex-add-mcp` skill or manual edit):
{
"zoom-mcp": {
"command": "npx",
"args": ["-y", "zoom-mcp"],
"env": {}
}
}3. Tell the user the MCP server needs to restart for changes to take effect.
Step 4: Authenticate via OAuth
1. Run the Zoom MCP server -- this starts the OAuth flow 2. A browser window opens for Zoom sign-in 3. The user authorizes the requested scopes (recordings, meetings, users) 4. The token is saved locally
**If OAuth succeeds:**
Connected! I can see your Zoom account.
**If it fails:**
The OAuth flow didn't complete. A few things to check: 1. **Did the browser open?** If not, try copying the URL from the terminal output 2. **Did you approve all permissions?** Dex needs recording and meeting access 3. **Zoom Pro required?** Cloud recordings require a Pro (or higher) Zoom plan 4. **Corporate SSO?** Your Zoom admin may restrict OAuth apps Want to retry?
Retry up to 2 times, then offer to skip and come back later.
Step 5: Configure Preferences
Once connected, determine feature defaults based on Granola status:
**Feature defaults
A personal operating system powered by Claude. Strategic work management, meeting intelligence, relationship tracking, daily planning — all configured for your specific role. No coding required.
Repo: davekilleen/Dex
Other skills on davekilleen-dex.
- /agent-browser
Browser automation using Vercel's agent-browser CLI. Use when you need to interact with web pages, fill forms, take screenshots, or scrape data. Alternative to Playwright MCP - uses Bash commands with ref-based element selection. Triggers on "browse website", "fill form", "click
Open skill - /agent-native-architecture
Build applications where agents are first-class citizens. Use this skill when designing autonomous agents, creating MCP tools, implementing self-modifying systems, or building apps where features are outcomes achieved by agents operating in a loop.
Open skill - /andrew-kane-gem-writer
This skill should be used when writing Ruby gems following Andrew Kane's proven patterns and philosophy. It applies when creating new Ruby gems, refactoring existing gems, designing gem APIs, or when clean, minimal, production-ready Ruby library code is needed. Triggers on
Open skill - /brainstorming
This skill should be used before implementing features, building components, or making changes. It guides exploring user intent, approaches, and design decisions before planning. Triggers on "let's brainstorm", "help me think through", "what should we build", "explore
Open skill - /compound-docs
Capture solved problems as categorized documentation with YAML frontmatter for fast lookup
Open skill - /create-agent-skills
Expert guidance for creating, writing, and refining Claude Code Skills. Use when working with SKILL.md files, authoring new skills, improving existing skills, or understanding skill structure and best practices.
Open skill

