Luopan Company Research
zhangxiaoqiang1991/luopan
罗盘的公司研究子模式。研究具体上市或非上市公司的财务增长、商业模式、 竞争生态位、治理与组织信号,并分别生成投资初筛和求职初筛。
Applies Neil Rackham's SPIN methodology (Situation/Problem/Implication/Need-payoff questions) to major B2B sales.
$ npx skills add getagentseal/founder-playbook --skill spin-selling -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install getagentseal/founder-playbook spin-selling --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ 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-srcUse ~/.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/
Install the "spin-selling" agent skill from https://github.com/getagentseal/founder-playbook/tree/main/skills/spin-selling into .claude/skills/spin-selling/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "spin-selling", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/getagentseal/founder-playbook/tree/main/skills/spin-sellingType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add getagentseal/founder-playbook --skill spin-selling -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install getagentseal/founder-playbook spin-selling --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/getagentseal/founder-playbook.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/spin-selling .agents/skills/spin-selling && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "spin-selling" agent skill from https://github.com/getagentseal/founder-playbook/tree/main/skills/spin-selling into .agents/skills/spin-selling/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "spin-selling", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add getagentseal/founder-playbook --skill spin-selling -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install getagentseal/founder-playbook spin-selling --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/getagentseal/founder-playbook.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/spin-selling .cursor/skills/spin-selling && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "spin-selling" agent skill from https://github.com/getagentseal/founder-playbook/tree/main/skills/spin-selling into .cursor/skills/spin-selling/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "spin-selling", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/getagentseal/founder-playbook.git --path skills/spin-selling--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add getagentseal/founder-playbook --skill spin-selling -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install getagentseal/founder-playbook spin-selling --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/getagentseal/founder-playbook.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/spin-selling .gemini/skills/spin-selling && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "spin-selling" agent skill from https://github.com/getagentseal/founder-playbook/tree/main/skills/spin-selling into .gemini/skills/spin-selling/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "spin-selling", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install getagentseal/founder-playbook spin-sellingInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add getagentseal/founder-playbook --skill spin-selling -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/getagentseal/founder-playbook.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/spin-selling .github/skills/spin-selling && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "spin-selling" agent skill from https://github.com/getagentseal/founder-playbook/tree/main/skills/spin-selling into .github/skills/spin-selling/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "spin-selling", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add getagentseal/founder-playbook --skill spin-selling -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install getagentseal/founder-playbook spin-selling --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/getagentseal/founder-playbook.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/spin-selling .opencode/skills/spin-selling && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "spin-selling" agent skill from https://github.com/getagentseal/founder-playbook/tree/main/skills/spin-selling into .opencode/skills/spin-selling/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "spin-selling", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
spin-sellingApplies 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. 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.
2 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit e811e63. It shows what the files ask for, not the result of running them.
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.
Shell commands in SKILL.md call:
justFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
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.
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.
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.
The full file from getagentseal/founder-playbook at commit e811e63, republished under its MIT licence (© getagentseal). 2,219 words, ~4,845 tokens.
.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.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.
"The closing techniques that can be effective in smaller accounts will actually lose you business as the sales grow larger." - Neil Rackham
Sales techniques that work in small sales (closing, objection handling, feature pitching) tend to backfire in large sales.
| Dimension | Small Sale | Large Sale |
|---|---|---|
| Selling cycle | Single call | Multi-call (months/years) |
| Decision maker | Individual | Multiple stakeholders |
| Customer's risk | Low (personal $) | High (career, public visibility) |
| Post-sale relationship | None | Ongoing |
| Need development | Instant | Slow, painful |
| Effective pressure | Yes (closing works) | No (closing backfires) |
| Top behavior | Closing/Features | Questioning/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.
| Stage | What Happens | Importance in Major Sales |
|---|---|---|
| 1. Preliminaries | Opening, warming up | LOW (≤20% of call time) |
| 2. Investigating | Asking questions to develop needs | HIGHEST (this is where you win) |
| 3. Demonstrating Capability | Showing your solution | Medium (only after needs developed) |
| 4. Obtaining Commitment | Getting next-step action | Low (good investigating makes this easy) |
Background facts about the customer's current situation.
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."
Probe for problems, difficulties, dissatisfactions.
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.
Take a problem and explore its EFFECTS, CONSEQUENCES, IMPLICATIONS.
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."
Get the customer to articulate the VALUE/BENEFITS of solving the problem.
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:
Critical: Don't ask NPQs about needs you CAN'T meet. Amplifies a need that benefits your competitor.
The hardest distinction. An 8-year-old solved it instantly:
"Implication Questions are always sad. Need-payoff Questions are always happy."
| Question Type | Focus | Tone |
|---|---|---|
| Implication | Problem-centered | Sad (makes problem bigger) |
| Need-payoff | Solution-centered | Happy (makes solution attractive) |
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/AdvanceSPIN is a guideline, not a rigid formula. Top performers use it flexibly. If the customer opens with an Explicit Need, jump to Need-payoff.
| Need Type | Definition | Example |
|---|---|---|
| Implied | Problems, difficulties, dissatisfactions | "Our system is unreliable" |
| Explicit | Specific wants, desires, intentions | "We need a more reliable system" |
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:
| Sales Type | Implied 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.
Traditional FAB training is wrong for major sales.
| Behavior | Definition | Small Sales | Large Sales |
|---|---|---|---|
| Features | Facts about the product | Slightly positive | Neutral or negative |
| Advantages | Show how product can be used or help | Positive | Slightly positive early, decreases over cycle |
| Benefits | Show how product meets an EXPLICIT NEED expressed by customer | Very positive | Very positive |
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."
Right (Benefit): Customer says: "We need a more reliable system." → Seller: "Our system is built specifically for reliability and would meet that need."
| Study | Finding |
|---|---|
| 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.
In a 575-call study (small-sale environment), success rates by closes per call:
Zero closing also fails. Even in major sales, you must propose SOME commitment. The right number is one - propose a clear, realistic next step.
Two characteristics of good commitment proposals:
| Outcome | Definition | Success? |
|---|---|---|
| Order | Firm commitment to buy | YES |
| Advance | Specific action moves sale forward | YES |
| Continuation | Sale continues, no specific action agreed | NO |
| No-sale | Customer actively refuses | NO |
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."
| 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, contrary to common belief, are more often CREATED BY THE SELLER than the customer."
| Seller Behavior | Most Probable Customer Response |
|---|---|
| Features | Price concerns |
| Advantages | Objections |
| Benefits | Approval |
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.
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.
Cure: Cut Features/Advantages. Add Problem, Implication, NPQ to build value.
"Work on one thing at a time, and get it right." - Tom Landry
200 golfers studied: 157 of 200 said they scored WORSE after their first lesson. The skill needs breaking in.
Don't worry about asking the perfect question. Ask LOTS of questions. Quality follows quantity.
"New skills go in SMALL accounts and well-known customers. Never in important sales."
| Phase | Focus |
|---|---|
| 1 | Just ask MORE questions (mostly Situation, that's fine) |
| 2 | Plan and ask Problem Questions (aim for 6+ per call) |
| 3 | Move to Implication Questions (after PQs feel comfortable) |
| 4 | Add Need-payoff Questions last |
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 fineAre 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 problemJust 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| Number | Rule |
|---|---|
| 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 |
| 3 | Minimum times to try a new behavior before judging |
| <10% | Major-account calls that result in Order or No-sale (rest = Advances/Continuations) |
| 7.8 | Average calls per major-sale cycle |
| 55% | Reduction in objections from objection-prevention training |
| 1 in 20 | Average questions that are Implication Questions in typical sales calls |
| 10x | Top performers ask this many more NPQs (rhetorical, no published baseline) |
Before every major-sales call:
During the call:
After the call:
"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.
| Context | Why SPIN Fails | Use Instead |
|---|---|---|
| Cold call (<2 min) | No time for chained questions | Hook + value prop + meeting ask |
| RFP procurement | Buyer wants price, not problems | Direct response + differentiation |
| PLG / freemium SaaS | User pre-qualified themselves | Activation + expansion playbook |
| Inbound MQL (read 4 assets) | Already in solution mode | Skip Investigating, fit/Benefit |
| Committee buying | Single-call SPIN insufficient | MEDDPICC + Champion enablement |
| Founder selling at $0-$1M | Optimization premature | Mom Test + offer iteration |
| Pure transactional <$50 | Small sales techniques work | Closing/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.
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
SKILL.md and 4 other files in skills/spin-selling of getagentseal/founder-playbook.
Open the folder on GitHubat commit e811e63
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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Spin Selling this skillgetagentseal/founder-playbook | 729 | — | ~4.8k | Automated safety check: Pass | MIT | |
| Luopan Company Researchzhangxiaoqiang1991/luopan | 389 | — | ~998 | Automated safety check: Pass | MIT | |
| Company Researchstophobia/deerflow2.0-enhanced | 821 | — | ~845 | Automated safety check: Pass | MIT | |
| Meeting Prep BriefBrianRWagner/ai-marketing-claude-code-skills | 440 | — | ~922 | Automated safety check: Pass | None | |
| SdtStopDisTrain/sdt-skills | 309 | — | ~535 | Automated safety check: Pass | MIT | |
| Account Researchextruct-ai/gtm-skills | 109 | — | ~1.6k | Automated safety check: Pass | None |
zhangxiaoqiang1991/luopan
罗盘的公司研究子模式。研究具体上市或非上市公司的财务增长、商业模式、 竞争生态位、治理与组织信号,并分别生成投资初筛和求职初筛。
stophobia/deerflow2.0-enhanced
综合企业背景调研技能,用于尽职调查、合作伙伴评估、投资分析、市场研究等场景。支持公司工商信息、财务数据、法律风险、舆情分析、竞品对比等多维度调研,自动生成Markdown和HTML格式的专业调研报告。触发条件:用户提及"企业调研"、"公司背景"、"尽职调查"、"合作伙伴评估"、"投资分析"、"市场研究"等关键词。
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.
StopDisTrain/sdt-skills
SDT 内容生产工具箱的总入口:根据当前任务选择最合适的 sdt- 模块,既能完成标题、开头等单一步骤,也能组织从账号研究到发布的完整流程。用户不知道该用哪个 SDT Skill,或希望一站式完成内容生产时使用。
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…
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.
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.
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.
getagentseal/founder-playbook
Frameworks from Kim & Mauborgne for creating uncontested market space and making competition irrelevant.
getagentseal/founder-playbook
Startup diagnostic router. An agent skill from getagentseal/founder-playbook.
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.
getagentseal/founder-playbook
Applies Eric Ries's Lean Startup methodology for building products under extreme uncertainty.
Categories
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.
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.
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.
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.
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.
Going by SKILL.md and its folder, Spin Selling needs the command-line tools its instructions call (just).
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.
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.
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.
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.
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.
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.