Token导航 LogoToken导航

Agent Skill · 研究检索

sales-playbook(销售手册)

sales-playbook 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

sales-playbook 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为只读;许可证信息还不明确,第三方扫描已通过,按安装量在研究检索类的 73,675 个 Skill 里排第 65,084。

总安装 288周安装 12GitHub Stars 6下载 96核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:sales-playbook(销售手册)
来源仓库:https://github.com/sunnypatneedi/claude-starter-kit
仓库路径:skills/sales-playbook
安装命令:
npx skills add https://github.com/sunnypatneedi/claude-starter-kit --skill sales-playbook
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/sunnypatneedi/claude-starter-kit --skill sales-playbook

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

sales-playbook 用于查找、检索和筛选相关信息。适用于根据关键词、任务场景或来源线索快速定位候选结果。通过 npx skills add 命令从指定 GitHub 仓库安装并使用。安装前需确认权限范围、维护状态及是否触发联网或文件操作。建议结合原始 README 进一步核验具体功能和使用边界。

来源仓库内路径:skills/sales-playbook

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/sunnypatneedi/claude-starter-kit --skill sales…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它标注为只读,先用只读任务试一次,确认行为符合预期再扩大使用范围。

常见问题

6 条

sales-playbook 怎么安装?

在终端执行 npx skills add https://github.com/sunnypatneedi/claude-starter-kit --skill sales-playbook。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

sales-playbook 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

sales-playbook 需要什么权限?

权限级别是只读。该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

sales-playbook 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

sales-playbook 用的人多吗?

公开数据是累计安装 288 次,近一周安装 12 次,下载 96 次,GitHub 6 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

sales-playbook 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。
  • 标注为只读权限,试用阶段不容易误改本地文件。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。
  • 只想先试试效果、不希望它改动本地文件的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
sales-playbook

销售手册 · 本页

2886只读未明确通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

Sales Playbook

Complete framework for building scalable, repeatable sales systems that convert prospects to customers.

When to Use

  • Building sales process for new product
  • Onboarding sales team members
  • Improving conversion rates
  • Handling objections consistently
  • Managing sales pipeline
  • Scaling from founder-led to team sales

Sales Process Stages

PROSPECT → QUALIFY → DISCOVER → PRESENT → HANDLE OBJECTIONS → CLOSE → ONBOARD

1. PROSPECT: Find potential customers
2. QUALIFY: Determine fit (BANT/MEDDIC)
3. DISCOVER: Understand their situation
4. PRESENT: Show how you solve their problem
5. HANDLE OBJECTIONS: Address concerns
6. CLOSE: Ask for the business
7. ONBOARD: Ensure success

Workflow

Step 1: Define Your Ideal Customer Profile (ICP)

## Ideal Customer Profile

**Demographics:**
- Company size: [Employees/Revenue]
- Industry: [Specific verticals]
- Geography: [Locations]
- Role/Title: [Who you sell to]

**Firmographics:**
- Technology stack: [What they use]
- Growth stage: [Startup/Scale-up/Enterprise]
- Funding: [Bootstrapped/VC-backed]

**Psychographics:**
- Pain points: [Top 3 problems]
- Goals: [What they're trying to achieve]
- Buying triggers: [When they buy]
- Budget: [Price range they can afford]

**Examples of Good Fit:**
- Company A: [Why they're ideal]
- Company B: [Why they're ideal]

**Examples of Bad Fit:**
- Company X: [Why they're not a fit]
- Company Y: [Why they're not a fit]

Step 2: Craft Your Value Proposition

Value Prop Framework:

FOR [target customer]
WHO [has this specific problem]
OUR [product/service]
PROVIDES [key benefit with numbers]
UNLIKE [competitors]
WE [unique differentiator]

Example:

FOR B2B SaaS companies
WHO struggle with customer onboarding (60% churn in first 30 days)
OUR automated onboarding platform
PROVIDES 40% reduction in time-to-value and 25% higher retention
UNLIKE generic customer success tools
WE offer industry-specific playbooks and automated milestone tracking

One-Liner:

"We help [target] achieve [outcome] without [pain]."

Example: "We help SaaS companies reduce churn by 25% without hiring more customer success reps."

Step 3: Qualification (BANT vs MEDDIC)

BANT (Simpler, B2C/SMB):

## BANT Qualification

**Budget:**
- Can they afford it? $[Range]
- What's their budget? $[X]
- Decision authority over budget? [Y/N]

**Authority:**
- Who makes the decision? [Name/Title]
- Who else is involved? [Stakeholders]
- Decision process? [Committee/Individual]

**Need:**
- What problem are they solving? [Pain]
- How urgent is it? [1-10]
- Cost of not solving? $[X]/[Time]

**Timeline:**
- When do they need it? [Date]
- Why that timeline? [Reason]
- What happens if delayed? [Impact]

**Qualified?** [Yes/No]
**Next Steps:** [Schedule demo / Send proposal]

MEDDIC (Complex, Enterprise B2B):

## MEDDIC Qualification

**Metrics:**
- What are their success measures?
- Current state metrics: [Numbers]
- Desired state metrics: [Numbers]
- How do they measure ROI? [Formula]

**Economic Buyer:**
- Who controls the budget? [Name/Title]
- What's their priority? [Business goal]
- What do they care about? [Key metric]

**Decision Criteria:**
- How will they decide? [Must-haves vs nice-to-haves]
- Who evaluates? [Technical team, exec team]
- What's the scoring? [Point system, checklist]

**Decision Process:**
- What's the buying process? [Steps]
- Who's involved at each stage? [Stakeholders]
- Timeline? [Dates for each step]

**Identify Pain:**
- What's the business problem? [Quantified impact]
- Who feels the pain most? [Department/Person]
- Cost of inaction? $[X]/year

**Champion:**
- Who will sell internally for you? [Name]
- Do they have influence? [Y/N]
- Are they coaching you? [Y/N]

**Qualified?** [Yes/No]
**Deal Score:** [X/10]

Step 4: Discovery Questions

The Goal: Understand Their World Deeply

Current State:

- "Walk me through your current process for [X]."
- "What tools are you using today?"
- "How much time does this take per week?"
- "Who's responsible for this?"

Pain Points:

- "What's the biggest challenge with your current approach?"
- "What have you tried to solve this?"
- "Why didn't that work?"
- "What's this costing you? (time/money/opportunity)"

Impact:

- "If you could wave a magic wand, what would change?"
- "What would solving this enable you to do?"
- "How would this impact your team/company?"
- "What's at stake if this doesn't get solved?"

Decision Process:

- "How do decisions like this typically get made here?"
- "Who else needs to be involved?"
- "What would need to happen for you to move forward?"
- "What's your timeline for making a decision?"

Discovery Framework (SPIN Selling):

SITUATION: Understand their current state
- "How many customers do you have?"
- "What's your current process?"

PROBLEM: Identify pain points
- "What challenges are you facing?"
- "How is this impacting the business?"

IMPLICATION: Make pain bigger
- "What happens if this continues?"
- "How does this affect other areas?"

NEED-PAYOFF: Paint the solution
- "How would solving this help?"
- "What would that mean for your team?"

Step 5: Demo/Presentation

Demo Flow (20 minutes max):

## Demo Structure

**1. Recap Pain (2 min)**
- "Based on our conversation, you mentioned [X pain]"
- "Your goal is to [Y outcome]"
- "Today I'll show you exactly how we solve that"

**2. Show Solution (10 min)**
- Focus ONLY on features that solve THEIR pain
- Show, don't tell
- Use their data/examples if possible
- "Here's how you'd [specific task]..."

**3. Prove It (5 min)**
- Case study: "Company like yours saw [result]"
- ROI calculation: "Based on [their numbers], you'd save $[X]"
- Social proof: "[Number] companies use this for [use case]"

**4. Next Steps (3 min)**
- "Does this solve [their pain]?"
- "What questions do you have?"
- "What would you like to see next?"
- Schedule follow-up BEFORE you hang up

Presentation Principles:

✅ DO:
- Tailor to their specific pain
- Use their language/terminology
- Show, don't tell
- Quantify value ($X saved, Y% improvement)
- Leave time for questions

❌ DON'T:
- Feature dump
- Talk more than 60% of the time
- Skip their pain points
- Assume they remember past conversations
- End without clear next steps

Step 6: Objection Handling (LAER Framework)

LAER Method:

LISTEN: Let them fully express the objection
ACKNOWLEDGE: Show you understand
EXPLORE: Ask questions to find root cause
RESPOND: Address the real concern

Common Objections:

"It's too expensive"

LISTEN: "I understand budget is a concern."
ACKNOWLEDGE: "Many customers felt the same way initially."
EXPLORE: "Help me understand - compared to what?" / "What budget did you have in mind?"
RESPOND:
- "Let me show you the ROI..." [Show calculation]
- "What's the cost of not solving this?" [Quantify pain]
- "We have [alternative option] at [lower price]"

"I need to think about it"

LISTEN: "Of course, this is an important decision."
ACKNOWLEDGE: "I'd want time to think too."
EXPLORE: "What specifically would you like to think through?"
RESPOND: [Address the REAL concern they reveal]
- If budget: Show ROI
- If timing: Understand why delay
- If features: Address gaps
- If trust: Provide references

"We're already using [Competitor]"

LISTEN: "I appreciate you sharing that."
ACKNOWLEDGE: "[Competitor] is a good product."
EXPLORE: "How's that going? What made you take this call?"
RESPOND:
- Don't trash competitor
- "Many customers switched from [Competitor] because..."
- "What would make you consider an alternative?"
- Focus on differentiation

"Now isn't a good time"

LISTEN: "I understand timing matters."
ACKNOWLEDGE: "Timing has to be right."
EXPLORE: "When would be better? What's happening now?"
RESPOND:
- "What would change in [timeframe]?"
- "What's the cost of waiting [X months]?"
- "Can we start small now and expand later?"
- Schedule specific future follow-up

"I need to talk to [someone else]"

LISTEN: "Absolutely, it's important they're involved."
ACKNOWLEDGE: "Getting buy-in is critical."
EXPLORE: "What will be most important to them?"
RESPOND:
- "Can we schedule a call with them included?"
- "What do you think their main concerns will be?"
- "I can prepare materials for you to share"
- Offer to present to decision-maker directly

Step 7: Closing Techniques

Assumptive Close:

"Based on what we've discussed, this clearly solves [their pain].
When would you like to get started?"

Alternative Close:

"Would you prefer to start with the annual plan or monthly?"
"Should we begin with 10 licenses or 25?"

Summary Close:

"Let me make sure I understood correctly:
- You need to [solve X]
- We've shown how we do that
- The ROI is [Y]
- Your team is ready to start [timeline]
Does that sound right? What would you like to do next?"

Trial Close (Gauge Interest):

"If we can address [concern], are you ready to move forward?"
"On a scale of 1-10, how likely are you to proceed?"
(If <8: "What would make it a 10?")

Direct Ask:

"I think this is a great fit. Are you ready to get started?"

Step 8: Pipeline Management

Pipeline Stages:

| Stage | Definition | Exit Criteria | Probability | Avg Days |
|-------|------------|---------------|-------------|----------|
| Lead | Initial contact | Responded | 10% | 0-7 |
| Qualified | Fits ICP + BANT | Discovery scheduled | 25% | 7-14 |
| Discovery | Needs understood | Demo scheduled | 40% | 14-21 |
| Demo | Solution shown | Proposal requested | 50% | 21-28 |
| Proposal | Pricing sent | Verbal yes | 60% | 28-35 |
| Negotiation | Terms discussed | Contract sent | 80% | 35-42 |
| Closed Won | Deal signed | -- | 100% | 42 |
| Closed Lost | Deal lost | -- | 0% | -- |

Weekly Pipeline Review:

## Pipeline Review: [Date]

### Summary
- Total pipeline value: $[X]
- Weighted pipeline: $[X] (value × probability)
- Deals in play: [X]
- Expected to close this month: $[X]
- Actual closed this month: $[X]

### By Stage
| Stage | # Deals | Value | Weighted | Avg Age |
|-------|---------|-------|----------|---------|
| Qualified | 5 | $50K | $12.5K | 10 days |
| Discovery | 3 | $30K | $12K | 18 days |
| Proposal | 2 | $40K | $24K | 25 days |

### Top 5 Deals
| Company | Value | Stage | Next Step | Close Date | Risk |
|---------|-------|-------|-----------|------------|------|
| Acme | $20K | Proposal | Send contract | Feb 15 | Low |
| TechCo | $15K | Negotiation | Legal review | Feb 20 | Med |

### Stuck Deals (>14 days in stage)
| Company | Stage | Days Stuck | Blocker | Action |
|---------|-------|------------|---------|--------|
| SlowCo | Discovery | 21 | No response | Call champion |

### Actions This Week
1. Follow up with SlowCo champion
2. Send proposal to Acme
3. Schedule 5 new discovery calls

Sales Email Templates

Cold Outreach:

Subject: [Trigger event or pain point]

Hi [Name],

Saw that [specific observation about their company - shows research].

[One sentence about common pain point in their industry.]

[One sentence about how you help, with specific result.]

Worth a 15-minute call to explore if there's a fit?

Best,
[Name]

P.S. [Relevant case study or proof point]

Follow-Up (No Response):

Subject: Re: [Original subject]

Hi [Name],

Quick follow-up on my note last week about [value prop in different words].

If now isn't the right time, no worries - just let me know and I'll check back in [3/6 months].

Best,
[Name]

Post-Meeting Follow-Up:

Subject: Next steps - [Company name]

Hi [Name],

Great speaking with you today. As discussed:

**Your challenges:**
- [Challenge 1 they mentioned]
- [Challenge 2 they mentioned]

**How we can help:**
- [Solution 1 with specific outcome]
- [Solution 2 with specific outcome]

**Next steps:**
- [Action 1] - [Owner] - [Date]
- [Action 2] - [Owner] - [Date]

Let me know if I missed anything.

Best,
[Name]

Sales Playbook Template

## Sales Playbook: [Product/Service]

### Ideal Customer Profile
[See ICP section above]

### Value Proposition
[One-liner and full framework]

### Discovery Questions
[Top 10 questions to ask]

### Common Objections & Responses
[Top 5 objections with LAER responses]

### Demo Flow
[20-minute structure]

### Pricing Presentation
- Lead with value, not price
- Anchor high: "$X for enterprise, but most start at $Y"
- Show ROI calculation
- Offer options (good, better, best)

### Closing Process
[Preferred closing techniques]

### Success Metrics
- Lead → Qualified: [X]%
- Qualified → Demo: [X]%
- Demo → Proposal: [X]%
- Proposal → Close: [X]%
- Average deal size: $[X]
- Sales cycle: [X] days

Common Mistakes

Don'tDo
Talk more than listenListen 60%, talk 40%
Lead with featuresLead with their pain
Skip discoveryThorough discovery every time
Give up after one objectionUse LAER framework
Forget to ask for the saleAlways ask for next step
Wing itFollow the playbook
Ignore pipeline metricsReview weekly
Compete on priceCompete on value

Tools & Resources

CRM:

  • HubSpot (free tier available)
  • Salesforce
  • Pipedrive
  • Close

Outreach:

  • Apollo.io (prospecting)
  • LinkedIn Sales Navigator
  • Hunter.io (email finding)

Resources:

  • "SPIN Selling" by Neil Rackham
  • "The Challenger Sale" by Dixon & Adamson
  • "Predictable Revenue" by Aaron Ross

Related Skills

  • /pitch-deck-review - Creating sales presentations
  • /pricing-analysis - Setting pricing strategy
  • /copywriter - Writing compelling emails

Last Updated: 2026-01-22

平台分布

Codex

34.12%
按下载量换算33

Claude

30.32%
按下载量换算29

Cursor

19.53%
按下载量换算19

Gemini CLI

9.14%
按下载量换算9

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills