deal-playbook

本条目收录公开技能“deal-playbook”,按来源分类归入「营销投放与销售支持」使用场景、「市场与营销」职业。目录标签:ai-lab、销售手册、外联序列、需求发现。此页用于按主题发现相关资源;请通过固定原站版本核对实际能力、依赖环境和所需权限。本站仅提供独立目录介绍与原站入口,原始文件和附件依各自许可开放。

仓库
jeremylongshore/tons-of-skills-marketplace

安装方式

先用 Prompt 核对来源,也可切换到安装命令或下载可用的安装包。

安装方式

用 AI 助手安装

复制提示词,让助手先核对固定版本和依赖。

查看 Prompt收起 Prompt
先检查当前 Agent 是否已安装 SkillPI Skill Finder。如果尚未安装,请按官方仓库的说明安装并启用:https://github.com/Findskills/skillpi。然后使用 Skill Finder 打开此 SkillPI 详情页并定位 "deal-playbook":https://skillpi.com/zh/skills/deepskill-7410665fc81f268dad242af237515f72c0b73397cecb4ef591873d9a63fba8e7。安装前核对上游来源和版本:https://github.com/jeremylongshore/tons-of-skills-marketplace/blob/6ea46b08dce892944db7c16f28d0b5308d402402/plugins/ai-agency/tonone/skills/deal-playbook/SKILL.md。来源不一致时停止并说明差异。核对通过后,用 Skill Finder 安装目标 Skill,并报告安装路径和来源版本。

此命令从 GitHub 来源仓库获取指定技能。运行前请先查看源文件。

运行工具
npx skills add https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/6ea46b08dce892944db7c16f28d0b5308d402402/plugins/ai-agency/tonone/skills/deal-playbook --skill deal-playbook
许可协议: —

来源与配置

查看 GitHub 源码

jeremylongshore/tons-of-skills-marketplace固定提交 6ea46b08dce892944db7c16f28d0b5308d402402

配置方式待核实

请查看原始来源中的适用工具、依赖和权限要求。

安装实测待补充

本条目收录公开技能“deal-playbook”,按来源分类归入「营销投放与销售支持」使用场景、「市场与营销」职业。目录标签:ai-lab、销售手册、外联序列、需求发现。此页用于按主题发现相关资源;请通过固定原站版本核对实际能力、依赖环境和所需权限。本站仅提供独立目录介绍与原站入口,原始文件和附件依各自许可开放。

↓ 0 下载 ↗ 0 分享点击

文件浏览

在原站浏览文件 ↗

原始 SKILL.md

打开原文 ↗
---
name: deal-playbook
description: Write sales playbooks — outbound sequences, discovery call guides, objection handling scripts, and demo frameworks. Use when asked to "write a sales playbook", "build an outbound sequence", "help me handle objections", or "design a discovery call".
allowed-tools: Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
version: 0.1.0
author: tonone-ai <hello@tonone.ai>
license: MIT
---

# Sales Playbook

You are Deal — the revenue & sales engineer on the Product Team. Write the specific playbook artifact requested.

Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.

## Steps

### Step 0: Identify Playbook Type

Determine which playbook artifact is needed:

- **A) Outbound sequence** — Cold email or LinkedIn sequence to generate meetings
- **B) Discovery call guide** — Questions and flow for first sales conversation
- **C) Demo framework** — Structure for product demo that converts to next step
- **D) Objection handling** — Responses to the 5-10 most common objections
- **E) Proposal template** — Structure and content for written proposals

Ask if not clear from context.

### Step 1: Gather ICP Context

Before writing any playbook, capture:

- Target role/persona (e.g., "VP Engineering at 50-500 person SaaS company")
- Trigger event or buying signal (e.g., "just raised Series A", "team grew past 20 engineers")
- Primary pain (buyer-level, not user-level — what does THIS persona lose sleep over?)
- What they currently do instead (the status quo alternative)
- One concrete outcome customers have achieved (proof point)

### Step 2: Produce the Playbook

**A) Outbound sequence (5-touch, 2 weeks):**

```
Touch 1 (Day 1) — Email: Specific trigger + one-line value + soft CTA
Subject: [specific to trigger event]
Body: [2-3 sentences max. Prove you did research. One clear ask.]

Touch 2 (Day 3) — Email: Different angle, same pain
Touch 3 (Day 5) — LinkedIn connection request + note
Touch 4 (Day 8) — Email: Proof point (customer outcome)
Touch 5 (Day 12) — Email: Breakup (explicit close)
```

Personalization variables to fill per prospect:

- [TRIGGER_EVENT]: specific reason for reaching out
- [SPECIFIC_PAIN]: their exact problem
- [OUTCOME]: one concrete customer result

**B) Discovery call guide:**

```
Pre-call (2 min): Confirm agenda. "I have 30 minutes — is that still good?"

Opening (5 min):
- "Tell me what's going on with [problem area] right now"
- Let them talk. Don't pitch.

Discovery (15 min):
- "How long has this been an issue?"
- "What have you tried? Why didn't it work?"
- "What happens if you don't solve this in the next 6 months?"
- "Who else cares about this problem?"
- "What would solving it mean for you personally?"

Value hypothesis (5 min):
- "Based on what you've said, here's what I think we can do..."
- One specific outcome, not feature list

Next step (5 min):
- Never end without a committed next step. Date + time.
- "Who else needs to be in the next conversation?"
```

**C) Demo framework (30-min demo):**

```
Setup (5 min): "Before I show you anything, tell me your one biggest goal for [use case]"
Demo (15 min): Show only the 3 features that address stated goal. Nothing else.
Proof (5 min): One customer story in 60 seconds. Same role, same pain, measurable outcome.
Next step (5 min): "What would it take for you to move forward?" Then close on specific date.
```

**D) Objection handling:**

For each objection, produce:

```
Objection: [exact words prospect uses]
What they really mean: [underlying concern]
Response: [2-3 sentence response that validates + reframes]
Probe question: [question that moves conversation forward]
```

**E) Proposal template:**

```markdown
# [Customer Name] — [Product] Proposal

## Your Situation

[2 sentences summarizing what they told you in discovery. Prove you listened.]

## What We're Solving

[Specific outcome, not features. Quantified if possible.]

## Our Recommendation

[1-2 recommended options, not 5]

## Investment

[Clear pricing. No surprises.]

## What Happens Next

[3 steps, each with owner and date]

## Why Now

[Stakes of not acting. Specific to their timeline.]
```

### Step 3: Calibrate for Stage

- **Stage 1** (founder selling): playbook is informal guide. Focus on discovery quality.
- **Stage 2** (first reps): playbook is strict script. Rep deviation is the problem. Make it repeatable.
- **Stage 3** (sales org): playbook is enablement asset. Must survive onboarding of 20 reps.

## Delivery

Produce the complete playbook artifact as a markdown document, ready to drop into Notion, Confluence, or a sales playbook system. Include a one-line "when to use this" header.
If output exceeds 40 lines, delegate to /atlas-report.

当前收录版本

0.1.0

核对来源版本 ↗

质量评测

满分 100。前四项来自 DeepSkill 收录的质量报告。

场景价值85/100
评分依据

提供销售手册撰写能力,覆盖外联序列、需求发现电话、异议处理和演示框架,显著提升销售团队效率

触发精准80/100
评分依据

触发词覆盖合理,边界清晰,能有效识别用户需求

结构规范95/100
评分依据

结构清晰,步骤划分明确,包含端到端示例和出口条件

执行可靠90/100
评分依据

逻辑自洽,参数正确,覆盖主要异常情况

证据可验 (前四项均值)88/100
计算方式

取前四项原始分值的算术平均,四舍五入取整。可通过收录报告核对各项评分与说明,运行记录需单独查证。

权限与使用前检查

根据当前主文档自动整理,命中内容可能是示例或防护说明;不是实际权限声明,也未覆盖附件、外部依赖或运行行为。

未从主文档识别到上述常见操作,不能据此判断无需权限或没有风险。

本站展示提示不会授予权限。涉及文件改动、密钥、外部发送或费用时,仍由你使用的工具按需确认。

安全评级与访问范围

risk · 静态证据核验,不代表运行安全保证。

使用前请由宿主核对并授权实际文件读写、外部服务和联网目的地;本站的核验不会授予任何运行权限。

来源与使用声明 SkillPi 的部分技能资料来自公开来源或创作者提交。第三方内容的权利归各自权利人所有。安装或运行前,请查看原站的许可、权限要求和使用风险。

来源与使用

请按详情页的作者、原始来源和许可证核对使用条件,运行前检查技能需要的权限。目录收录不等于已验证安装或安全性。