Name: gong
Rating: 64 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

gong

Gong integration. Manage Calls, Users, Teams, Deals. Use when the user wants to interact with Gong data.

Quality

76%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/gong/SKILL.md

Quality

Content

82%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.

The content is highly actionable with concrete, executable Membrane commands and a well-structured connection workflow that includes validation via state polling. Minor conciseness and organization gaps (intro padding, inlined action catalog, unlabeled "Step 2") keep it from the top tier.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient command-driven guidance, but includes light over-explanation such as the introductory paragraph on what Gong is and filler like "Use action names and parameters as needed," which could be trimmed.	4 / 5
Actionability	It provides copy-paste-ready executable commands throughout (install, login, connection ensure/get, action list/run, proxy request) with concrete flags and a popular-actions table, fully covering the common cases.	5 / 5
Workflow Clarity	The connection flow is clearly sequenced with an explicit state machine (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and polling feedback loops, but "Step 2" is referenced without being labeled, a minor checkpoint gap.	4 / 5
Progressive Disclosure	The body is well organized into clear sections for a self-contained skill with no bundle files, though the 18-row popular-actions catalog is inlined reference data that arguably belongs in a separate file, keeping it just below anchor 5.	4 / 5
	Total	17 / 20 Passed

Description

70%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.

The description is concise and clearly answers both what it does and when to use it, with a distinct Gong-specific niche. It is held back by a generic "Manage" verb and trigger phrasing that could be more concrete.

Suggestions

Replace the single generic verb "Manage" with a few specific actions (e.g., "List, retrieve, and create Calls, Users, Teams, and Deals") to raise specificity.

Expand the "Use when" clause with concrete trigger phrases users actually say (e.g., "Use when the user wants to list Gong calls, fetch call transcripts, or query Gong users and deals").

Add natural synonyms/variants (e.g., "conversations", "revenue calls") to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	The description names the domain and four concrete entities ("Manage Calls, Users, Teams, Deals"), but relies on a single generic verb ("Manage") rather than enumerating several specific actions, which keeps it below anchor 4.	3 / 5
Completeness	Both "what" (Gong integration managing Calls/Users/Teams/Deals) and "when" ("Use when the user wants to interact with Gong data") are present, but the trigger clause is somewhat generic rather than packed with concrete trigger phrases, fitting anchor 4.	4 / 5
Trigger Term Quality	It surfaces natural terms users would say ("Calls, Users, Teams, Deals", "interact with Gong data") plus the product name "Gong", giving good keyword coverage with only minor synonym gaps.	4 / 5
Distinctiveness Conflict Risk	The explicit "Gong" naming and "interact with Gong data" trigger carve out a clear niche, but the entity vocabulary (Calls/Users/Teams/Deals) overlaps with generic CRM/sales skills, leaving minor overlap risk below anchor 5.	4 / 5
	Total	15 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/gong/SKILL.md
Commit: f484c82

Reviewed: ~20 hours 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.