Create and manage Zoom meetings and access cloud recordings via the Zoom API. Use for queries like "create a Zoom meeting", "list my Zoom meetings", "show my Zoom recordings", or "schedule a meeting for tomorrow".
npx skills add https://github.com/glebis/claude-skills --skill zoom
Manage Zoom meetings and cloud recordings via the Zoom API.
Note: All times passed to create/update commands are interpreted as local time. The script auto-detects your timezone if not explicitly specified with --timezone.
This skill uses two authentication methods:
| Feature | Auth Type | Credentials File |
|---------|-----------|------------------|
| Meetings | Server-to-Server OAuth | ~/.zoom_credentials/credentials.json |
| Recordings | User OAuth (General App) | ~/.zoom_credentials/oauth_token.json |
Check status:
python3 scripts/zoom_meetings.py setup
meeting:read:meeting:adminmeeting:read:list_meetings:adminmeeting:write:meeting:adminuser:read:user:adminmkdir -p ~/.zoom_credentials
cat > ~/.zoom_credentials/credentials.json << 'EOF'
{
"account_id": "YOUR_ACCOUNT_ID",
"client_id": "YOUR_CLIENT_ID",
"client_secret": "YOUR_CLIENT_SECRET"
}
EOF
Server-to-Server apps cannot access cloud recordings. You need a separate General App:
http://localhost:8888/callbackcloud_recording:read:list_user_recordingscloud_recording:read:list_recording_files# Open this URL in browser (replace CLIENT_ID):
https://zoom.us/oauth/authorize?response_type=code&client_id=YOUR_CLIENT_ID&redirect_uri=http://localhost:8888/callback
# After authorizing, you'll be redirected to:
# http://localhost:8888/callback?code=AUTHORIZATION_CODE
# Exchange the code for tokens (replace values):
python3 -c "
import requests, json
resp = requests.post('https://zoom.us/oauth/token',
auth=('CLIENT_ID', 'CLIENT_SECRET'),
data={'grant_type': 'authorization_code', 'code': 'AUTH_CODE', 'redirect_uri': 'http://localhost:8888/callback'})
data = resp.json()
data['client_id'] = 'CLIENT_ID'
data['client_secret'] = 'CLIENT_SECRET'
data['expires_at'] = __import__('time').time() + data.get('expires_in', 3600)
with open(__import__('pathlib').Path.home() / '.zoom_credentials/oauth_token.json', 'w') as f:
json.dump(data, f, indent=2)
print('Saved!')
"
# Check setup
python3 scripts/zoom_meetings.py setup
# List upcoming meetings
python3 scripts/zoom_meetings.py list
# Create a meeting
python3 scripts/zoom_meetings.py create "Team Standup" --start "2025-01-15T10:00:00" --duration 30
# List recordings
python3 scripts/zoom_meetings.py recordings --start 2025-01-01
# List meetings
python3 scripts/zoom_meetings.py list # upcoming
python3 scripts/zoom_meetings.py list --type previous # past
python3 scripts/zoom_meetings.py list --limit 10 --json
# Get meeting details
python3 scripts/zoom_meetings.py get MEETING_ID
# Create meeting (times are treated as LOCAL time)
python3 scripts/zoom_meetings.py create "Topic" # instant
python3 scripts/zoom_meetings.py create "Topic" --start "2025-01-15T14:00:00" # scheduled (local time)
python3 scripts/zoom_meetings.py create "Topic" --duration 60 --timezone "Europe/Berlin"
python3 scripts/zoom_meetings.py create "Topic" --agenda "Discussion points" --waiting-room
python3 scripts/zoom_meetings.py create "Topic" --invite "[email protected]" # send invite
python3 scripts/zoom_meetings.py create "Topic" --invite "[email protected]" --invite "[email protected]" # multiple
# Update meeting
python3 scripts/zoom_meetings.py update MEETING_ID --topic "New Topic"
python3 scripts/zoom_meetings.py update MEETING_ID --start "2025-01-16T10:00:00"
# Delete meeting (requires meeting:delete:meeting:admin scope)
python3 scripts/zoom_meetings.py delete MEETING_ID
# List all recordings (default: last 30 days)
python3 scripts/zoom_meetings.py recordings
# With date range
python3 scripts/zoom_meetings.py recordings --start 2025-01-01 --end 2025-01-31
# Show download URLs
python3 scripts/zoom_meetings.py recordings --show-downloads
# Get specific meeting's recordings
python3 scripts/zoom_meetings.py recording MEETING_ID
# JSON output
python3 scripts/zoom_meetings.py recordings --json
# Zoom Meetings (3 upcoming)
## Weekly Team Sync
**ID:** 123456789
**Start:** 2025-01-15 14:00:00 UTC
**Duration:** 60 minutes
**Join URL:** https://zoom.us/j/123456789
Add --json for structured output suitable for piping to other tools.
| Type | Description |
|------|-------------|
| MP4 | Video recording |
| M4A | Audio only |
| TRANSCRIPT | Text transcript (VTT) |
| CHAT | Chat messages |
| TIMELINE | Speaker timeline |
| SUMMARY | AI meeting summary |
| User says | Command |
|-----------|---------|
| "List my Zoom meetings" | list |
| "Show past meetings" | list --type previous |
| "Create a meeting for tomorrow at 2pm" | create "Meeting" --start "2025-01-15T14:00:00" |
| "Show my Zoom recordings" | recordings --start 2025-01-01 |
| "Get the recording for meeting X" | recording MEETING_ID |
pip install requests
| File | Purpose |
|------|---------|
| ~/.zoom_credentials/credentials.json | S2S OAuth credentials |
| ~/.zoom_credentials/token.json | S2S cached token |
| ~/.zoom_credentials/oauth_token.json | User OAuth tokens (auto-refreshes) |
join_before_host is account-level. This setting is locked at the Zoom account admin level. Setting it via API per-meeting is silently ignored if the account setting overrides it. Must change in Zoom admin settings (Security → "Allow participants to join before host") first, then API calls respect it.join_before_host won't work even if the API accepts it.Interactive daily standup/meeting update generator. Use when user says 'daily', 'standup', 'scrum update', 'status update', 'what did I do yesterday', 'prepare for meeting', 'morning update', or 'team sync'. Pulls activity from GitHub, Jira, and Claude Code session history. Conducts 4-question interview (yesterday, today, blockers, discussion topics) and generates formatted Markdown update.
Start your day with a prioritized sales briefing. Works standalone when you tell me your meetings and priorities, supercharged when you connect your calendar, CRM, and email. Trigger with "morning briefing", "daily brief", "what's on my plate today", "prep my day", or "start my day".
Full ICP-to-leads pipeline. Describe your ideal customer in plain English and get a ranked table of enriched decision-maker leads with emails and phone numbers.
Analyze meeting notes to find action items and create Jira tasks for assigned work. When an agent needs to: (1) Create Jira tasks or tickets from meeting notes, (2) Extract or find action items from notes or Confluence pages, (3) Parse meeting notes for assigned tasks, or (4) Analyze notes and generate tasks for team members. Identifies assignees, looks up account IDs, and creates tasks with proper context.
When the user wants to optimize post-signup onboarding, user activation, first-run experience, or time-to-value. Also use when the user mentions "onboarding flow," "activation rate," "user activation," "first-run experience," "empty states," "onboarding checklist," "aha moment," or "new user experience." For signup/registration optimization, see signup-flow-cro. For ongoing email sequences, see email-sequence.
Prepare for tomorrow''s meetings and tasks. Pulls calendar from Outlook via WorkIQ, cross-references open tasks and workspace context, classifies meetings, detects conflicts and day-fit issues, finds learning and deep-work slots, and generates a structured HTML prep file with productivity recommendations.
Design meeting rhythms, metric reporting, quarterly planning, and decision-making velocity for scaling companies. Use when decisions are slow, planning is broken, the company is growing but alignment is worse, or leadership meetings consume all time without producing decisions.
Add Google Calendar as an MCP tool (list calendars, list/search/create events, free/busy queries) using OneCLI-managed OAuth. Multi-calendar and multi-account supported. Mirrors /add-gmail-tool's stub pattern — no raw credentials ever reach the container; OneCLI injects real tokens at request time.
Take glebis/zoom from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.
The instructions reference pip.
Without those the skill loads but fails at the first command.