Pipeline Review Skill

Every deal in your pipeline has a story. This skill reads all of them — flags what’s stale, what’s missing, and what’s about to slip — before your weekly review.

Overview

The Pipeline Review Skill runs a full signal check across every open deal in your pipeline and returns a ranked brief — deals at risk at the top, deals on track below. Stale contacts, missing buying group coverage, no activity in 30 days, a champion who left last week — every risk surfaces before you walk into the review, not during it.

Give it your pipeline — a list of open deals with account names and deal stages. It pulls live signals via the Lusha in Claude connector, verifies that key contacts are still in seat, checks for buying signals and news that change the deal picture, and returns a risk-ranked brief with a recommended action for every deal that needs attention.

The result is a pipeline review your manager doesn’t have to run for you — because you already know every answer before they ask.

What it does

  • Deal risk ranking — scores every open deal by risk level and surfaces the highest-risk deals first. No more discovering a deal is in trouble halfway through the review.
  • Contact verification — checks that key contacts are still in seat for every deal. A champion who left is the most common reason a deal slips — this catches it before it does.
  • Buying group coverage audit — flags deals where key roles — Economic Buyer, Technical Evaluator, Procurement — have no verified contact behind them.
  • Signal check per deal — pulls buying signals, recent news, and hiring moves at each account. Surfaces anything that changes the deal picture since the last review.
  • Recommended next action per deal — every at-risk deal gets a concrete next action tied to the specific risk flagged. Not a status update — a thing to do.

Use cases

Weekly pipeline review prep

Before your weekly pipeline review, run the skill across every open deal. It returns a risk-ranked brief with a recommended action for every deal that needs attention. You walk into the review knowing every answer — not scrambling to explain why a deal slipped.

End-of-quarter pipeline audit

Before quarter close, run the skill to identify every deal with a verification gap, a missing contact, or a stale signal. The deals most likely to slip surface first — with enough time to do something about it.

Manager deal inspection

For sales managers inspecting a rep’s pipeline, run the skill before the 1:1. Every deal risk is already surfaced — stale contacts, coverage gaps, missing Economic Buyers — so the conversation is about what to do next, not what’s going on.

Skill definition

The instructions Claude uses to run this skill. Copy it into a .md file in your Claude Code skills folder, or paste it into a Claude project as a custom instruction.

Example outputs in this skill are illustrative — they reflect the structure, fields, and format of real Lusha connector output, but were not pulled from a live session. Run the skill with your own data and connectors to see live results.

---
name: pipeline-review-skill
description: >
  Run a full signal check across every open deal in a pipeline.
  Takes a deal list with account names and stages. Returns a
  risk-ranked brief — stale contacts, missing buying group
  coverage, signal gaps, and a recommended next action for
  every deal that needs attention.
connectors:
  required: lusha
  optional: crm, slack
campus_url: https://www.lusha.com/campus/plays/pipeline-review-skill/
category: Skills
---

# Pipeline Review Skill

Run a full signal check across every open deal in a pipeline.
Rank deals by risk. Verify key contacts are still in seat.
Flag buying group gaps. Surface signals that change the deal
picture. Return a brief the rep or manager can act on before
the weekly review.

## Input

The user will provide via $ARGUMENTS:

- Deal list (required) — a list of open deals. For each deal:
  - Account name or domain (required)
  - Deal stage (required) — e.g. Stage 1, Discovery, Proposal,
    Negotiation, Pre-close
  - Key contacts (optional) — named contacts to verify per deal
  - Deal value (optional) — used to weight risk scoring
- Review context (optional) — what this review is for. Examples:
  - "weekly pipeline review — flag everything at risk"
  - "end of quarter audit — focus on deals in Stage 3+"
  - "manager 1:1 — inspect rep's full pipeline"

  If deal list is missing, ask once. If declined, return an
  error — the skill cannot run without a list of deals.

## Workflow

1. Anchor on the review context.
   Read the review context and deal list from $ARGUMENTS.
   Default to full pipeline risk review if no context supplied.
   State the parameters at the top of the output.

2. Resolve accounts via Lusha.
   For each deal in the list:
   - Resolve the account via companies_search using the name
     or domain.
   - Flag any accounts that could not be resolved and skip them.

3. Pull signals and verify contacts in parallel.
   For each resolved account, run these calls concurrently:
   - Contact verification: confirm key contacts are still in
     seat. Flag departures, role changes, and tenure risks.
     If no key contacts supplied, identify and verify the most
     senior contact in the primary buying function automatically.
   - Buying group coverage: check for verified contacts across
     all key buying roles — Champion, Economic Buyer, Technical
     Evaluator, Procurement. Flag missing roles.
   - Buying signals: intent topics, signal score 60+. Flag
     anything that changes the deal picture — intent on a
     competitor's category, intent on your category dropping.
   - Recent news and scoops: last 30 days. Leadership moves,
     funding, layoffs, budget signals, product launches.
   - Activity gap: flag any deal with no noted activity in
     30+ days as stale.

4. Score each deal by risk.
   Assign each deal a risk score based on:
   - Contact verification status — departed champion: high risk
   - Buying group coverage gaps — missing Economic Buyer at
     Stage 3+: high risk
   - Activity gap — no activity in 30+ days: medium risk
   - Negative signals — layoffs, budget cuts, competitor intent:
     high risk
   - Deal stage vs. signal alignment — late stage deal with no
     buying signals: medium risk
   - Deal value — weight higher-value deals more heavily

   Rank deals: At Risk (H) → Needs Attention (M) → On Track (L)

5. Write the pipeline brief.
   Lead with a summary: total deals reviewed, at-risk count,
   needs-attention count, on-track count, and the single most
   urgent action across the whole pipeline this week.
   Then the ranked deal list.

## Output Format

### Pipeline Review Brief

Review context: [restate in one line]
Deals reviewed: [n]
At risk: [n]
Needs attention: [n]
On track: [n]
Most urgent action: [one line — the single most important
action across the whole pipeline right now]

---

### At Risk Deals

For each at-risk deal, ranked by risk score:

**[Account Name]** — Stage: [stage] | Risk: High

| Risk Factor | Detail | Recommended Action |
|---|---|---|

Key contact status: [verified in seat / departed / unverifiable]
Buying group gaps: [missing roles, if any]
Next action: [one concrete action tied to the highest risk factor]

---

### Needs Attention

For each deal needing attention, ranked by risk score:

**[Account Name]** — Stage: [stage] | Risk: Medium

| Risk Factor | Detail | Recommended Action |
|---|---|---|

Next action: [one concrete action]

---

### On Track

Deals with no significant risk flags this week:
[list of account names and stages]

These deals were checked — nothing material surfaced.

---

### Contact Flags

Contacts who have departed or changed roles across the pipeline:

| Account | Contact | Previous Title | Flag | Recommended Action |
|---|---|---|---|---|

Privacy rules — apply to every row:
- Names: initials only (e.g. J.K.)
- Tag the table: Contacts confirmed live via Lusha connector,
  [date]

---

### Unresolved Accounts

Accounts that could not be matched in Lusha:
[list of account names or domains]

Recommend verifying company name or domain and re-running.

---
Built by: Lusha
Tools: Claude, Lusha
Type: Skill

FAQ

  • Do I need anything beyond Lusha in Claude?

    No. The skill runs entirely through the Lusha in Claude connector. Connect it once in Claude settings. Optional: connect your CRM if you want the skill to pull existing deal context — stage, activity history, and close date — before running the risk check.

  • How do I give it my pipeline?

    Paste your deal list directly into the chat — account name, deal stage, and any key contacts you want verified, one deal per line. If you run this weekly, the fastest setup is a Claude Project with your pipeline saved as a custom instruction. The skill reads it automatically every time without re-pasting.

  • How is this different from the Weekly Pipeline Review play?

    The Weekly Pipeline Review play is a one-time prompt — run it, get a review. This skill is installable and reusable. Save your pipeline once in a Claude Project and the skill runs against it every week. It also adds buying group coverage auditing and contact verification per deal — so you know not just that a deal is at risk, but exactly why.

  • Can a sales manager run this across a rep's full pipeline?

    Yes — and that’s one of the strongest use cases. Paste the rep’s full deal list before a 1:1. The skill surfaces every risk factor per deal so the conversation is about what to do next, not what’s going on. No more deals going quiet without anyone noticing.

  • What if a key contact has left one of my deals?

    The skill flags it in the Contact Flags section — with the contact’s previous title and a recommended action for who to re-thread with. A champion departure mid-deal is one of the highest-risk signals there is. The skill catches it before the deal goes dark.

Related Plays

Ready to run this?

Connect once, run anywhere. Works in Claude, ChatGPT, n8n, Clay, or any agent connected to Lusha.

Get free access Read the Docs