Zoom Meeting SDK Android

anthropics/zoom-meeting-sdk-android

| Zoom Meeting SDK for Android native apps. Use when embedding Zoom meetings in Android with default/custom UI, PKCE + SDK auth, join/start flows, and Meeting SDK API integration.

3k tokens

context cost

the whole folder, loaded on every use

files

instructions only

copies elsewhere

how many repositories repackaged it

23273

stars on the repo

on the repository, not the skill itself

Install

one command, takes just this skill from the repository

npx skills add https://github.com/anthropics/knowledge-work-plugins --skill zoom-meeting-sdk-android

What comes with it

9 261 bytes besides the instruction

RUNBOOK.md

android.md

concepts/architecture.md

concepts/lifecycle-workflow.md

examples/join-start-pattern.md

references/android-reference-map.md

references/environment-variables.md

references/versioning-and-compatibility.md

scenarios/high-level-scenarios.md

troubleshooting/common-issues.md

The instruction itself

5 sections, as written by the author

Zoom Meeting SDK (Android)

Use this skill when building Android apps with embedded Zoom meeting capabilities.

Start Here

android.md
concepts/lifecycle-workflow.md
concepts/architecture.md
examples/join-start-pattern.md
scenarios/high-level-scenarios.md
references/android-reference-map.md
references/environment-variables.md
references/versioning-and-compatibility.md
troubleshooting/common-issues.md

Routing Notes

Use default UI first for first successful join/start validation.
Move to custom UI once auth, meeting state transitions, and permissions are stable.
For signature/JWT mistakes, chain with ../../oauth/SKILL.md and ../references/signature-playbook.md.

Key Sources

Docs: https://developers.zoom.us/docs/meeting-sdk/android/
API reference: https://marketplacefront.zoom.us/sdk/meeting/android/index.html
Broader guide: ../SKILL.md

Operations

RUNBOOK.md - 5-minute preflight and debugging checklist.

How to use it

Copy the folder

Take anthropics/zoom-meeting-sdk-android from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

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.