Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Sales Coach

ASecurity

Coach sales performance — discovery, objection handling, negotiation, pipeline management, and winning habits.

2 stars
0 votes
0 copies
2 views
Added 9/29/2026
ai-agentsgosecurityperformance

Works with

cli

Security Analysis

A100/100

Scanned 9/29/2026

$npx -y skills add aicodedecode/awesome-muse-skills --skill sales-coach --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Sales Coach?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Sales Coach
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/aicodedecode-sales-coach/badge)](https://www.skillsdirectory.com/skills/aicodedecode-sales-coach)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: sales-coach
description: Coach sales performance — discovery, objection handling, negotiation, pipeline management, and winning habits.
category: business-marketing
---

## Overview

Sales coaching improves how sellers sell: sharper discovery, better objection handling, cleaner pipeline, and stronger closing — through frameworks, practice, and feedback. This skill covers the full sales craft from prospecting to negotiation, aimed at founders selling their own product and at sales teams alike.

Coaching, not just training: the skill emphasizes diagnosing individual gaps and prescribing targeted practice.

## When to use

- Improving discovery calls that don't convert
- Handling recurring objections (price, timing, competition)
- Building or cleaning up a sales pipeline
- Preparing for a negotiation
- Onboarding new salespeople
- Diagnosing why win rates are low

- Preparing for a major enterprise deal review
- Coaching SDRs on outbound messaging that gets replies
- Building a sales playbook for a new product or segment
- Coaching account executives on enterprise deals
- Building objection-handling playbooks
- Improving discovery call quality
## Core concepts

**Discovery before pitch.** Great sellers diagnose before prescribing. Framework: situation → problem → impact → decision process. Talk-to-listen ratio should favor listening. The goal: understand pain, quantify impact, and map the buying process — before presenting anything.

**MEDDPICC (enterprise).** Metrics, Economic buyer, Decision criteria, Decision process, Paper process, Identified pain, Champion, Competition. Qualification rigor that prevents surprise losses late in the cycle.

**Objection handling.** Listen fully → acknowledge → clarify ("help me understand...") → respond with evidence → confirm resolved. Most objections are unasked questions: price objections often mean value wasn't established; timing objections mean pain isn't urgent.

**Value selling.** Tie every capability to a customer metric (revenue, cost, risk, time). Build a business case with the champion: current cost of the problem vs. cost of your solution. People buy outcomes, not features.

**Pipeline management.** Stages with exit criteria (not vibes), next steps and dates on every opportunity, regular pipeline reviews. Forecast by stage-weighted probability — and inspect the deals, not just the numbers.

**Negotiation.** Never negotiate against yourself; trade concessions (give-get); anchor high with justification; understand their constraints (budget cycles, procurement rules); be willing to walk away. The best negotiation leverage is a strong pipeline.


**Champion building.** Deals die without an internal champion who sells for you when you are not in the room. Test for champions: do they share internal information? Do they introduce you to power? Will they rehearse the pitch with you? Coach sellers to build champions deliberately, not hope for them.

**Mutual action plans.** A shared document with the buyer listing every step to close (technical validation, security review, procurement, signatures) with owners and dates on both sides. MAPs expose fake deals fast — buyers who will not commit to steps will not commit to buying.

**Discovery frameworks.** SPIN (situation, problem, implication, need-payoff), MEDDIC (metrics, economic buyer, decision criteria, decision process, identify pain, champion), and Challenger (teach, tailor, take control).
MEDDIC for complex enterprise; SPIN for mid-market; Challenger where you have genuine insight advantage.
Master one deeply rather than sampling all three.
**Objection handling.** Listen fully → acknowledge (not agree) → clarify ("help me understand...") → respond with proof → confirm resolution.
Most objections are requests for more information disguised as resistance.
Build an objection library from real calls — the same 10 objections recur.
**Demo mastery.** Tell-show-tell: tell them what you will show, show it in their context (their data, their workflow), tell them what they saw.
Demos fail from feature tours — every click must tie to a stated pain.
## Practical workflow

1. **Diagnose.** Listen to call recordings or shadow calls. Score: discovery depth, objection handling, talk ratio, next-step setting, follow-up quality. Find the one or two gaps costing the most deals.
2. **Prescribe targeted practice.** Role-play the specific weakness (e.g., price objections) with real scenarios. Record, review, repeat. Generic training doesn't fix specific gaps.
3. **Sharpen discovery.** Build a discovery question bank for your sale: situation questions (minimal), problem questions, implication questions (quantify pain), and decision-process questions (who, how, when, criteria, budget).
4. **Build the objection playbook.** List the top 5 objections. For each: what the prospect really means, clarifying questions, response framework, proof points, and a success story. Practice until responses are natural, not scripted.
5. **Install pipeline discipline.** Define stage exit criteria. Weekly pipeline review: inspect stalled deals, verify next steps, challenge happy ears. Clean dead opportunities ruthlessly — a bloated pipeline lies.
6. **Review and reinforce.** Monthly: win/loss analysis (why did we win/lose?), call reviews, metric trends (activity → pipeline → wins). Coaching is continuous, not an event.

**Discovery question bank starters:** "Walk me through how you handle X today." "What happens when X goes wrong?" "What does that cost you — in money, time, risk?" "Who else feels this pain?" "How will you decide? What's the timeline?"


**Call review scorecard (use weekly):** opening (agenda set? permission gained?) → discovery (pain quantified? decision process mapped? economic buyer identified?) → presentation (tied to their metrics? concise?) → objection handling (acknowledged? clarified? resolved?) → close (next step committed with date? mutual action plan updated?). Score 1–5 each; coach the lowest two.

**Coaching cadence:** weekly 1:1 (deal review + skill focus) → biweekly call review (recorded calls, scorecard) → monthly skill workshop (one skill deep) → quarterly plan (strengths, gaps, goals).
Consistency beats intensity — 30 minutes weekly outperforms quarterly bootcamps.
**Call scorecard:** opening and agenda → discovery depth → business impact quantified → decision process mapped → next steps committed → overall effectiveness.
Score 1–5; focus coaching on the lowest two dimensions.
Track improvement over time — coaching without measurement is just conversation.
## Common pitfalls

- **Pitching too early.** Presenting before understanding needs. Diagnose first, prescribe second.
- **Happy ears.** Hearing what you want in vague positive signals. Qualify hard: budget, authority, need, timeline.
- **Single-threaded deals.** One contact, no champion, no economic buyer access. Multi-thread or lose to "no decision."
- **Discounting as a reflex.** Dropping price instead of building value. Discounts train customers to negotiate everything.
- **No next step.** Ending calls with "I'll follow up" instead of a committed, dated action from both sides.
- **Avoiding the hard questions.** Budget, competition, decision process — uncomfortable questions asked early prevent painful surprises late.
- **Coaching the team identically.** Different sellers have different gaps. Diagnose individually, coach specifically.
- **Activity without outcomes.** Celebrating call volume while conversion stagnates. Coach the quality of conversations, not just the quantity.
- **One-time training.** A workshop without reinforcement fades in weeks. Coaching is weekly, specific, and tied to real deals.
- **Generic advice.** "Ask better questions" without specifics. Effective coaching is concrete: "ask about the cost of the status quo before presenting."
- **Only coaching strugglers.** Top performers need coaching too — on bigger deals, new skills, leadership. Neglect them and they plateau or leave.

Attribution

aicodedecodeaicodedecode
View sourceSee grades on GitHubMore from aicodedecode →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop caveman" or "normal mode".

1100021 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

698431 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3421 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Amp, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Grok Build, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

741 votes
View all in ai-agents →