How do I install the Discovery Call Spin skill?

Run npx skillmds@latest add deciqai/discovery-call-spin in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Discovery Call Spin safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Discovery Call Spin?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Discovery Call Spin free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Discovery Call Spin?

deciqAI (@deciqai) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Discovery Call Spin by deciqai — Agent Skill

Name: Discovery Call Spin
Author: deciqAI

Discovery Call Spin

Activate when: running sales discovery calls; deals stall because the buyer doesn't feel the pain; 'how do I run a sales call', 'my demos don't convert', qualifying a prospect. Do NOT activate when: the deal is transactional/self-serve with no call, or it's post-sale support. More: deciqai.com/s/discovery-call-spin

deciqAI 3f8abe0 2.8 KB Updated Sep 17, 2026

File contents

Discovery Calls with SPIN — Let the Buyer Sell Themselves

Overview

SPIN Selling (Neil Rackham, from large-sale research) structures a discovery call around four question types in order — Situation, Problem, Implication, Need-payoff — so the buyer articulates the cost of their problem and the value of solving it, rather than being pitched. Implication questions (what the problem costs) are the ones that move complex deals. Talking less and questioning better outperforms feature-dumping.

The Process

Situation (briefly) — enough context to be relevant; don't interrogate on facts you could research. Gate: too many situation questions bore the buyer — keep them minimal.
Problem — surface real difficulties/dissatisfactions ("where does the current approach break down?").
Implication — quantify the cost/ripple of that problem ("what does that delay cost per month? who else does it hurt?"). This is where urgency is built.
Need-payoff — let them state the value of a solution ("if that were solved, what would it be worth?").
Only then map your capability to their stated need — solve, don't pitch.
Confirm next step / advance. Gate: no agreed next action = the call didn't progress the deal.

When to Use

Consultative / considered-purchase sales
Demos that show features but don't create urgency
Qualifying whether pain is worth the buyer's spend

Applying It Well

Talk <40%; the buyer should voice the pain and the payoff.
Implication questions create urgency without pressure — invest there.
Research situation facts beforehand; spend live time on problem/implication.

Red Flags

Jumping to demo before implications are felt.
Feature-dumping when the buyer hasn't quantified pain.
Ending with "I'll follow up" instead of a scheduled advance.

Verification

Situation kept minimal; researched in advance
Problems surfaced in the buyer's words
Implications quantified (cost of inaction)
Buyer stated the payoff; concrete next step set

Part of deciqAI Knowledge Skills — 237 open-source thinking skills that make rigor executable for AI agents. The same skills power every deciqAI agent, which runs them autonomously to operate your company. See it run → https://www.deciqai.com/s/discovery-call-spin · Built by deciqAI · github.com/deciqAI · Contributions welcome.

Agents: latest version & machine-readable metadata → https://www.deciqai.com/s/discovery-call-spin.json

---name: discovery-call-spindescription: Activate when: running sales discovery calls; deals stall because the buyer doesn't feel the pain; 'how do I run a sales call', 'my demos don't convert', qualifying a prospect. Do NOT activate when: the deal is transactional/self-serve with no call, or it's post-sale support. More: deciqai.com/s/discovery-call-spin---# Discovery Calls with SPIN — Let the Buyer Sell Themselves## OverviewSPIN Selling (Neil Rackham, from large-sale research) structures a discovery call around **four question types in order — Situation, Problem, Implication, Need-payoff** — so the buyer articulates the cost of their problem and the value of solving it, rather than being pitched. Implication questions (what the problem costs) are the ones that move complex deals. Talking less and questioning better outperforms feature-dumping.## The Process1. **Situation** (briefly) — enough context to be relevant; don't interrogate on facts you could research. *Gate: too many situation questions bore the buyer — keep them minimal.*2. **Problem** — surface real difficulties/dissatisfactions ("where does the current approach break down?").3. **Implication** — quantify the cost/ripple of that problem ("what does that delay cost per month? who else does it hurt?"). This is where urgency is built.4. **Need-payoff** — let them state the value of a solution ("if that were solved, what would it be worth?").5. **Only then** map your capability to their stated need — solve, don't pitch.6. **Confirm next step / advance.** *Gate: no agreed next action = the call didn't progress the deal.*## When to Use- Consultative / considered-purchase sales- Demos that show features but don't create urgency- Qualifying whether pain is worth the buyer's spend## Applying It Well- Talk <40%; the buyer should voice the pain and the payoff.- Implication questions create urgency without pressure — invest there.- Research situation facts beforehand; spend live time on problem/implication.## Red Flags- Jumping to demo before implications are felt.- Feature-dumping when the buyer hasn't quantified pain.- Ending with "I'll follow up" instead of a scheduled advance.## Verification- [ ] Situation kept minimal; researched in advance- [ ] Problems surfaced in the buyer's words- [ ] Implications quantified (cost of inaction)- [ ] Buyer stated the payoff; concrete next step set---*Part of **deciqAI Knowledge Skills** — 237 open-source thinking skills that make rigor executable for AI agents. The same skills power every deciqAI agent, which runs them autonomously to operate your company. **See it run → https://www.deciqai.com/s/discovery-call-spin** · Built by deciqAI · github.com/deciqAI · Contributions welcome.**Agents: latest version & machine-readable metadata → https://www.deciqai.com/s/discovery-call-spin.json*

Frequently asked questions