gong

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.

Quality

94%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

88%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, highly actionable read-only API skill with strong validation checkpoints and error-recovery guidance. The main room for improvement is tightening the verbose statistics-validation prose and potentially externalizing some operational detail.

Dimension	Reasoning	Score
Conciseness	The body assumes Claude's competence and avoids explaining known concepts, but the activity-statistics paragraph (timezone/midnight-instant validation prose) is dense and could be tightened without losing meaning.	4 / 5
Actionability	Provides a commands table with exact `gong.sh <subcommand>` invocations, concrete bounds (days 1–365, max_pages 1–20, segments 1–100), explicit endpoints, and a copy-paste credential JSON example — fully executable.	5 / 5
Workflow Clarity	Read-only skill with explicit validation checkpoints (returned call.id must equal requested ID; exactly one transcript with matching callId before emitting) and a failure-handling section giving per-error recovery loops.	5 / 5
Progressive Disclosure	Clean section structure and a single clearly-signaled, one-level-deep bundle reference (`scripts/gong.sh`, verified present), but the body is self-contained dense operational detail rather than an overview pointing to separate reference docs.	4 / 5
	Total	18 / 20 Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, third-person description that concretely states capabilities and gives explicit, natural trigger phrases for when to invoke the skill. It is specific, complete, and highly distinct.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'searching calls, transcripts', 'listing calls, fetching transcripts, user management, and activity stats' — with comprehensive coverage, matching the top anchor.	5 / 5
Completeness	Explicitly answers both what ('Gong API for searching calls... Supports listing calls, fetching transcripts, user management, and activity stats') and when ('Use when working with Gong call recordings...') with concrete triggers.	5 / 5
Trigger Term Quality	Surfaces five natural phrases a user would say — 'Gong call recordings, sales conversations, transcripts, meeting data, conversation analytics' — giving comprehensive trigger coverage.	5 / 5
Distinctiveness Conflict Risk	Names a specific product (Gong) with a clear niche and distinct conversation-intelligence triggers, so overlap with other skills is minimal.	5 / 5
	Total	20 / 20 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning

	Total	14 / 16 Passed

Repository: jdrhyne/agent-skills
Path: skills/gong/SKILL.md
Commit: 439cd3a

Reviewed: 13 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

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.