build-zoom-phone-integration

Savant verdict: Review advised

SkillSpector or the source hub flagged patterns to review before use.

Live evaluation

Not evaluated yet. Workspaces can request a live evaluation.

Safety (NVIDIA SkillSpector)

5 patterns found

• Privilege Escalation: access tokenhigh · RUNBOOK.md:21 · Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
• Privilege Escalation: access tokenhigh · references/forum-top-questions.md:46 · Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
• Privilege Escalation: Access tokenhigh · troubleshooting/common-issues.md:15 · Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
• Data Exfiltration: https://api.zoom.us/medium · examples/phone-api-service-pattern.md:14 · Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
• Data Exfiltration: https://api.zoom.us/medium · examples/phone-api-service-pattern.md:30 · Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.

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-phone-integration
description: Use when building Phone.
---

# Build Zoom Phone Integration

Use this skill when the target workflow is Zoom Phone, CTI, CRM calling, call events, or Smart Embed behavior.

## Workflow

1. Classify the integration: REST API automation, webhook event processing, Smart Embed, URI launch, CRM dialer, or call-handling workflow.
2. Confirm the actor, account settings, phone entitlements, and OAuth scopes before implementation.
3. Keep call control, call records, number management, and webhook processing as separate modules.
4. For Smart Embed, validate postMessage event contracts, embedding constraints, and CRM state mapping.
5. Debug by checking scopes, phone license, role permissions, number ownership, webhook subscriptions, and event payload shape.

## References

- Full preserved guide: [references/full-guide.md](references/full-guide.md)
- Architecture and lifecycle: [concepts/architecture-and-lifecycle.md](concepts/architecture-and-lifecycle.md)
- Phone API service pattern: [examples/phone-api-service-pattern.md](examples/phone-api-service-pattern.md)
- Smart Embed bridge: [examples/smart-embed-postmessage-bridge.md](examples/smart-embed-postmessage-bridge.md)
- Event contract: [references/smart-embed-event-contract.md](references/smart-embed-event-contract.md)
- Common issues: [troubleshooting/common-issues.md](troubleshooting/common-issues.md)