Files
marketingskills/tools/integrations/gong.md
T
Corey Haines 30f9b9a729 feat: v2.0 skill renames and CRO consolidation (#291)
* feat: v2.0 skill renames and CRO consolidation

BREAKING CHANGE: Users must reinstall skills after this update.

## Skill Renames (16)
- ab-test-setup → ab-testing
- analytics-tracking → analytics
- aso-audit → aso
- competitor-alternatives → competitors
- email-sequence → emails
- free-tool-strategy → free-tools
- launch-strategy → launch
- onboarding-cro → onboarding
- paywall-upgrade-cro → paywalls
- popup-cro → popups
- pricing-strategy → pricing
- product-marketing-context → product-marketing
- referral-program → referrals
- schema-markup → schema
- signup-flow-cro → signup
- social-content → social

## Consolidations (1)
- page-cro + form-cro → cro (form content in references/form.md)

## Why 2.0?
- Shorter, cleaner skill names
- Consistent naming (no -strategy, -setup, -cro suffixes)
- All cross-references updated across 100+ files

Total skills: 40

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

* fix(v2.0): update evals for renamed skills, fix validate script, clear warnings

- Update 32 evals.json files to reference new skill names (page-cro → cro,
  product-marketing-context → product-marketing, etc.) — these were missed
  in the initial v2.0 rename pass since only SKILL.md and marketplace.json
  were updated.
- Fix validate-skills.sh: replace GNU-only `head -n -1` with portable awk
  so frontmatter extraction works on macOS.
- Move Copy Editing Checklist (56 lines) to references/checklist.md to
  bring copy-editing SKILL.md under the 500-line limit (508 → 457).
- Add "see X" pointers to marketing-psychology description for skill
  discovery (cro, pricing, copywriting).
- Update skill-request.yml issue template placeholder (page-cro → cro).

All 40 skills now pass validation with zero warnings.

* fix(v2.0): add evals for 8 missing skills, strip stale frontmatter from cro/form.md

Adds 48 new eval cases (6 per skill) for skills that previously had no evals:
aso, co-marketing, community-marketing, competitor-profiling, directory-submissions,
image, lead-magnets, video. All 40 skills now have eval coverage (251 total cases).

Strips leftover frontmatter from skills/cro/references/form.md — it was inherited
from the old form-cro SKILL.md before consolidation. Reference files don't need
frontmatter.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* fix(v2.0): rename paid-ads → ads

One more v2.0 simplification — drops the redundant 'paid-' qualifier. Updates
the skill directory, SKILL.md frontmatter, evals.json, README skill table, the
v2.0 rename table in VERSIONS.md (now 17 renames), and all cross-references in
related skills (ad-creative, aso, competitor-profiling, customer-research,
lead-magnets, marketing-ideas) plus the tools/integrations guides.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* fix(v2.0): bump SKILL.md frontmatter version to 2.0.0 for all 40 skills

VERSIONS.md was already updated to 2.0.0 but the metadata.version field inside
each SKILL.md was still on 1.x. That mismatch would have caused the update-check
flow to perpetually report 'update available' since it compares VERSIONS.md
against local SKILL.md metadata versions.

Caught by codex review (P1).

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* fix(v2.0): add legacy product-marketing-context.md filename fallback

Before this fix, users upgrading from v1.x who had a `product-marketing-context.md`
file would lose automatic context loading — every skill only checked the new
`product-marketing.md` filename. Now all 40 skills also accept the legacy
filename (in either `.agents/` or `.claude/`), and the README migration command
covers both legacy and current filenames.

Caught by codex review (P1 + P2).

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* fix(v2.0): re-sort README skills table alphabetically, fix ads box width

The skills table had a few entries out of alphabetical order from the renames
(co-marketing was after cold-email, ads was at the renamed position).
Re-sorted alphabetically per sync-skills.js. Also padded the 'ads' cell in the
ASCII flow diagram to keep the box width consistent.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* fix(v2.0): document folder cleanup on upgrade, stop sync-skills from re-adding skills array

README upgrade guide now includes:
- A clear cleanup step for stale v1.x skill folders (renamed + consolidated) so
  users don't end up with both old and new folders side-by-side after upgrading
- The full v1 to v2 rename map for reference
- Existing product-marketing-context.md migration steps (preserved)

sync-skills.js no longer (re-)introduces a `skills` array on marketplace.json --
Claude Code's plugin schema discovers skills via the `skills/` directory, and the
explicit array was failing validation. The script now refreshes the description
count and strips the stale array if present.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
2026-05-13 22:05:15 -07:00

4.2 KiB

Gong

Revenue intelligence platform that records, transcribes, and analyzes sales conversations (calls, video meetings, emails) to surface deal insights, coaching opportunities, and competitive intelligence.

Capabilities

Integration Available Notes
API REST API, Basic Auth or OAuth2
MCP - Not available
CLI - Not available
SDK - REST API only; community Python client via dltHub

Authentication

API Endpoints

Most Gong API endpoints use POST with JSON request bodies for filtering. Check the official API docs for current endpoint availability.

Calls

# List calls (with date/user filters)
POST /v2/calls/extensive

# Get call transcripts (batch, by call IDs)
POST /v2/calls/transcript

Users & Stats

# List users
GET /v2/users

# Get activity stats (talk ratio, questions asked, longest monologue)
POST /v2/stats/activity/day-by-day

Engagement Flows

# List flows
GET /v2/flows

# Get flow analytics
GET /v2/flows/{id}/analytics

Key Data Points

Per Call

  • Full transcript with speaker labels and timestamps
  • Talk-to-listen ratio per participant
  • Topics discussed (auto-detected)
  • Questions asked (count and content)
  • Longest monologue duration
  • Next steps mentioned
  • Competitor mentions
  • Pricing discussions flagged

Per Deal

  • All associated calls and emails
  • Deal stage progression
  • Risk signals (gone dark, competitor mentioned, champion left)
  • Engagement score

Per Rep

  • Talk ratio trends
  • Question frequency
  • Topic coverage vs. playbook
  • Win rate correlation with behaviors

Common Agent Operations

Extract Competitive Intelligence from Calls

  1. Query calls mentioning competitor names
  2. Extract: objections raised, features compared, pricing discussed
  3. Synthesize into competitive battlecard updates
  4. Track competitor mention frequency over time

Mine Calls for Customer Research

  1. Pull transcripts from recent won/lost deals
  2. Extract: pain points, trigger events, decision criteria, language used
  3. Feed into persona building and messaging work
  4. Identify recurring objections for sales enablement

Revenue Attribution

  1. Pull call data alongside CRM deal data
  2. Map which content/pages were discussed in winning deals
  3. Identify which talking points correlate with closed-won
  4. Build content-to-revenue attribution reports

Rep Coaching Insights

  1. Compare top performer call patterns vs. team average
  2. Identify: talk ratio, question frequency, topic coverage gaps
  3. Surface specific call moments for coaching review
  4. Track improvement over time

Rate Limits

  • 3 API calls per second
  • 10,000 API calls per day
  • Pagination required for large result sets

When to Use

  • Mining sales call transcripts for customer research and VOC data
  • Extracting competitive intelligence from prospect conversations
  • Building revenue attribution models (content → deal influence)
  • Analyzing win/loss patterns across deal transcripts
  • Coaching sales reps based on conversation analytics
  • Identifying common objections and buying signals

Limitations

  • API access requires admin credentials
  • Transcript quality depends on call audio quality
  • Rate limits (10k/day) may constrain large-scale analysis
  • Pricing is enterprise-level (not publicly listed, typically $100+/user/month)
  • Requires team adoption — records calls via integrations, but also supports uploading calls from non-integrated telephony systems

Relevant Skills

  • customer-research
  • sales-enablement
  • competitors
  • revops
  • cold-email

Sources