Gong

PassAudited by ClawScan on May 1, 2026.

Overview

This skill coherently wraps Gong’s API, but installing it means the agent can use your Gong API key to read users, calls, transcripts, and activity data.

Install this only if you want the agent to use your Gong API credentials to retrieve Gong users, calls, transcripts, call details, and activity stats. Use a scoped API key, verify the configured base_url is a real Gong API endpoint, and keep ~/.config/gong/credentials.json protected.

Findings (3)

Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.

Low

#ASI03: Identity and Privilege Abuse

What this means

Anyone using this skill should assume the agent can access Gong data allowed by the configured API key.

Why it was flagged

The helper reads a local Gong access key and secret, builds a Basic Auth header, and sends it to the configured Gong base URL. This is expected for the skill’s purpose, but it gives the agent account-level API access through the provided key.

Skill content

CREDS=${GONG_CREDS:-~/.config/gong/credentials.json}
BASE=$(jq -r '.base_url' "$CREDS")
AUTH=$(jq -r '"\(.access_key):\(.secret_key)"' "$CREDS" | base64)
...
curl -s "$BASE$1" -H "Authorization: Basic $AUTH"

Recommendation

Use a dedicated, least-privilege Gong API key, confirm the base_url is an official Gong API domain, and protect the credentials file with appropriate local file permissions.

Low

#ASI02: Tool Misuse and Exploitation

What this means

The agent may retrieve and display internal Gong users, meeting participants, call metadata, and transcript text when used for Gong-related tasks.

Why it was flagged

The script exposes read operations for users, full call details, parties, and transcripts. These operations match the skill description, but they can reveal sensitive sales and meeting content.

Skill content

users)
    api "/v2/users"
...
call)
    api "/v2/calls/extensive" -X POST ... "content":true,"parties":true
...
transcript)
    api "/v2/calls/transcript" -X POST

Recommendation

Install only in workspaces where this Gong visibility is intended, and avoid using broad API keys if only a subset of calls or users should be accessible.

Info

#ASI04: Agentic Supply Chain Vulnerabilities

What this means

Users may not realize from metadata alone that local CLI tools and a Gong credential file are needed.

Why it was flagged

The helper visibly depends on jq, base64, curl, and shell execution, while registry metadata lists no required binaries and no primary credential. This is an under-declaration rather than hidden behavior.

Skill content

BASE=$(jq -r '.base_url' "$CREDS")
AUTH=$(jq -r '"\(.access_key):\(.secret_key)"' "$CREDS" | base64)
...
curl -s "$BASE$1"

Recommendation

Before installing, verify the included script contents, ensure required CLI tools are available, and treat the registry metadata as incomplete.