Zoom Plugin

Skill 138 of 200

Start

Start here for any Zoom integration or app idea.

1 minute · 175 words · 4 sections

Install

$ npx skills add anthropics/knowledge-work-plugins --skill start

$ npx skills add anthropics/knowledge-work-plugins

» /plugin marketplace add anthropics/knowledge-work-plugins

The first command installs just this skill, by the name in its SKILL.md; the second installs the whole repository.

Use this as the default entry skill for the plugin.

What This Skill Does

Classifies the request by job-to-be-done, not by product name alone
Routes into the right implementation skill
Pulls in product-specific Zoom references only after the route is clear
Prevents common early mistakes, especially Meeting SDK vs Video SDK and REST API vs MCP confusion

Routing Table

If the user wants to…	Route to
Choose the right Zoom surface for a new project	plan-zoom-product
Set up OAuth, tokens, scopes, or app credentials	setup-zoom-oauth
Embed or customize a Zoom meeting flow	build-zoom-meeting-app
Build a bot, recorder, or real-time meeting processor	build-zoom-bot
Use Zoom-hosted MCP for AI workflows	setup-zoom-mcp
Debug a broken integration	debug-zoom

Supporting Zoom References

Use these only after selecting the workflow:

Operating Rules

Prefer one clear recommendation over a product catalog dump.
Ask a short clarifier only when the route is genuinely ambiguous.
Keep the first response architectural and actionable, then go deep.
Pull in deeper references only when they directly help the current decision or implementation.

About this skill

Trigger

Start here for any Zoom integration or app idea. Use when you need to choose the right Zoom surface, shape the architecture, or route into the correct implementation skill without reading the whole Zoom doc set first.

The verbatim description from this skill’s front matter — the string an agent matches on to decide whether to load it.

Colophon for this issue

Colophon

How this issue was made

Source

github.com/anthropics/knowledge-work-plugins, branch main, last pushed 24 September 2026.

Licence

Apache-2.0 — the text of every skill is reproduced unmodified, frontmatter included, under the upstream licence.

Discovery

200 skills found by walking the repository tree for SKILL.md, not by matching a directory convention. 27 distinct layouts observed: bio-research/skills/*/SKILL.md, cowork-plugin-management/skills/*/SKILL.md, customer-support/skills/*/SKILL.md, data/skills/*/SKILL.md, design/skills/*/SKILL.md, engineering/skills/*/SKILL.md, enterprise-search/skills/*/SKILL.md, finance/skills/*/SKILL.md, human-resources/skills/*/SKILL.md, legal/skills/*/SKILL.md, marketing/skills/*/SKILL.md, operations/skills/*/SKILL.md, partner-built/apollo/skills/*/SKILL.md, partner-built/brand-voice/skills/*/SKILL.md, partner-built/common-room/skills/*/SKILL.md, partner-built/slack/skills/*/SKILL.md, partner-built/zoom-plugin/skills/*/SKILL.md, partner-built/zoom-plugin/skills/contact-center/*/SKILL.md, partner-built/zoom-plugin/skills/meeting-sdk/*/SKILL.md, partner-built/zoom-plugin/skills/meeting-sdk/web/*/SKILL.md, partner-built/zoom-plugin/skills/video-sdk/*/SKILL.md, partner-built/zoom-plugin/skills/virtual-agent/*/SKILL.md, partner-built/zoom-plugin/skills/zoom-mcp/*/SKILL.md, pdf-viewer/skills/*/SKILL.md, product-management/skills/*/SKILL.md, productivity/skills/*/SKILL.md, sales/skills/*/SKILL.md.

Issue colours

Resolved from the awesome-design-md registry — hue 39°, chroma 0.113. Two accent tones are generated per issue and each is proven against its own ground before it ships: a single accent that passes AA on both light and dark paper is arithmetically impossible.

Typefaces

Display: Copernicus is not available to us; set in Newsreader.

We never load a typeface at request time from a third-party origin, so a brand face we do not already self-host is substituted rather than fetched.

Heading repairs

1 repair applied to this skill so the document has one h1 and no skipped levels:

Removed “Start”, a leading h1 that duplicated the skill title.

Spec compliance

53 editorial notes across 41 of 200 skills. They are printed in the margin of each skill rather than as errors here.

and 31 more.

Images

Images inside a skill come from the upstream repository. Where the author gave no alternative text we mark the image decorative rather than inventing a description — a plausible caption we made up is worse than none for the reader who depends on it.

Marketplace

A plugin manifest is published at .claude-plugin/marketplace.json by Anthropic, declaring 120 plugins. It is read for editorial metadata only — never as the skill index, which is always the repository tree.

Signal

Install counts come from skills.sh. They measure downloads, not quality, and an unranked repository is not an unread one.

Agent surfaces

The whole issue is available as one markdown document at /anthropics/knowledge-work-plugins.md, and each skill at its own .md URL.

Publication

Set by Skills Docs from the source repository. Body text is Literata at the reader’s chosen size and measure; code is Geist Mono. Nothing on this page was written by us except this paragraph.

Use this as the default entry skill for the plugin.

What This Skill Does

Classifies the request by job-to-be-done, not by product name alone
Routes into the right implementation skill
Pulls in product-specific Zoom references only after the route is clear
Prevents common early mistakes, especially Meeting SDK vs Video SDK and REST API vs MCP confusion

Routing Table

If the user wants to…	Route to
Choose the right Zoom surface for a new project	plan-zoom-product
Set up OAuth, tokens, scopes, or app credentials	setup-zoom-oauth
Embed or customize a Zoom meeting flow	build-zoom-meeting-app
Build a bot, recorder, or real-time meeting processor	build-zoom-bot
Use Zoom-hosted MCP for AI workflows	setup-zoom-mcp
Debug a broken integration	debug-zoom

Supporting Zoom References

Use these only after selecting the workflow:

Operating Rules

Prefer one clear recommendation over a product catalog dump.
Ask a short clarifier only when the route is genuinely ambiguous.
Keep the first response architectural and actionable, then go deep.
Pull in deeper references only when they directly help the current decision or implementation.