agentleFS
zoomzoom/skills/.cursor/rules/zoom-platform.mdc

skills / rules

Cursor rule82 starsChanged 8 months agoMITView on GitHub

For Zoom Developer Platform tasks, prefer current official documentation over memory and route to the matching skill under skills/.

We split this zoom-platform.mdc into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Stop and verify current Zoom documentation before answering unstable questions about:

    line 16
  2. Distinctive:

    Do not answer Meeting SDK and Video SDK tasks interchangeably.

    line 42
  3. Distinctive:

    Do not answer REST API and MCP tasks interchangeably.

    line 43

≈ “Common” is an estimate: at least 1 in 5 of the 6,350 Cursor rule files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
zoom-platform.mdc
---
description: For Zoom Developer Platform tasks, prefer current official documentation over memory and route to the matching skill under skills/.
alwaysApply: false
globs:
  - "**/*.md"
  - "**/*.ts"
  - "**/*.tsx"
  - "**/*.js"
  - "**/*.jsx"
  - "**/*.mjs"
  - "**/*.cjs"
  - "**/*.json"
---
# Zoom Developer Platform

Stop and verify current Zoom documentation before answering unstable questions about:
- API endpoints and scopes
- SDK versions and platform setup
- MCP tools, scopes, and endpoints
- rate limits
- app types and Marketplace requirements

## Preferred sources

- Zoom API Hub: `https://developers.zoom.us/api-hub/`
- Zoom docs: `https://developers.zoom.us/`
- Zoom Developer Forum: `https://devforum.zoom.us/`
- Zoom MCP:
  - `https://mcp-us.zoom.us/mcp/zoom/streamable`
  - `https://mcp-us.zoom.us/mcp/whiteboard/streamable`

## Routing

Route to the closest matching skill under `skills/` first:
- `skills/general/` for cross-product routing
- `skills/rest-api/` for deterministic API automation
- `skills/meeting-sdk/` for embedded Zoom meetings
- `skills/video-sdk/` for custom video sessions
- `skills/zoom-mcp/` for Zoom-hosted MCP workflows
- `skills/webhooks/` and `skills/websockets/` for event delivery

Do not answer Meeting SDK and Video SDK tasks interchangeably.
Do not answer REST API and MCP tasks interchangeably.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.