Savant verdict: Analyzed
Scanned or evaluated by Savant; not yet both passing.
Live evaluation
Not evaluated yet. Workspaces can request a live evaluation.
Safety (NVIDIA SkillSpector)
Risk score
0/100
Recommendation
SAFE
Severity
LOW
Savant decision
Passed
SkillSpector rated the package safe. SkillSpector 2.12.0, static analysis.
0 patterns found
Structure
- Description is very shortA description that says when to use the skill helps agents route to it.
- No license declaredConfirm you may reuse this skill before importing it into your repository.
SKILL.md
--- name: build-zoom-meeting-app description: Use when embedding meetings. --- # /build-zoom-meeting-app Use this skill for embedded meeting experiences and meeting lifecycle implementation. ## Covers - Meeting SDK selection and platform routing - Join/auth implementation planning - Meeting creation plus join flow design - Web vs native platform considerations - Meeting SDK vs Video SDK boundary decisions ## Workflow 1. Confirm whether the user wants a Zoom meeting or a custom video session. 2. Route to Meeting SDK if the user needs actual Zoom meetings. 3. Pull in the relevant platform references. 4. Add REST API only for meeting creation, resource management, or reporting. 5. Add webhooks or RTMS only when the use case explicitly needs them. ## Primary References - [meeting-sdk](../meeting-sdk/SKILL.md) - [rest-api](../rest-api/SKILL.md) - [webhooks](../webhooks/SKILL.md) - [rtms](../rtms/SKILL.md) - [video-sdk](../video-sdk/SKILL.md) ## Common Mistakes - Using Video SDK for normal Zoom meeting embeds - Mixing resource-management APIs into the core join flow without reason - Skipping platform-specific SDK constraints until too late