Agent skill

Spin Selling

by getagentseal in getagentseal/founder-playbook

Applies Neil Rackham's SPIN methodology (Situation/Problem/Implication/Need-payoff questions) to major B2B sales.

MITAuto-check passedSales & Support

Install Spin Selling

skills CLI
$ npx skills add getagentseal/founder-playbook --skill spin-selling -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install getagentseal/founder-playbook spin-selling --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/getagentseal/founder-playbook.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/spin-selling .claude/skills/spin-selling && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
spin-selling
GitHub stars
729
Token cost
~4.8k tokens
SKILL.md length
2,219 words
Files
5
Skills in repo
16
Repo updated
First seen
Licence
MIT

At a glance

Applies Neil Rackham's SPIN methodology (Situation/Problem/Implication/Need-payoff questions) to major B2B sales.

  • Works in 2 steps: Shifts attention from problem (negative)… → Customer tells YOU the benefits - far…
  • Complex multi-call sales cycles
  • SKILL.md covers Core Insight, The 4 Stages of Every Sales Call, SPIN: The 4 Question Types and The SPIN Logic Chain, plus 8 more sections
  • Calls just

What it does

Spin Selling is an agent skill from getagentseal/founder-playbook. Applies Neil Rackham's SPIN methodology (Situation/Problem/Implication/Need-payoff questions) to major B2B sales. Use for complex multi-call sales cycles, enterprise deals where the customer must justify the decision to others, when objections are mounting, when calls end in vague continuations instead of advances, when traditional closing techniques are backfiring on large deals, or when designing discovery-call structure. Triggers include 'my deal isn't closing', 'too many objections', 'B2B sales coaching'…

Its SKILL.md is about 4.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files (for example `cases.md`, `examples.md` and `frameworks.md`).

It sits in Sales & Support, covering Sales call preparation. The repository describes itself as: 15 proven business books distilled into AI-native skills. Works with Claude Code, ChatGPT, Gemini, Cursor. The licence is MIT.

When your agent uses it

  • Complex multi-call sales cycles
  • Enterprise deals where the customer must justify the decision to others
  • Objections are mounting
  • Calls end in vague continuations instead of advances

Example prompts

  • “my deal isn”
  • “too many objections”
  • “B2B sales coaching”
  • “/spin-selling”

Workflow steps

2 steps, taken from the first numbered list in SKILL.md.

  1. Shifts attention from problem (negative) to solution (positive)
  2. Customer tells YOU the benefits - far more persuasive

What it can do on your machine

Read from SKILL.md and the folder at commit e811e63. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • just

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Spin Selling loads about 4.8k tokens when it runs. Until then it costs about 170 tokens; SKILL.md has 2,219 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~170
When it runs · the whole SKILL.md, loaded when a task matches
~4.8k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from getagentseal/founder-playbook at commit e811e63, republished under its MIT licence (© getagentseal). 2,219 words, ~4,845 tokens.

Download SKILL.mdSave it as .claude/skills/spin-selling/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.
name
spin-selling
description
Applies Neil Rackham's SPIN methodology (Situation/Problem/Implication/Need-payoff questions) to major B2B sales. Use for complex multi-call sales cycles, enterprise deals where the customer must justify the decision to others, when objections are mounting, when calls end in vague continuations instead of advances, when traditional closing techniques are backfiring on large deals, or when designing discovery-call structure. Triggers include 'my deal isn't closing', 'too many objections', 'B2B sales coaching', 'discovery call structure', 'stuck in the middle of the sale'. Not for transactional sub-$50 sales, pure consumer impulse, or PLG self-serve products.

Note: This skill is independent analysis and commentary, not a reproduction of the original text. It synthesizes the book's core ideas with modern startup practice, surfaces where frameworks are outdated or incomplete, and integrates perspectives from adjacent disciplines. For the full argument and context, read the original book.

SPIN Selling

"The closing techniques that can be effective in smaller accounts will actually lose you business as the sales grow larger." - Neil Rackham

Core Insight

Sales techniques that work in small sales (closing, objection handling, feature pitching) tend to backfire in large sales.

DimensionSmall SaleLarge Sale
Selling cycleSingle callMulti-call (months/years)
Decision makerIndividualMultiple stakeholders
Customer's riskLow (personal $)High (career, public visibility)
Post-sale relationshipNoneOngoing
Need developmentInstantSlow, painful
Effective pressureYes (closing works)No (closing backfires)
Top behaviorClosing/FeaturesQuestioning/Need development

Decision rule: If you can't complete the sale in a single call, or if the customer must justify the decision to others, you're in a major sale. Use SPIN.


The 4 Stages of Every Sales Call

StageWhat HappensImportance in Major Sales
1. PreliminariesOpening, warming upLOW (≤20% of call time)
2. InvestigatingAsking questions to develop needsHIGHEST (this is where you win)
3. Demonstrating CapabilityShowing your solutionMedium (only after needs developed)
4. Obtaining CommitmentGetting next-step actionLow (good investigating makes this easy)

SPIN: The 4 Question Types

S - Situation Questions

Background facts about the customer's current situation.

  • "What equipment are you using now?"
  • "How long have you had it?"

Research finding: Negatively related to success. Inexperienced sellers ask too many.

Rule: Minimum needed. Do homework first - never ask what you could research. Each must have a specific purpose.

"There's a special place in hell reserved for wicked salespeople where they sit for all eternity being forced to answer their own Situation Questions."

P - Problem Questions

Probe for problems, difficulties, dissatisfactions.

  • "Are you satisfied with your present equipment?"
  • "What disadvantages does this approach have?"
  • "Is reliability an issue?"

Research finding: Strong predictor in small sales. Foundational in large sales but not sufficient alone.

Rule: Aim for 6+ Problem Questions per call. Plan 3+ problems your product can solve before each call. Inexperienced sellers don't ask enough because they fear offending the customer.

I - Implication Questions

Take a problem and explore its EFFECTS, CONSEQUENCES, IMPLICATIONS.

  • "What effect does that have on output?"
  • "What's the cost of doing nothing?"
  • "Could this affect your competitiveness?"

Research finding: Strongest predictor of success in major sales. Only 1 in 20 questions in average sales call is an Implication Question. Harder to ask. MUST be planned in advance.

Purpose: Take a problem the buyer perceives as small and build it large enough to justify expensive action.

"Even the smartest people we've studied find it hard to ask Implication Questions unless they've planned them in advance."

N - Need-Payoff Questions (NPQ)

Get the customer to articulate the VALUE/BENEFITS of solving the problem.

  • "How would solving this help you?"
  • "Why is that important?"
  • "Would it be useful if...?"
  • "What other ways could this help?"

Research finding: Top performers ask materially more NPQs than average reps (Rackham's "10x" figure is rhetorical, no published baseline). Calls with high NPQs are rated by customers as POSITIVE, CONSTRUCTIVE, HELPFUL.

Two effects:

  1. Shifts attention from problem (negative) to solution (positive)
  2. Customer tells YOU the benefits - far more persuasive

Critical: Don't ask NPQs about needs you CAN'T meet. Amplifies a need that benefits your competitor.

Quincy's Rule (Implication vs Need-payoff)

The hardest distinction. An 8-year-old solved it instantly:

"Implication Questions are always sad. Need-payoff Questions are always happy."

Question TypeFocusTone
ImplicationProblem-centeredSad (makes problem bigger)
Need-payoffSolution-centeredHappy (makes solution attractive)

The SPIN Logic Chain

Situation (background) → Problem (find difficulty) →
Implied Need ("we have this problem") →
Implication (make it bigger) → Need-payoff (build value of solving) →
Explicit Need ("I want X") → Benefit ("we deliver X") →
Order/Advance

SPIN is a guideline, not a rigid formula. Top performers use it flexibly. If the customer opens with an Explicit Need, jump to Need-payoff.


Implied vs Explicit Needs (The Key Distinction)

Two Categories Used in Practice
Need TypeDefinitionExample
ImpliedProblems, difficulties, dissatisfactions"Our system is unreliable"
ExplicitSpecific wants, desires, intentions"We need a more reliable system"
Buying Signals - Critical Distinction

In major sales, Implied Needs are NOT buying signals. Inexperienced reps misread "we have a problem with X" as a buy signal. It isn't.

The real buying signal in major sales is an Explicit Need:

  • "We're going to do something about X"
  • "We're looking for a system with these characteristics"
Research Statistics
Sales TypeImplied Needs Predict Success?Explicit Needs Predict Success?
Small (646 deals)YES (2x more in successful)Less critical
Large (1,406 deals, $27K avg)NO (no correlation)YES (2x more in successful)

The fundamental insight: In major sales, success comes from CONVERTING Implied Needs into Explicit Needs using Implication and NPQs.


FAB Redefined (Features / Advantages / Benefits)

Traditional FAB training is wrong for major sales.

BehaviorDefinitionSmall SalesLarge Sales
FeaturesFacts about the productSlightly positiveNeutral or negative
AdvantagesShow how product can be used or helpPositiveSlightly positive early, decreases over cycle
BenefitsShow how product meets an EXPLICIT NEED expressed by customerVery positiveVery positive
The Critical Definition Difference

Most sales training calls "Type A Benefits" what Rackham calls Advantages (showing how product helps). True Benefits require the customer to FIRST express an Explicit Need.

Wrong (Advantage): "Because our system uses high-reliability components, it solves your reliability problem."

  • Reliability problem is an Implied Need (not yet Explicit).

Right (Benefit): Customer says: "We need a more reliable system." → Seller: "Our system is built specifically for reliability and would meet that need."


Closing: The Counterintuitive Truth

StudyFinding
Office equipment (190 calls)High-close: 37% success. Low-close: 70% success
Photo store (cheap goods)Closing increased success: 72% → 76%
Photo store (expensive goods)Closing DECREASED success: 42% → 33%
Customer satisfaction (n=145)Closed customers: 5.8/10. Non-closed: 7.7/10
Professional buyer survey (n=54)34 of 54 said closing makes them LESS likely to buy

Pressure rule: Pressure helps with small decisions, hurts with large ones.

The American Airlines Counter-Finding (Important Caveat)

In a 575-call study (small-sale environment), success rates by closes per call:

  • 0 closes: 22% success
  • 1 close: 61% success (peak)
  • 2 closes: ~40%
  • 3+ closes: <20%

Zero closing also fails. Even in major sales, you must propose SOME commitment. The right number is one - propose a clear, realistic next step.

What Top Performers Do Instead (Obtaining Commitment)
  1. Concentrate Attention on Investigating - "You don't require closing techniques with a customer who wants to buy."
  2. Check That Key Concerns Are Covered - "Before we go further, could I check whether there are any areas you'd like me to tell you more about?"
  3. Summarize the Benefits - in long calls customers lose track
  4. Propose a Commitment (Don't Ask, Tell) - "Then the most logical next step would be for you and your accountant to come and see one of these systems in operation."

Two characteristics of good commitment proposals:

  1. The commitment ADVANCES the sale
  2. It's the HIGHEST realistic commitment the customer can give

The 4 Possible Call Outcomes

OutcomeDefinitionSuccess?
OrderFirm commitment to buyYES
AdvanceSpecific action moves sale forwardYES
ContinuationSale continues, no specific action agreedNO
No-saleCustomer actively refusesNO

Examples of Advances: demo attendance, intro to higher decision-maker, agreed trial, technical-team meeting, letter of intent.

Examples of Continuations (DEADLY): "Thank you, please visit again," "Fantastic presentation. Let's meet again sometime," "We liked it. We'll be in touch."

Decision rule: Judge call success by customer ACTIONS, not WORDS. Compliments are not a sign of success.

"In most major-account sales forces, fewer than 10% of calls result in an Order or No-sale."


Setting Call Objectives

Bad (Continuation)Good (Advance)
"Build the relationship""Get her to come to the demo"
"Collect information""Get a meeting with his boss"
"Make a good impression""Get an introduction to Planning"

"If a call's worth making, it's got to do something - to push the sale forward."


Objections: Prevention vs Handling

"Objections, contrary to common belief, are more often CREATED BY THE SELLER than the customer."

Show full SKILL.md (887 more words)Show less
The Linda Marsh Correlation
Seller BehaviorMost Probable Customer Response
FeaturesPrice concerns
AdvantagesObjections
BenefitsApproval

Pattern: Problem Question → Implied Need → Advantage → Objection.

When you offer a solution before the customer feels the problem deeply, they push back. The cost feels too high relative to the developed need.

The Bold Experiment

Selected 8 salespeople with 10x average objection rates. Trained them in objection PREVENTION. Taught SPIN questioning to develop Explicit Needs and offer Benefits. Result: 55% reduction in objections.

Two Sure Signs You're Causing Objections
  1. Objections early in the call = talking solutions before developing needs
  2. Objections about value ("It's too expensive") = need not built strongly enough

Cure: Cut Features/Advantages. Add Problem, Implication, NPQ to build value.


Opening the Call (Preliminaries)

What Doesn't Work in Major Sales
  1. Relating to personal interests (golf trophy, family photo) - senior buyers don't care about your golf game
  2. Opening benefit statements ("Let me show you how to save thousands...") - traps you into early product details
What Works - Three Things to Establish
  1. Who you are
  2. Why you're there (NOT product details)
  3. Your right to ask questions
Three Rules
  1. Get down to business quickly - ≤20% of call time on Preliminaries
  2. Don't talk about solutions too soon - no products in the first half
  3. Concentrate on questions, not openings - plan questions, not opening lines

How to Implement: 4 Golden Rules of Skill Learning

Rule 1: Practice Only ONE Behavior at a Time

"Work on one thing at a time, and get it right." - Tom Landry

Rule 2: Try the New Behavior at Least 3 Times

200 golfers studied: 157 of 200 said they scored WORSE after their first lesson. The skill needs breaking in.

Rule 3: Quantity Before Quality

Don't worry about asking the perfect question. Ask LOTS of questions. Quality follows quantity.

Rule 4: Practice in SAFE Situations

"New skills go in SMALL accounts and well-known customers. Never in important sales."

Implementation Sequence
PhaseFocus
1Just ask MORE questions (mostly Situation, that's fine)
2Plan and ask Problem Questions (aim for 6+ per call)
3Move to Implication Questions (after PQs feel comfortable)
4Add Need-payoff Questions last

Decision Trees

"Is this a major sale?"
Will it complete in a single call?
├─ YES → Small sale. Use traditional techniques (close, features, etc.)
└─ NO  → Will customer need to justify to others?
        ├─ YES → Major sale. Use SPIN.
        └─ NO  → Is the spend significant ($) for the buyer?
                ├─ YES → Use SPIN-lite (PQ + needs)
                └─ NO  → Small sale techniques fine
"Why isn't this deal closing?"
Are you getting lots of objections?
├─ YES → Likely cause: too many Advantages too early
│        Cut Features/Advantages, add PQ/IQ/NPQ
└─ NO  → Are calls ending in Continuations (no specific next step)?
        ├─ YES → Call objectives are weak. Set Advance objectives.
        └─ NO  → Is customer not feeling enough urgency?
                └─ Add Implication Questions to develop the problem
"When to use which question type?"
Just met customer / new to account?
├─ Light on Situation Questions (do homework first)
└─ Started conversation?
   ├─ Customer aware of problems → Problem Questions
   ├─ Customer dismissive of severity → Implication Questions
   └─ Customer excited about solving → Need-payoff Questions

Critical Numbers & Rules of Thumb

NumberRule
27%Sales lift gap (Motorola, dollar value) - see cases.md for full breakdown and caveats
63%New-business order increase from SPIN training (Motorola) - see cases.md
6+Problem Questions per call - quantity target
20%Maximum % of call time spent on Preliminaries
3Minimum times to try a new behavior before judging
<10%Major-account calls that result in Order or No-sale (rest = Advances/Continuations)
7.8Average calls per major-sale cycle
55%Reduction in objections from objection-prevention training
1 in 20Average questions that are Implication Questions in typical sales calls
10xTop performers ask this many more NPQs (rhetorical, no published baseline)

Quick Reference Checklist

Before every major-sales call:

  • Researched enough to skip basic Situation Questions
  • Planned 3+ Problem Questions
  • Planned Implication Questions for each problem
  • Planned a few Need-payoff Questions
  • Set OBJECTIVE that requires customer action (Advance, not Continuation)
  • Planned how to summarize and propose commitment

During the call:

  • Preliminaries <20% of time
  • Asking questions, not telling
  • Building need with Implications before offering solutions
  • Converting Implied Needs into Explicit Needs
  • Asking NPQs to make customer articulate value

After the call:

  • Got an Order or Advance? (or just a Continuation?)
  • Which specific question had most impact?
  • What would I do differently next time?

The Big Idea

"Success rests on minute behavioral details. The hundreds of minute behavioral details in a call decide whether it succeeds."

The win isn't the close. It isn't the personality. It isn't the strategy. It's the questions you ask.


Supporting Files

  • frameworks.md - Full 3-stage need development model, value equation, FAB extended, BP buyer anecdote, "plan-do-review" loop, common mistakes (18-item list)
  • cases.md - Easiflo $120K canonical chained-Implication transcript; British Petroleum yacht photo; Tom Landry skill-learning case; Quincy's Rule origin; failed validation attempts (intellectual honesty)
  • examples.md - Question-planning templates; Implication Question generator; NPQ stock library; pre-call planning sheet; post-call review template
  • integration.md - Adaptation for B2C/SaaS/cultural contexts (Fuji Xerox 74% Japan study), competing methodologies (Challenger/MEDDPICC/Sandler/Gap Selling), conflicts with Mom Test/$100M Offers/Crossing the Chasm, evidence and limitations

When SPIN Fails (Don't Use Here)

ContextWhy SPIN FailsUse Instead
Cold call (<2 min)No time for chained questionsHook + value prop + meeting ask
RFP procurementBuyer wants price, not problemsDirect response + differentiation
PLG / freemium SaaSUser pre-qualified themselvesActivation + expansion playbook
Inbound MQL (read 4 assets)Already in solution modeSkip Investigating, fit/Benefit
Committee buyingSingle-call SPIN insufficientMEDDPICC + Champion enablement
Founder selling at $0-$1MOptimization prematureMom Test + offer iteration
Pure transactional <$50Small sales techniques workClosing/Features fine
Highly technical to expert buyer"Just show me the product"Lead with Features (the "Features appetite")

Full table and modern (post-1988) adaptations: see integration.md.


Note on Evidence

SPIN's empirical base is largely Huthwaite-internal: ~35,000 calls of broader research across 27 countries, but only n=42 (Motorola Canada) and n=55 (Multinational Business-Machines) are clean SPIN-specific validation studies. Both showed real productivity gains. No independent peer-reviewed replication. Treat SPIN as a strong prior for major sales, not gospel. Full evidence detail and Rackham's 6 failed validation attempts: see integration.md. For the Motorola validation study and its caveats, see cases.md.

© getagentseal, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 4 other files in skills/spin-selling of getagentseal/founder-playbook.

  • SKILL.md
  • cases.md
  • examples.md
  • frameworks.md
  • integration.md

Open the folder on GitHubat commit e811e63

Compare with similar skills

Spin Selling next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Spin Selling compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Spin Selling this skillgetagentseal/founder-playbook729—~4.8kAutomated safety check: PassMIT
Luopan Company Researchzhangxiaoqiang1991/luopan389—~998Automated safety check: PassMIT
Company Researchstophobia/deerflow2.0-enhanced821—~845Automated safety check: PassMIT
Meeting Prep BriefBrianRWagner/ai-marketing-claude-code-skills440—~922Automated safety check: PassNone
SdtStopDisTrain/sdt-skills309—~535Automated safety check: PassMIT
Account Researchextruct-ai/gtm-skills109—~1.6kAutomated safety check: PassNone

Similar skills

  • Luopan Company Research

    zhangxiaoqiang1991/luopan

    罗盘的公司研究子模式。研究具体上市或非上市公司的财务增长、商业模式、 竞争生态位、治理与组织信号,并分别生成投资初筛和求职初筛。

    389 GitHub stars~998 tokensUpdated 2 mo ago
    Sales & SupportAuto-check passed
  • Company Research

    stophobia/deerflow2.0-enhanced

    综合企业背景调研技能,用于尽职调查、合作伙伴评估、投资分析、市场研究等场景。支持公司工商信息、财务数据、法律风险、舆情分析、竞品对比等多维度调研,自动生成Markdown和HTML格式的专业调研报告。触发条件:用户提及"企业调研"、"公司背景"、"尽职调查"、"合作伙伴评估"、"投资分析"、"市场研究"等关键词。

    821 GitHub stars~845 tokensUpdated 6 mo ago
    Sales & SupportAuto-check passed
  • Meeting Prep Brief

    BrianRWagner/ai-marketing-claude-code-skills

    Builds a pre-meeting brief from your Obsidian vault: participant research, past notes, open commitments, a prioritized agenda and sharp questions.

    440 GitHub stars~922 tokensUpdated 6 mo ago
    Sales & SupportAuto-check passed
  • Sdt

    StopDisTrain/sdt-skills

    SDT 内容生产工具箱的总入口:根据当前任务选择最合适的 sdt- 模块,既能完成标题、开头等单一步骤,也能组织从账号研究到发布的完整流程。用户不知道该用哪个 SDT Skill,或希望一站式完成内容生产时使用。

    309 GitHub stars~535 tokensUpdated 1 mo ago
    Sales & SupportAuto-check passed
  • Account Research

    extruct-ai/gtm-skills

    Deep-research a single target account into a decision-ready dossier: the entity tree, the buying units and decision-makers, live signals (open/closed roles, leadership moves, news, tech stack), and…

    109 GitHub stars~1.6k tokensUpdated 11 days ago
    Sales & SupportAuto-check passed
  • Call Prep

    breakstageaxe61/genspark-claw

    Prepare an AI phone call end-to-end — research the callee, set a concrete objective and fallback, draft a natural call script with branching, and produce a post-call summary template.

    159 GitHub stars~986 tokensUpdated 13 days ago
    Sales & SupportAuto-check passed

More from getagentseal/founder-playbook

All 16 skills in this repo
  • 100m Leads

    getagentseal/founder-playbook

    Builds lead generation systems using Alex Hormozi's Core Four framework (warm outreach, content, cold outreach, paid ads), lead magnets, and Rule of 100.

    729 GitHub stars~2.3k tokensUpdated 3 days ago
    Auto-check passed
  • 100m Offers

    getagentseal/founder-playbook

    Designs irresistible Grand Slam Offers using Alex Hormozi's value equation, obstacle-solution mapping, value-cost trim/stack, and offer-naming patterns.

    729 GitHub stars~2.7k tokensUpdated 3 days ago
    Auto-check passed
  • Blue Ocean Strategy

    getagentseal/founder-playbook

    Frameworks from Kim & Mauborgne for creating uncontested market space and making competition irrelevant.

    729 GitHub stars~3.1k tokensUpdated 3 days ago
    Auto-check passed
  • Diagnose

    getagentseal/founder-playbook

    Startup diagnostic router. An agent skill from getagentseal/founder-playbook.

    729 GitHub stars~2.6k tokensUpdated 3 days ago
    Auto-check passed
  • Influence

    getagentseal/founder-playbook

    Cialdini's seven principles of compliance (the classic six — reciprocation, commitment-consistency, social proof, liking, authority, scarcity — plus Unity, added 2016) and Pre-Suasion.

    729 GitHub stars~3.8k tokensUpdated 3 days ago
    Auto-check passed
  • Lean Startup

    getagentseal/founder-playbook

    Applies Eric Ries's Lean Startup methodology for building products under extreme uncertainty.

    729 GitHub stars~4.6k tokensUpdated 3 days ago
    Auto-check passed

Categories

Questions about Spin Selling

What does Spin Selling do?

Applies Neil Rackham's SPIN methodology (Situation/Problem/Implication/Need-payoff questions) to major B2B sales. Spin Selling is an agent skill from getagentseal/founder-playbook. Applies Neil Rackham's SPIN methodology (Situation/Problem/Implication/Need-payoff questions) to major B2B sales.

When should I use Spin Selling?

Spin Selling fits situations like: complex multi-call sales cycles; enterprise deals where the customer must justify the decision to others; objections are mounting; calls end in vague continuations instead of advances.

How do I install Spin Selling in Claude Code?

Run `npx skills add getagentseal/founder-playbook --skill spin-selling -a claude-code`. Or copy the skill folder (skills/spin-selling in getagentseal/founder-playbook) into .claude/skills/spin-selling in your project. Claude Code loads it when a task matches its description.

How do I install Spin Selling in Codex?

Run `npx skills add getagentseal/founder-playbook --skill spin-selling -a codex`. Or copy the skill folder (skills/spin-selling in getagentseal/founder-playbook) into .agents/skills/spin-selling in your project. Codex loads it when a task matches its description.

Can I use Spin Selling in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add getagentseal/founder-playbook --skill spin-selling -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/spin-selling, .gemini/skills/spin-selling, .github/skills/spin-selling and .opencode/skills/spin-selling in your project.

What does Spin Selling need to run?

Going by SKILL.md and its folder, Spin Selling needs the command-line tools its instructions call (just).

Does Spin Selling access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Spin Selling safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Spin Selling use?

Spin Selling is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Spin Selling use?

About 4.8k tokens (SKILL.md is roughly 19k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Spin Selling?

Skills that share tags, products or a category with Spin Selling: Luopan Company Research (zhangxiaoqiang1991/luopan, 389 stars), Company Research (stophobia/deerflow2.0-enhanced, 821 stars), Meeting Prep Brief (BrianRWagner/ai-marketing-claude-code-skills, 440 stars) and Sdt (StopDisTrain/sdt-skills, 309 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Spin Selling?

getagentseal (a GitHub organization) maintains it in getagentseal/founder-playbook, which has 729 GitHub stars. The repository holds 16 skills in this directory. The repository was last updated on October 6, 2026.

Source: getagentseal/founder-playbook on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.