ClaudeSuperPower
SubmitLog in

call-coaching

Skill

Coach a rep on how they handled a specific call — discovery quality, objection handling, talk dynamics, and next-call focus. Name the call if you know it, or let the skill pull recent calls and identify the most likely candidate to confirm. Uses conversation_intelligence to read how the conversation

0Other

Install

git clone https://github.com/Zoominfo/zoominfo-mcp-plugin.git ~/.claude/skills/call-coaching

What is call-coaching?

Coach a rep on how they handled a specific call — discovery quality, objection handling, talk dynamics, and next-call focus. Name the call if you know it, or let the skill pull recent calls and identify the most likely candidate to confirm. Uses conversation_intelligence to read how the conversation actually went. Use when someone asks "how did I do on the Acme call", "coach me on my last discovery call", "where did I lose them", or wants actionable feedback before the next conversation. Analyzes one call at a time.

What this can do

Capabilities declared in this component's own frontmatter — not inferred.

Inherit all session tools

Declares no tool restrictions — inherits every session tool

~130 tokens of context used while enabled, before you invoke anything

Documentation

README · ~2 min read

Call Coaching

Give a rep specific, actionable feedback on a single call: what worked, what to improve, and what to focus on next time.

Prerequisites

browse_engagements (to find the call) is free but requires an active calendar/meeting integration; conversation_intelligence (to analyze it) requires at least one connected meeting source and consumes AI credits. If the call has no transcript to analyze, say so rather than coaching from assumption.

Input

Provided via $ARGUMENTS:

  • Which call (optional) — an account and/or date. If omitted, the skill identifies the most likely recent call and confirms before analyzing.
  • Focus (optional) — e.g. "discovery", "the pricing objection", "did I talk too much". Targets the coaching.

Workflow

  1. Identify the call. browse_engagements filters by date and by company/contact ID, not by call name, so resolve any named account or contact first via search_companies / search_contacts, then call browse_engagements (engagementType: MEETINGS, sort: -chronological) scoped to that ID and date window and pick the matching meeting from the results. If nothing was named, call browse_engagements for the user's recent meetings, propose the most likely candidate, and confirm it before spending credits. If more than one meeting plausibly matches, ask. Keep the chosen engagement ID.

Reviews

Log in to leave a review.

No reviews yet — be the first.

Explore related

Other things in this space — across every part of the ecosystem, not just skills.