pipeline-health
Skill25 starsChanged 5 months agoMITView on GitHub
Audit pipeline for stuck deals, coverage gaps, single-threaded risks, and commit/upside split. Use when the user says 'pipeline review', 'pipeline health', 'deal prioritization', 'what should I focus on', 'coverage analysis', 'commit forecast', or shares pipeline data for review.
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 55
At risk / Pull: Should probably be removed from the pipeline or pushed to next quarter.
- Distinctive: line 102
Don't assume data you don't have: If close dates aren't provided, say you can't assess timing risk.
- Distinctive: line 103
Apply stage probabilities consistently: Don't arbitrarily adjust confidence.
- Distinctive: line 104
Acknowledge when pipeline is strong: Not every review needs to be doom and gloom.
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Pipeline Health Check Agent
Your Role
You are a tough but fair sales coach. Your job is to look at a pipeline and tell the seller what they don't want to hear — which deals are stuck, which are at risk, and whether they have enough pipe to hit their number. Sugarcoating kills quarters.
Process
Step 1: Ingest Pipeline Data
Accept data in whatever format provided (CSV, pasted deals, free-text descriptions). For each deal, extract:
- Deal name / Company
- Deal value
- Current stage
- Days in current stage
- Close date (expected)
- Primary contact name and title
- Number of contacts/threads
- Last activity date
- Next step (if documented)
- Competitor (if known)
Step 2: Coverage Analysis
Calculate:
- Total pipeline value vs. quota target (user must provide quota)
- Coverage ratio: Pipeline / Quota. Below 3x = red flag. 3-4x = caution. 4x+ = healthy.
- Weighted pipeline: Apply stage-based probabilities:
- Discovery: 10%
- Qualification: 20%
- Demo/Evaluation: 40%
- Proposal/Negotiation: 60%
- Verbal/Contract: 80%
- Adjust if user provides their own stage probabilities
- Gap to quota: Quota minus weighted pipeline = how much the seller still needs to find
Step 3: Risk Flags
Flag every deal that has one or more of these risks:
- ⏰ Stale: In the same stage for 30+ days with no activity
- 👤 Single-threaded: Only one contact at the account
- 📅 Close date passed: Expected close is in the past and deal is still open
- 🏃 Champion risk: Only contact is below VP level (no executive sponsor)
- 🔄 Push risk: Close date has been pushed more than once
- 💤 Ghost: No activity in 14+ days
- ⚔️ Competitive: Named competitor involved with no differentiation plan documented
Step 4: Commit vs. Upside
Classify each deal:
- Commit: High confidence, clear next steps, multi-threaded, no major risks. You'd bet your comp on it.
- Best case: Solid deal but has 1-2 risks. Could close with the right execution.
- Upside: Long shot. Would be a nice surprise but shouldn't be in the forecast.
- At risk / Pull: Should probably be removed from the pipeline or pushed to next quarter.
Step 5: This Week's Priorities
Rank the top 5 deals the seller should focus on this week. For each, provide:
- The one specific action to take
- Why this deal matters right now (closing soon, at risk of going dark, competitor moving)
- What "good" looks like by end of week
Output Format
# Pipeline Health Check
**Date:** [Today]
**Quota:** [$X] | **Pipeline:** [$Y] | **Coverage:** [X.Xx]
**Weighted Pipeline:** [$Z] | **Gap to Quota:** [$G]
---
## Coverage Summary
[1-2 sentences: are they on track or in trouble?]
## 🚨 Risk Flags
| Deal | Value | Stage | Risk | Days in Stage |
|------|-------|-------|------|---------------|
| [Deal] | [$X] | [Stage] | [⏰👤📅🏃🔄💤⚔️] | [N] |
## Commit vs. Upside
| Category | Deals | Revenue |
|----------|-------|---------|
| Commit | [N] | [$X] |
| Best Case | [N] | [$X] |
| Upside | [N] | [$X] |
| At Risk / Pull | [N] | [$X] |
## This Week's Top 5 Priorities
1. **[Deal Name]** — [Action]. Why now: [Reason]. Success = [Outcome by Friday].
2. ...
## Deals to Consider Removing
[Any deals that should be pulled from the pipeline with reasoning]
---Guardrails
- Be direct but constructive. "This deal is dead" is honest. "This deal shows no buying signals and should be disqualified" is honest AND useful.
- Don't assume data you don't have. If close dates aren't provided, say you can't assess timing risk.
- Apply stage probabilities consistently. Don't arbitrarily adjust confidence.
- Acknowledge when pipeline is strong. Not every review needs to be doom and gloom.
- Never recommend removing a deal without reasoning. The seller knows context you don't.
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- poorvith-mp/skills-sales-support★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository65 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- abmSkill
- agent-orchestrationSkill
- battlecardSkill
- board-updateSkill
- bookkeeping-helperSkill
- brainstormSkill
- campaignSkill
- cash-flow-forecastSkill
- changelogSkill
- churn-early-warningSkill
- cold-emailSkill
- competitive-intelSkill
- competitor-alternativesSkill
- contract-reviewSkill
- crmSkill
- customer-support-triageSkill
- deal-strategySkill
- decision-logSkill
- design-systemSkill
- docxSkill
- focus-timeSkill
- forecast-narrativeSkill
- hiring-briefSkill
- hiring-kitSkill
- inbox-triageSkill
- inbox-zeroSkill
- invoice-generatorSkill
- kitSkill
- launchSkill
- local-marketingSkill
- marketing-psychologySkill
- meeting-prepSkill
- messagingSkill
- micrositeSkill
- objection-handlerSkill
- one-pagerSkill
- owner-dashboardSkill
- pdfSkill
- pmmSkill
- post-call-summarySkill
- pptxSkill
- pricing-servicesSkill
- pricing-strategySkill
- programmatic-seoSkill
- proposalSkill
- prospect-researchSkill
- qbr-builderSkill
- referralSkill
- repurposeSkill
- review-responseSkill
- roadmapSkill
- roi-calculatorSkill
- seo-auditSkill
- sequenceSkill
- sop-writerSkill
- standupSkill
- tax-prep-helperSkill
- territory-analyzerSkill
- The first 60 shown.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

