Gong API for searching calls, transcripts, and conversation intelligence. Use when working with Gong call recordings, sales conversations, transcripts, meeting data, or conversation analytics. Supports listing calls, fetching transcripts, user management, and activity stats.
92
Does it follow best practices?
Validation for skill structure
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-crafted skill description that excels across all dimensions. It clearly identifies the specific platform (Gong), lists concrete capabilities, includes an explicit 'Use when...' clause with natural trigger terms, and occupies a distinct niche that won't conflict with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'searching calls, transcripts, and conversation intelligence', 'listing calls, fetching transcripts, user management, and activity stats'. These are clear, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what ('Gong API for searching calls, transcripts...', 'Supports listing calls, fetching transcripts...') and when ('Use when working with Gong call recordings, sales conversations, transcripts, meeting data, or conversation analytics'). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'Gong', 'call recordings', 'sales conversations', 'transcripts', 'meeting data', 'conversation analytics'. These are terms users would naturally use when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Very distinct niche with 'Gong' as a specific product name, combined with domain-specific terms like 'sales conversations' and 'conversation intelligence'. Unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, well-crafted API skill that provides executable, copy-paste ready examples with excellent organization. The main weakness is the lack of error handling guidance and validation steps - there's no mention of checking response codes, handling rate limit errors, or verifying successful API calls before using returned data.
Suggestions
Add a brief error handling section showing how to check for successful responses (e.g., checking HTTP status codes or response structure before processing)
Include an example of handling rate limit errors (429 responses) given the noted 3 req/sec limit
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, providing only necessary information without explaining what Gong is or how APIs work. Every section serves a clear purpose with no padding or unnecessary context. | 3 / 3 |
Actionability | All examples are fully executable bash commands with proper curl syntax, jq transformations, and realistic JSON payloads. Copy-paste ready with clear variable setup. | 3 / 3 |
Workflow Clarity | Operations are clearly presented but lack validation checkpoints. No guidance on verifying API responses, handling errors, or confirming successful operations before proceeding. | 2 / 3 |
Progressive Disclosure | Well-organized with clear sections progressing from setup to authentication to operations. The endpoint reference table provides quick lookup. Content is appropriately sized for a single file without needing external references. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 13 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 13 / 16 Passed | |
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.