Gong

**Judgment**: This skill is a solid, focused integration for teams already using Gong and needing automated access to calls, transcripts, and activity analytics. It is primarily read-only and centers on retrieval and analysis operations, making it well-suited for reporting, summarization, and sales intelligence workflows. **Strengths** - Good coverage of key Gong endpoints (users, calls, transcripts, activity stats, meetings) with filtering and pagination. - Uses Gong’s official v2 API and standard HTTP/JSON patterns, which should perform well and be robust. - Well-suited for building agent workflows that summarize calls, surface insights, or compute simple analytics. **Risks / Limitations** - Exposes sensitive internal call content (PII, customer data, internal strategies); requires strict access control and careful prompt design to avoid over-exposure. - Depends on correct credential management via files/env vars; if misconfigured, calls will fail and may be hard to debug from within an agent. - Appears read-only and focused on a subset of operations; more advanced or write-type actions in Gong (if needed) are not covered. - Rate limit (~3 req/s) and potentially heavy transcript payloads may constrain high-volume or highly interactive agents. **Recommended Scenarios** - Enterprise or sales ops environments where Gong is already deployed and there is a clear need to automatically summarize, analyze, or report on call activity. - Agent workflows that pull in Gong call transcripts as a data source for coaching, QBR preparation, or automated CRM note generation. - Analytics or monitoring tasks that need aggregated activity stats over defined time windows (e.g., last 7 days, monthly reports).