zoom/SKILL.md
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 skillsauth add glebis/claude-skills zoomInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
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.development
Create Tufte-inspired data reports and infographic dashboards as standalone HTML files. Uses EB Garamond for text, Monaspace Argon for numbers, Chart.js for interactive charts, and inline SVG sparklines. Produces publication-quality reports with 2-column narrative+data layouts, status dashboards, scroll animations, and responsive mobile support. Use this skill whenever the user wants to create a data report, activity dashboard, infographic, personal analytics page, health tracker visualization, or any document that combines narrative text with interactive charts and tables. Also triggers for "make a report like Tufte", "create an infographic", "build a dashboard", "visualize my data", or requests for beautiful data-driven documents.
documentation
Cut a software release and maintain a tiered compatibility policy. Use when the user wants to release, ship a version, bump the version, tag a release, write a changelog, or update COMPATIBILITY. Config-driven via release.config.json; bumps version files, runs a readiness gate, updates COMPATIBILITY.md tiers and deprecations, tags (→ release workflow), and reports closed issues. Teaches the underlying standards as it runs.
development
Sync and manage bilingual (EN/RU) library content for agency-docs. Use when adding, updating, or reviewing library articles. Handles translation, sync checks, and Russian stylistic review.
development
This skill should be used to watch a long-running background job (ffmpeg/media encode, qmd or other embedding/vector-DB run, batch agent/LLM pipeline, or a real-browser/agent-browser daemon) until it finishes or wedges, then deliver a verdict (done, needs-attention, or blocked) plus the exact next command, without burning dozens of manual poll commands. Triggers on "babysit this job", "watch this until it's done", "ping me when the encode/embed/batch finishes", "is this background process stuck", "monitor this ffmpeg/qmd run", or any request to wait on a long-running process and be told when it's complete or hung.