How do I install the Deal Pipeline skill?

Run npx skillmds@latest add jeremylongshore/deal-pipeline in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Deal Pipeline safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Deal Pipeline?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Deal Pipeline free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Deal Pipeline?

jeremylongshore (@jeremylongshore) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Deal Pipeline by jeremylongshore — Agent Skill

Name: Deal Pipeline
Rating: 4.5 (4 reviews)
Author: jeremylongshore

Deal Pipeline

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".

File contents

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:

# 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.

Source: jeremylongshore/claude-code-plugins-plus-skills → plugins/ai-agency/tonone/skills/deal-pipeline/SKILL.md

---name: deal-pipelinedescription: 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".--- # 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. --- **Source:** [`jeremylongshore/claude-code-plugins-plus-skills`](https://github.com/jeremylongshore/claude-code-plugins-plus-skills) → `plugins/ai-agency/tonone/skills/deal-pipeline/SKILL.md`

Frequently asked questions