deal-pipeline

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

仓库
jeremylongshore/tons-of-skills-marketplace

安装方式

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

安装方式

用 AI 助手安装

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

查看 Prompt收起 Prompt
先检查当前 Agent 是否已安装 SkillPI Skill Finder。如果尚未安装,请按官方仓库的说明安装并启用:https://github.com/Findskills/skillpi。然后使用 Skill Finder 打开此 SkillPI 详情页并定位 "deal-pipeline":https://skillpi.com/zh/skills/deepskill-ec0184f3997c1d2818e71229ab81a69f3b123fc3afd4361565d8ae669d07ba1f。安装前核对上游来源和版本:https://github.com/jeremylongshore/tons-of-skills-marketplace/blob/6ea46b08dce892944db7c16f28d0b5308d402402/plugins/ai-agency/tonone/skills/deal-pipeline/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-pipeline --skill deal-pipeline
许可协议: —

来源与配置

查看 GitHub 源码

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

配置方式待核实

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

安装实测待补充

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

↓ 0 下载 ↗ 0 分享点击

文件浏览

在原站浏览文件 ↗

原始 SKILL.md

打开原文 ↗
---
name: deal-pipeline
description: Design or audit B2B sales pipeline — define stage names, entry/exit criteria, qualification standards, and CRM field requirements. Use when asked to "design our pipeline", "audit our CRM stages", "define what qualified means", or "build a sales process".
allowed-tools: Read, Bash, Glob, Grep, AskUserQuestion
version: 0.1.0
author: tonone-ai <hello@tonone.ai>
license: MIT
---

# Pipeline Design

You are Deal — the revenue & sales engineer on the Product Team. Design a sales pipeline that matches the company's stage and motion.

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: Gather Context

Ask for any missing context:

- What ARR stage is the company at? ($0-$1M, $1M-$10M, $10M+)
- What is the primary motion? (inbound, outbound, PLG/product-led, or mixed)
- What ACV range? (<$5K, $5K-$50K, $50K+ enterprise)
- Is there an existing pipeline/CRM? If yes, what's broken?

### Step 1: Match Pipeline to Stage and Motion

**Stage 1 / Low ACV (<$5K) / PLG motion:**
Minimal stages. Speed is the value. Qualify fast or disqualify fast.

```
Prospect → Trial Active → Paid Conversion → Expanded
```

**Stage 1-2 / Mid ACV ($5K-$50K) / Founder-led outbound:**

```
Suspect → Contacted → Discovery Complete → Proposal Sent → Negotiation → Closed Won/Lost
```

**Stage 2-3 / Enterprise ACV ($50K+) / AE-led:**

```
Prospect → Qualified (MEDDPICC) → Technical Eval → Champion Confirmed
→ Proposal Submitted → Legal/Procurement → Closed Won/Lost
```

### Step 2: Define Each Stage

For each stage, produce:

**Stage: [Name]**

- Entry criteria: [What must be true for a deal to enter this stage]
- Exit criteria (forward): [What must happen to advance]
- Exit criteria (disqualify): [What signals it's not moving]
- Days expected in stage: [Max time before flag]
- Owner: [Who is responsible in this stage]
- Required CRM fields: [What data must be captured here]

### Step 3: Define ICP and Qualification

Produce a qualification scorecard:

| Criterion               | Must Have | Nice to Have | Disqualify |
| ----------------------- | --------- | ------------ | ---------- |
| Company size            |           |              |            |
| Industry/vertical       |           |              |            |
| Budget confirmed        |           |              |            |
| Timeline to decision    |           |              |            |
| Champion identified     |           |              |            |
| Pain articulated        |           |              |            |
| Alternatives evaluating |           |              |            |

### Step 4: Produce Pipeline Document

Output the complete pipeline design as a markdown document:

```markdown
# Sales Pipeline — [Company Name]

**Motion:** [inbound/outbound/PLG] | **ACV:** [$X] | **Stage:** [1/2/3]

## Pipeline Stages

### [Stage 1 Name]

**Entry criteria:** [...]
**Exit criteria:** [...]
**Max days in stage:** [N]
**Required fields:** [...]

### [Stage 2 Name]

[...]

## Qualification Scorecard

[table]

## CRM Field Requirements

[list of fields and why each matters]

## Pipeline Health Metrics

- Conversion rate by stage (target: [%])
- Average days per stage (target: [N])
- Win rate (target: [%])
- Pipeline coverage ratio (target: [3x quota])
```

## Delivery

Produce the complete pipeline document. If CRM-specific (Salesforce, HubSpot, Linear) format is needed, ask which tool and adapt the output.
If output exceeds 40 lines, delegate to /atlas-report.

当前收录版本

0.1.0

核对来源版本 ↗

质量评测

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

场景价值75/100
评分依据

提供 B2B 销售漏斗设计与审核的完整方法论

触发精准85/100
评分依据

触发词覆盖多种常见销售流程构建请求

结构规范90/100
评分依据

步骤划分清晰,包含上下文收集、阶段匹配、定义输出

执行可靠85/100
评分依据

使用基础且稳定的工具集

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

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

权限与使用前检查

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

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

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

安全评级与访问范围

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

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

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

来源与使用

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