PluginBench
Skill
Official
Pass
Audit score 90

pipeline-review

anthropics/knowledge-work-plugins

Analyze pipeline health, prioritize deals, and flag risks with a weekly action plan.

What is pipeline-review?

Analyze your sales pipeline to identify stale or stuck opportunities, audit for hygiene issues, and get a prioritized weekly action plan. Use this when running a weekly pipeline review, deciding which deals to focus on, or spotting at-risk deals that need attention.

  • Scores pipeline health across stage progression, activity recency, close date accuracy, and contact coverage
  • Prioritizes deals by impact and closability using a weighted framework (close date, deal size, stage, activity, risk)
  • Flags stale deals (no activity 14+ days), stuck deals (same stage 30+ days), past-due close dates, and single-threaded opportunities
  • Audits hygiene issues like missing close dates, amounts, next steps, or primary contacts
  • Generates a prioritized weekly action plan with specific next steps per deal
  • Provides pipeline shape analysis by stage, close month, and deal size

How to install pipeline-review

npx skills add https://github.com/anthropics/knowledge-work-plugins --skill pipeline-review
Claude Code
Cursor
Windsurf
Cline

How to use pipeline-review

  1. 1.Run `/pipeline-review [segment or rep]` to start the analysis
  2. 2.Provide your pipeline data via CSV export from your CRM, paste deal details, or describe your pipeline verbally
  3. 3.Review the pipeline health score and risk flags to identify problem areas
  4. 4.Focus on the priority actions ranked by impact and closability
  5. 5.Execute the weekly action items and update your CRM with new close dates, stages, or next steps

Use cases

Good for
  • Running a weekly pipeline review to stay on top of deal health and progress
  • Deciding which deals to focus on this week based on closability and impact
  • Identifying stale or stuck opportunities that need re-engagement or qualification
  • Auditing pipeline for data quality issues like bad close dates or missing contacts
  • Spotting single-threaded deals where only one contact exists and risk is high
Who it's for
  • Sales reps managing their own pipeline
  • Sales managers reviewing team or segment pipelines
  • Sales leaders auditing pipeline hygiene and forecast accuracy

pipeline-review FAQ

What data do I need to provide?

You can upload a CSV from your CRM (Salesforce, HubSpot, etc.), paste deal details manually, or describe your pipeline verbally. Helpful fields include deal name, account, amount, stage, close date, last activity date, and primary contact.

How does the prioritization framework work?

Deals are ranked by close date (30%), deal size (25%), stage (20%), activity recency (15%), and risk level (10%). You can adjust weights by telling the skill to focus on quick wins, big deals, or other priorities.

What if my CRM is connected?

When connected, the skill pulls your pipeline automatically, can update records with new close dates and stages, create follow-up tasks, and track hygiene improvements over time.

What counts as a stale or stuck deal?

Stale deals have no activity in 14+ days. Stuck deals have been in the same stage for 30+ days. Both are flagged for re-engagement or qualification decisions.

Can I use this for a team or just my own pipeline?

You can review your own pipeline or a segment/team's pipeline by specifying the segment or rep name in the command.

Full instructions (SKILL.md)

Source of truth, from anthropics/knowledge-work-plugins.


name: pipeline-review description: Analyze pipeline health — prioritize deals, flag risks, get a weekly action plan. Use when running a weekly pipeline review, deciding which deals to focus on this week, spotting stale or stuck opportunities, auditing for hygiene issues like bad close dates, or identifying single-threaded deals. argument-hint: "<segment or rep>"

/pipeline-review

If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.

Analyze your pipeline health, prioritize deals, and get actionable recommendations for where to focus.

Usage

/pipeline-review [segment or rep]

Review pipeline for: $ARGUMENTS

If a file is referenced: @$1


How It Works

┌─────────────────────────────────────────────────────────────────┐
│                     PIPELINE REVIEW                              │
├─────────────────────────────────────────────────────────────────┤
│  STANDALONE (always works)                                       │
│  ✓ Upload CSV export from your CRM                              │
│  ✓ Or paste/describe your deals                                 │
│  ✓ Health check: flag stale, stuck, and at-risk deals          │
│  ✓ Prioritization: rank deals by impact and closability        │
│  ✓ Hygiene audit: missing data, bad close dates, single-thread │
│  ✓ Weekly action plan: what to focus on                        │
├─────────────────────────────────────────────────────────────────┤
│  SUPERCHARGED (when you connect your tools)                      │
│  + CRM: Pull pipeline automatically, update records             │
│  + Activity data for engagement scoring                         │
│  + Historical patterns for risk prediction                      │
│  + Calendar: See upcoming meetings per deal                     │
└─────────────────────────────────────────────────────────────────┘

What I Need From You

Option A: Upload a CSV Export your pipeline from your CRM (e.g. Salesforce, HubSpot). Helpful fields:

  • Deal/Opportunity name
  • Account name
  • Amount
  • Stage
  • Close date
  • Created date
  • Last activity date
  • Owner (if reviewing a team)
  • Primary contact

Option B: Paste your deals

Acme Corp - $50K - Negotiation - closes Jan 31 - last activity Jan 20
TechStart - $25K - Demo scheduled - closes Feb 15 - no activity in 3 weeks
BigCo - $100K - Discovery - closes Mar 30 - created last week

Option C: Describe your pipeline "I have 12 deals. Two big ones in negotiation that I'm confident about. Three stuck in discovery for over a month. The rest are mid-stage but I haven't talked to some of them in a while."


Output

# Pipeline Review: [Date]

**Data Source:** [CSV upload / Manual input / CRM]
**Deals Analyzed:** [X]
**Total Pipeline Value:** $[X]

---

## Pipeline Health Score: [X/100]

| Dimension | Score | Issue |
|-----------|-------|-------|
| **Stage Progression** | [X]/25 | [X] deals stuck in same stage 30+ days |
| **Activity Recency** | [X]/25 | [X] deals with no activity in 14+ days |
| **Close Date Accuracy** | [X]/25 | [X] deals with close date in past |
| **Contact Coverage** | [X]/25 | [X] deals single-threaded |

---

## Priority Actions This Week

### 1. [Highest Priority Deal]
**Why:** [Reason — large, closing soon, at risk, etc.]
**Action:** [Specific next step]
**Impact:** $[X] if you close it

### 2. [Second Priority]
**Why:** [Reason]
**Action:** [Next step]

### 3. [Third Priority]
**Why:** [Reason]
**Action:** [Next step]

---

## Deal Prioritization Matrix

### Close This Week (Focus Time Here)
| Deal | Amount | Stage | Close Date | Next Action |
|------|--------|-------|------------|-------------|
| [Deal] | $[X] | [Stage] | [Date] | [Action] |

### Close This Month (Keep Warm)
| Deal | Amount | Stage | Close Date | Status |
|------|--------|-------|------------|--------|
| [Deal] | $[X] | [Stage] | [Date] | [Status] |

### Nurture (Check-in Periodically)
| Deal | Amount | Stage | Close Date | Status |
|------|--------|-------|------------|--------|
| [Deal] | $[X] | [Stage] | [Date] | [Status] |

---

## Risk Flags

### Stale Deals (No Activity 14+ Days)
| Deal | Amount | Last Activity | Days Silent | Recommendation |
|------|--------|---------------|-------------|----------------|
| [Deal] | $[X] | [Date] | [X] | [Re-engage / Downgrade / Remove] |

### Stuck Deals (Same Stage 30+ Days)
| Deal | Amount | Stage | Days in Stage | Recommendation |
|------|--------|-------|---------------|----------------|
| [Deal] | $[X] | [Stage] | [X] | [Push / Multi-thread / Qualify out] |

### Past Close Date
| Deal | Amount | Close Date | Days Overdue | Recommendation |
|------|--------|------------|--------------|----------------|
| [Deal] | $[X] | [Date] | [X] | [Update date / Push to next quarter / Close lost] |

### Single-Threaded (Only One Contact)
| Deal | Amount | Contact | Risk | Recommendation |
|------|--------|---------|------|----------------|
| [Deal] | $[X] | [Name] | Champion leaves = deal dies | [Identify additional stakeholders] |

---

## Hygiene Issues

| Issue | Count | Deals | Action |
|-------|-------|-------|--------|
| Missing close date | [X] | [List] | Add realistic close dates |
| Missing amount | [X] | [List] | Estimate or qualify |
| Missing next step | [X] | [List] | Define next action |
| No primary contact | [X] | [List] | Assign contact |

---

## Pipeline Shape

### By Stage
| Stage | # Deals | Value | % of Pipeline |
|-------|---------|-------|---------------|
| [Stage] | [X] | $[X] | [X]% |

### By Close Month
| Month | # Deals | Value |
|-------|---------|-------|
| [Month] | [X] | $[X] |

### By Deal Size
| Size | # Deals | Value |
|------|---------|-------|
| $100K+ | [X] | $[X] |
| $50K-100K | [X] | $[X] |
| $25K-50K | [X] | $[X] |
| <$25K | [X] | $[X] |

---

## Recommendations

### This Week
1. [ ] [Specific action for priority deal 1]
2. [ ] [Action for at-risk deal]
3. [ ] [Hygiene task]

### This Month
1. [ ] [Strategic action]
2. [ ] [Pipeline building if needed]

---

## Deals to Consider Removing

These deals may be dead weight:

| Deal | Amount | Reason | Recommendation |
|------|--------|--------|----------------|
| [Deal] | $[X] | [No activity 60+ days, no response] | Mark closed-lost |
| [Deal] | $[X] | [Pushed 3+ times, no champion] | Qualify out |

Prioritization Framework

I'll rank your deals using this framework:

FactorWeightWhat I Look For
Close Date30%Deals closing soonest get priority
Deal Size25%Bigger deals = more focus
Stage20%Later stage = more focus
Activity15%Active deals get prioritized
Risk10%Lower risk = safer bet

You can tell me to weight differently: "Focus on big deals over soon deals" or "I need quick wins, prioritize close dates."


If CRM Connected

  • I'll pull your pipeline automatically
  • Update records with new close dates, stages, next steps
  • Create follow-up tasks
  • Track hygiene improvements over time

Tips

  1. Review weekly — Pipeline health decays fast. Weekly reviews catch issues early.
  2. Kill dead deals — Stale opportunities inflate your pipeline and distort forecasts. Be ruthless.
  3. Multi-thread everything — If one person goes dark, you need a backup contact.
  4. Close dates should mean something — A close date is when you expect signature, not when you hope for one.

Related skills

More from anthropics/knowledge-work-plugins and the wider catalog.

PLplan-payroll logo

plan-payroll

Official
anthropics/knowledge-work-plugins

Forecasts cash, ranks overdue invoices, and stages PayPal reminders so the owner can confidently run payroll. Accepts optional horizon and payroll-date arguments.

706 installs
PLplan-zoom-integration logo

plan-zoom-integration

Official
anthropics/knowledge-work-plugins

Turn a Zoom integration idea into an implementation plan with architecture, auth, and delivery milestones. Use when you need a practical build plan, phased delivery sequence, risk list, and next-step recommendation.

1.1k installsAudited
PLplan-zoom-product logo

plan-zoom-product

Official
anthropics/knowledge-work-plugins

Choose the right Zoom building surface for a use case and explain the tradeoffs clearly. Use when deciding between REST API, Webhooks, WebSockets, Meeting SDK, Video SDK, Zoom Apps SDK, Phone, Contact Center, or MCP for a specific product idea or integration goal.

1.1k installsAudited
POpolicy-lookup logo

policy-lookup

Official
anthropics/knowledge-work-plugins

Find and explain company policies in plain language from handbooks and knowledge bases.

1.8k installsAudited
PRprice-check logo

price-check

Official
anthropics/knowledge-work-plugins

Produces a margin-by-product table and three pricing-scenario data views so the owner can see the full financial picture before making a pricing decision. Accepts optional product name argument.

611 installsAudited
PRprobe-sdk logo

probe-sdk

Official
anthropics/knowledge-work-plugins

Reference skill for Zoom Probe SDK. Use after routing to a preflight workflow when testing browser compatibility, media permissions, audio or video diagnostics, and network readiness before users join.

1.1k installs