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

Discovery Coach

ASecurity

Use when an org role acts as discovery coach and must improve reps' sales discovery calls with SPIN, MEDDIC or BANT qualification and call scorecards. Sales discovery, not product discovery (see product-discovery).

21 stars
0 votes
0 copies
0 views
Added 9/22/2026
ai-agentsrustgogit

Security Analysis

A100/100

Scanned 9/28/2026

$npx -y skills add monoes/monomind --skill discovery-coach --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Discovery Coach?

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

Security grade badge for Discovery Coach
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/monoes-discovery-coach/badge)](https://www.skillsdirectory.com/skills/monoes-discovery-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: discovery-coach
description: "Use when an org role acts as discovery coach and must improve reps' sales discovery calls with SPIN, MEDDIC or BANT qualification and call scorecards. Sales discovery, not product discovery (see product-discovery)."
tags: ["sales","customer-research","communication"]
tools: []
license: Apache-2.0
source: https://github.com/monoes/monomind
---
# Discovery Coach — Best Practices

## Focus
Sharpens how reps run discovery calls — the questions they ask, the depth they go to, and the qualification rigor — since discovery quality predicts win rate more than almost any other sales skill.

## Best practices
- Push reps toward the proven question arc: Situation → Problem → Implication → Vision/Need-payoff (SPIN), rather than jumping straight to pitching a solution.
- Target roughly an 80/20 open-to-closed question ratio, and coach toward 11-14 substantive questions per call rather than a rushed five-minute checklist.
- Emphasize implication questions specifically — top performers ask far more of these than average reps, and they correlate strongly with win rate and deal size.
- Require real pre-call preparation; asking questions whose answers are obvious from public info signals no homework and erodes buyer trust immediately.
- Coach toward listening, not talking — buyers consistently rank "listen to my needs" as their top ask, and talk-ratio is one of the most fixable, highest-leverage metrics.
- Anchor every discovery call to a qualification framework (MEDDIC or BANT) so reps leave with Metrics, Economic Buyer, Decision Criteria/Process — not just vague interest.
- Review calls with structured scorecards mapped to the chosen methodology, not gut-feel impressions.
- Reinforce that the goal of discovery is diagnosis, not qualification theater — the rep should be able to state the customer's problem back better than the customer can.

## Common pitfalls
- Reps pitching too early, before the customer's actual pain, priority, and buying process are understood.
- Surface-level situation questions without ever pushing into implication/impact — leaves the business case fuzzy for the customer.
- Skipping economic-buyer and decision-process questions, leading to deals that stall in "no decision" because the real buyer was never engaged.
- Treating discovery as a one-time call instead of an ongoing thread refined throughout the deal cycle.

## Tools & techniques
- SPIN and MEDDIC/BANT as the two core qualification lenses — pick one as primary and coach consistently against it.
- Discovery call scorecards scoring question mix (situation/problem/implication/vision), talk ratio, and qualification field completeness.
- Call recording + transcript review for implication-question frequency, a strong leading indicator of win rate.
- Standard discovery question bank, refreshed from what's actually working in recent won deals.

Attribution

monoesmonoes
View sourceSee grades on GitHubMore from monoes →
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', ...

698621 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 →