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".
npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill deal-pipeline --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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-
What does the deal-pipeline skill do?
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".
How do I install it?
Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill deal-pipeline --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From jeremylongshore/claude-code-plugins-plus-skills, a repository with 2,596 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.