Inspects deal health, map stakeholders, identify risks, and recommend next actions. Use when a deal feels stuck or at risk, you're not sure who the real decision-maker is, champion seems weak or disengaged, MEDDPICC gaps are unclear, a deal review is coming up and you need to prep, or you can't tell if a deal will actually close. Do NOT use for portfolio-level pipeline management (use /sales-pipeline), revenue forecasting (use /sales-forecast), or reviewing a specific sales call (use /sales-call-review).
Help the user inspect an individual deal — score its health, identify risks, map stakeholders, and build a prioritized action plan.
If references/learnings.md exists, read it first for accumulated knowledge.
Ask the user:
Deal basics:
Stakeholders:
What's your biggest concern about this deal?
Score each dimension as Green (strong), Yellow (gaps), or Red (at risk):
| Dimension | Status | Evidence | Gap |
|---|---|---|---|
| Champion strength | Do you have an internal advocate who is actively selling on your behalf? Can they access power? | ||
| Economic buyer access | Have you met the person who controls the budget? Do they support this initiative? | ||
| Decision criteria | Do you know exactly what they're evaluating against? Are your strengths aligned to their criteria? | ||
| Decision process | Do you know every step from here to a signed contract? (Legal, procurement, board approval, etc.) | ||
| Compelling event | Is there a hard deadline driving urgency? (Contract expiry, board mandate, regulatory, fiscal year) | ||
| Competition | Do you know who else they're evaluating? What's your differentiation? | ||
| Budget | Has budget been allocated? Is it sufficient? Is there a procurement process? | ||
| Paper process | Do you know who signs, what approvals are needed, and the typical timeline for contracts? |
Overall health: Count of Green/Yellow/Red → Assessment:
| Element | What's known | What's missing | Priority to fill |
|---|---|---|---|
| Metrics | |||
| Economic Buyer | |||
| Decision Criteria | |||
| Decision Process | |||
| Paper Process | |||
| Implicate the Pain | |||
| Champion | |||
| Competition |
| # | Risk | Likelihood | Impact | Mitigation |
|---|---|---|---|---|
| 1 | High/Med/Low | High/Med/Low | Specific action to reduce this risk | |
| 2 | ||||
| 3 |
Check which patterns apply to this deal:
| Priority | Action | Owner | Timeline | Purpose |
|---|---|---|---|---|
| 1 | Rep / Manager / SE | This week | ||
| 2 | Next week | |||
| 3 | This month | |||
| 4 | Ongoing | |||
| 5 |
Actions should be specific, not generic. Instead of "build executive relationship," write "Request a 15-minute call with CFO Jane Smith to discuss Q3 cost-reduction goals — ask your champion Sarah to make the intro by Friday."
| Name | Title | Role in deal | Engagement level | Relationship strength | Action needed |
|---|---|---|---|---|---|
| Champion / EB / Tech Eval / End User / Blocker / Coach | High / Med / Low / None | Strong / Developing / Weak / Unknown |
/sales-salesloft — Salesloft Deals module for pipeline visibility and deal health scores/sales-forecast — Roll up deal assessments into forecast accuracy/sales-pipeline — Portfolio-level pipeline management and deal prioritization/sales-discovery — Prep discovery questions to fill MEDDPICC gaps/sales-call-review — Review the latest call on this deal for coaching insights/sales-close — Closing strategies and mutual action plans/sales-do — Not sure which skill to use? The router matches any sales objective to the right skill. Install: npx skills add sales-skills/sales --skill sales-doDon't rate champion strength without evidence. Claude tends to mark champion as "Yellow" or "Red" based on vague signals. Ask specifically: "Has your champion introduced you to other stakeholders? Have they shared internal docs or timeline info?" No evidence = unknown, not weak.
Don't assume single-threaded is always bad. For small deals (<$20k) with a single decision-maker, being single-threaded is normal and efficient. Multi-threading guidance applies primarily to complex, multi-stakeholder deals.
Don't confuse decision criteria with decision process. Criteria = what they're evaluating (features, price, integrations). Process = how they'll decide (who approves, what steps, what timeline). Claude often conflates these — keep them separate in the MEDDPICC extraction.
Don't generate generic "follow up with the prospect" action items. Every action must be specific: who, what, by when, and why. "Follow up" is not an action plan — "Ask Sarah to intro you to CFO by Friday so you can confirm budget before the board meeting" is.
Don't catastrophize a deal based on one missing MEDDPICC element. Not every deal needs all 8 elements fully addressed. Prioritize based on deal stage and size.
Self-improving: If you discover something not covered here, append it to references/learnings.md with today's date.
User says: "My $120k deal has been stuck at proposal stage for 3 weeks. I haven't met the CFO and Gong is competing." Skill does:
User says: "Help me prepare for a deal review with my manager. $250k Fortune 500, strong champion, CIO attended demo, in POC, but legal hasn't started and close date is 6 weeks out." Skill does:
Solution: Use the MEDDPICC extraction table to structure what's known vs. unknown. Even partial information reveals where the biggest gaps are. The skill can work with whatever the user provides and will flag what's missing.
Solution: Check for "happy ears" — the prospect says positive things but doesn't take action. Apply the commitment test: ask for something concrete (access to the EB, internal data, a specific next meeting date). If they won't commit, the deal health score should be downgraded regardless of what they say verbally.
Solution: Focus on the top risk by likelihood x impact. The action plan is prioritized for this reason. As a rule of thumb: fix Red items before Yellow, and address Champion/EB gaps before anything else — without a champion and economic buyer, no other action matters.