Skip to main content
skill CX Codex

sales-coach — Claude Code skill for sales calls

The sales-coach Claude Code skill suggests responses to sales objections from call captions. It also flags buying signals and reviews the conversation afterward.

MIT ★ 83 updated 2026-11-01

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin marketplace add Jakeschincariol/closer-skill
/plugin install closer-skill@closer-skill
Open on GitHub

What sales-coach does

The skill reads call captions or a transcript and displays a response card when the other person raises an objection. Suggested replies draw on objections.json and the offer details in closer/pipeline.json; when a needed field is missing, the card shows [your value line] rather than inventing an answer.

Its scripts require python3. For Google Meet, Claude in Chrome can read captions on the page; visible captions from Zoom or Teams and transcript files also work. After the call, coach.py review reports speaking time, questions, objections, buying signals, and whether the participants agreed on a next step. The skill stores no audio and never speaks during the call. Tell everyone on the call that captions are on before reading them.

What it helps with

  • draft a reply to a price or timing objection
  • use details from an existing offer to answer a prospect
  • spot buying signals in a live conversation
  • check whether the call ended with an agreed next step
  • review speaking time and questions asked

Example prompts for the agent

  • Coach me through this sales call using its captions.
  • What should I say if the prospect says the price is too high?
  • Review the transcript in closer/calls/live.txt.

How to install sales-coach

1Plugin marketplace

/plugin marketplace add Jakeschincariol/closer-skill
/plugin install closer-skill@closer-skill

This installs the whole closer-skill plugin with all its skills

2Skills CLI (Vercel)

npx skills add Jakeschincariol/closer-skill --skill sales-coach -a claude-code

3Manually: put the files in place

~/.claude/skills/sales-coach/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/sales-coach/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about sales-coach

How do I install sales-coach in Claude Code?

Add the marketplace with /plugin marketplace add Jakeschincariol/closer-skill, then install the skill with /plugin install closer-skill@closer-skill.

What does sales-coach do?

It displays suggested replies to objections based on call captions, flags buying signals, and points out questions that still need an answer. After the call, it produces a conversation review.

What does sales-coach need to run?

The scripts require python3 and call captions or a transcript. For Google Meet captions, it uses Claude in Chrome; tell call participants about the captions before reading them.

Source text

SKILL.md · MIT
---
name: sales-coach
description: >-
  Sales Coach. Listens to your sales call and tells you exactly what to say next. Reads the call's
  live captions (Google Meet's own captions, read off the page by Claude in Chrome, or any captions
  file), and the moment the other side raises an objection ("it's too expensive", "let me think
  about it", "I need to ask my partner", "we already have someone") it shows you, and only you, the
  answer to say next, filled from your real offer. Also flags buying signals and questions you
  still owe an answer, and reviews the call afterwards (talk time, questions asked, next step).
  Use when the user says "coach me on this call", "listen to my call", "I have a sales call",
  "what do I say if they say it's too expensive", "objection", "handle objections", or "review my call".
argument-hint: "[listen | card <objection> | review]"
---

# sales-coach

The coach sits beside the user on a live call, reads the captions as they appear, and answers one
question the whole time: what do I say next? It never speaks on the call. It only shows the user a card.

`${CLAUDE_SKILL_DIR}` below is this skill's folder (where this SKILL.md lives).

```bash
python3 "${CLAUDE_SKILL_DIR}/coach.py" listen --captions closer/calls/live.txt --me You
python3 "${CLAUDE_SKILL_DIR}/coach.py" listen --captions closer/calls/live.txt --me You --follow
python3 "${CLAUDE_SKILL_DIR}/coach.py" card --objection price
python3 "${CLAUDE_SKILL_DIR}/coach.py" review --captions closer/calls/live.txt --me You
```

The answers come from `objections.json` filled with the user's own offer from `closer/pipeline.json`
(`me.offer`, `me.price`, `me.plan_b`, `me.value_line`, `me.proof`). If a field is missing, the card shows
`[your value line]` instead of making one up.

## Before the call

1. Run `/researcher` on the prospect and read the brief together.
2. Check `me.plan_b` and `me.value_line` are set and TRUE. The price answer is only as good as they are.
3. Agree the opening line with the user: "Mind if I keep captions on so I can take good notes?"
   Everyone on the call hears that before anything is captured.

## During the call (Google Meet)

1. The user turns on captions in Meet (the CC button). The captions appear on the page with the speaker's name.
2. With Claude in Chrome, read the captions area every few seconds (`get_page_text` or `read_page` on the
   Meet tab) and append each NEW finished line to `closer/calls/live.txt` as `Name: text`. Never click
   anything in the meeting, never unmute, never type in the chat.
3. After each new line from the other side, run `coach.py listen --captions closer/calls/live.txt` on the
   new lines and show the card in big, plain text:

```
Objection: price  (Dana: "It looks great, but honestly, it's too expensive for us right now.")
Say this next: Totally fair. Most practices win the cost back with 2 new patients a month.
Want to start on the $399 monthly plan instead, with no setup fee?
```

4. Keep it to the card. No paragraphs mid-call. The user is talking.

Zoom, Teams or a phone call: any captions or live transcript the user can see works the same way. Or the
user runs `coach.py listen --follow` in a terminal while the lines are appended.

## The objections it knows

price, timing, needs to think, someone else decides, already has someone, does it work, send me info.
Each has the words it listens for, the answer, and why that answer works. Add the user's own: edit
`objections.json` with what their customers really say and what really works for them.

## After the call

`coach.py review`: how much of the call the user talked (aim for under half), how many questions they
asked, every objection and buying signal, and whether a next step was agreed. Then `/record-keeper call`
with the notes, and `/proposal-writer` or `/contract-writer` for the next step.

## Example from the reel

On the Thursday call at 2:14 PM, after "So that's the site, with online booking built in," Dana Ortiz said,
"It looks great, but honestly, it's too expensive for us right now." The card: Objection: price, "Totally
fair. Most practices win the cost back with 2 new patients a month. Want to start on the $399 monthly plan
instead, with no setup fee?" Then "How soon could we start?": Buying signal, agree the next step. The
transcript is `call.example.txt` (illustrative: Dana and Harbor Lane Dental are fictional).

## What it never does

- Never speaks, types or acts on the call. It only shows the user a card.
- Never keeps audio. The captions text stays in the user's project.
- Never suggests a lie, a fake deadline, a fake discount or pressure. If the true answer is "we're not the
  right fit", it says so.

## Consent and truth

- Calls: tell everyone on the call that captions or notes are on, before you start. Some places (for example
  California, Florida, Washington, and many countries) need every person's consent to record. The coach reads
  live captions as text, keeps no audio, and is shown only to the user. It never speaks on the call.
- Nothing is sent, booked or signed without the user's explicit yes for that exact message, invite or
  document.
- Never invent a number, a result, a client, a review or a deadline. Fill in only what is true and ask when
  something is missing.

© Jake Schincariol · MIT · Jakeschincariol/closer-skill

Similar skills

All skills for Marketing and content →

From the same set12

The whole set →
researcher The researcher Claude Code skill gathers public business details and prepares a call brief. It activates when asked to research a contact or before a scheduled call. CX Codex +1 ★ 83repo stars scheduler The scheduler Claude Code skill schedules calls and checks calendar availability. It activates when a reply suggests a time or someone asks for open slots. CX Codex +1 ★ 83repo stars win-back The win-back Claude Code skill finds deals ready for another contact and drafts a brief check-in. It runs on request about old or silent leads, or once a week. CX Codex +1 ★ 83repo stars record-keeper The record-keeper Claude Code skill logs emails and calls against CRM contacts. It responds to requests to sync an inbox, save call notes, or show a contact’s history. CX Codex +1 ★ 83repo stars contract-writer The contract-writer skill for Claude Code turns call notes and a proposal into a services agreement, then drafts an email to send it. After approval, it creates a PDF and records a returned signed copy as a won deal. CX Codex +1 ★ 83repo stars pipeline The pipeline Claude Code skill tracks deals on a shared CRM board. It displays stages and deal history, updates stages, and validates the data file after changes. CX Codex +1 ★ 83repo stars prospector The prospector Claude Code skill finds local businesses with gaps your offer could address and drafts tailored outreach. It responds to requests to find leads, build a prospect list, or write a cold email. CX Codex +1 ★ 83repo stars follow-up This Claude Code skill tracks follow-up dates and drafts messages for contacts who have not replied. It runs on request or as part of a morning check. CX Codex +1 ★ 83repo stars

Project sponsors

Companies that keep this analytics open