zoom-meeting-sdk-electron

Zoom Meeting SDK for Electron desktop applications. Use when embedding Zoom meetings in an Electron app with the Node addon wrapper, JWT auth, join/start flows, settings controllers, and raw data integration.

Jump to install

Repository: anthropics/knowledge-work-plugins
Last source activity: April 9, 2026 at 23:28
Detected SKILL.md language: English
Stars: 25,304
Forks: 3,008

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

A direct command skips the review prompt. Inspect the source before running it.

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

The command stays on one line. Scroll horizontally to inspect it before copying.

Prefer a local copy? Download the files currently available to SkillsMP.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

File Explorer

14 files

SKILL.md

Source instructions · Read-only preview

name: zoom-meeting-sdk-electron
description: Zoom Meeting SDK for Electron desktop applications. Use when embedding Zoom meetings in an Electron app with the Node addon wrapper, JWT auth, join/start flows, settings controllers, and raw data integration.
user-invocable: false
triggers: ["electron meeting sdk","zoom meeting sdk electron","embed zoom in electron","electron zoom bot","zoom node addon","zoom raw data electron"]

# Zoom Meeting SDK (Electron) Use this skill when building Electron desktop apps that embed Zoom Meeting SDK capabilities through the Electron wrapper. ## Start Here 1. **[Lifecycle Workflow](concepts/lifecycle-workflow.md)** - init -> auth -> join/start -> in-meeting -> cleanup 2. **[SDK Architecture Pattern](concepts/sdk-architecture-pattern.md)** - service/controller/event model in Electron 3. **[Setup Guide](examples/setup-guide.md)** - dependency and build expectations 4. **[Authentication Pattern](examples/authentication-pattern.md)** - SDK JWT generation and auth callbacks 5. **[Join Meeting Pattern](examples/join-meeting-pattern.md)** - start/join meeting execution flow 6. **[SKILL.md](SKILL.md)** - full navigation ## Core Notes - Electron wrapper is built on top of native Meeting SDK with Node addon bridges. - Keep SDK key/secret server-side; generate SDK JWT on backend. - Feature support differs by platform/version; check module docs before implementation. - Raw data and IPC patterns require explicit security hardening in production. ## References - [Electron API Reference Index](references/electron-reference.md) - [Module Map](references/module-map.md) - [Deprecated and Contradictions](troubleshooting/deprecated-and-contradictions.md) ## Related Skills - [zoom-meeting-sdk](../SKILL.md) - [zoom-oauth](../../oauth/SKILL.md) - [zoom-general](../../general/SKILL.md) ## Merged from meeting-sdk/electron/SKILL.md # Zoom Meeting SDK Electron - Documentation Index ## Start Here 1. [SKILL.md](SKILL.md) 2. [Lifecycle Workflow](concepts/lifecycle-workflow.md) 3. [SDK Architecture Pattern](concepts/sdk-architecture-pattern.md) 4. [Setup Guide](examples/setup-guide.md) ## Concepts - [Lifecycle Workflow](concepts/lifecycle-workflow.md) - [SDK Architecture Pattern](concepts/sdk-architecture-pattern.md) - [High-Level Scenarios](concepts/high-level-scenarios.md) ## Examples - [Setup Guide](examples/setup-guide.md) - [Authentication Pattern](examples/authentication-pattern.md) - [Join Meeting Pattern](examples/join-meeting-pattern.md) - [Raw Data Pattern](examples/raw-data-pattern.md) ## References - [Electron API Reference](references/electron-reference.md) - [Module Map](references/module-map.md) ## Troubleshooting - [Common Issues](troubleshooting/common-issues.md) - [Version Drift](troubleshooting/version-drift.md) - [Deprecated and Contradictions](troubleshooting/deprecated-and-contradictions.md) ## Operations - [RUNBOOK.md](RUNBOOK.md) - 5-minute preflight and debugging checklist.

View on GitHub

Back to search Back to installation

ad-manager

The ads consultant that becomes an ads agent. Reads paid-ad performance natively through the TikTok Ads connector, or via a build-connector Zapier connection for other ad platforms, explains in plain English what is working and what is burning money, recommends budget, targeting, and creative changes with the dollar impact of each, drafts new ad copy in the owner's voice plus Canva creative briefs, and — only after an explicit yes — executes the approved changes in the ad account. Works from exported CSV reports when nothing is connected, the normal starting point. Use this whenever the owner talks about ads or ad spend at all, including "are my ads working," "what's my ROI on ads," "I'm spending money on Facebook and I don't know what I'm getting," "should I turn this campaign off," "my cost per lead is going up," "write me a new ad," "who should I be targeting," or "the ad guy quit."

2026-09-15

ap-processor

Works the bill pile end to end: reads bills and vendor statements out of the AP inbox or from uploaded PDFs and phone photos, pulls out vendor, amount, due date, and line detail, codes each one to the right account and job, matches it against the purchase order and the receiving ticket, then stages the entries and a proposed payment run in QuickBooks, Xero, or NetSuite for the owner to approve in one pass. Nothing is entered and nothing is paid without an explicit yes. Reach for this whenever bills, vendor invoices, or paying people comes up — including "what do I owe," "the bills are piling up," "pull the invoices out of my email and into QuickBooks," "code these for me," "who needs to get paid this week," "did we get billed twice," or when the owner forwards a supplier invoice with no message at all. Use it before cash-flow-snapshot or month-end-prep so those run on real payables instead of a guess.

2026-09-15

brand-style

Sets and updates the owner's brand look and output preferences, which every page and document the plugin produces then follows automatically. Captures the brand from a pasted website link or a plain-words description — never a hex code, color picker, or upload — previews it on a sample page, asks how they want their outputs delivered (visual artifacts, Word docs, markdown, Notion pages, Canva Docs, or best-for-the-skill), and saves both to the business profile. Runs inside smb-onboard on first setup and stands alone forever after. Use when the owner says "update my brand," "we rebranded," "change my colors," "make the reports match our new look," "change how you give me reports," "I want Word docs instead," or anything about the look or format of what the plugin hands them.

2026-09-15

View all from this repository

zoom-meeting-sdk-electron

Source facts

Install options

Review the source files

More from this repository

More from this repository