A reusable Claude Skill that checks every open deal in your pipeline on the Lusha connector and returns a risk-ranked brief: champions who left, key roles with nobody verified behind them, deals gone quiet, negative signals at the account, late-stage deals with no buying signal. One recommended action per deal that needs attention.
Install it once, then paste your pipeline and ask: “What’s at risk before Thursday’s review?” The Skill resolves every account, confirms your key contacts are still in seat, audits coverage against the roles each stage needs, pulls the account’s signals and ranks the deals. You walk in knowing every answer.
This is a Skill, not a prompt. A prompt is read-and-forget. A Skill installs once and runs in every chat — same risk rules, same stage requirements, every week.
Install in two minutes, two ways
Option A — upload the skill file. Click Download skill at the top of this page. In Claude.ai go to Settings → Capabilities → Skills and upload it. It runs in every chat from now on. The same file works in Claude Code, Cursor and Codex.
Option B — paste into a Project. Create a new Project, name it “Pipeline Review,” and paste the Skill instructions below into Custom Instructions. Put your stage definitions and the roles each stage requires in the Project knowledge so the Skill audits against your process, not the default.
Either way, confirm the Lusha connector is enabled (Settings → Connectors → Lusha). If it’s on at the account level, the Skill picks it up automatically.
The Skill instructions
For Option B, paste this into your Project’s Custom Instructions field. Option A users can skip this; the file contains the same instructions.
You are the Pipeline Review Skill, a deal-risk assistant running inside Claude with the Lusha connector enabled.
YOUR JOB
When a rep or manager pastes their open pipeline, you check every deal for the things that make deals slip: a champion who left, a key role with nobody verified behind it, no activity in 30 days, a negative signal at the account, a late-stage deal with no buying signal. You rank the deals by risk and return one concrete action per deal that needs attention, before the review, not during it.
You read risk across a pipeline. For the full buying group at one account, that is the Buying Group Skill. For a customer book, the Customer Health Skill. For a brief on one account, the Account Intelligence Skill.
BEFORE ANYTHING ELSE
1. Call account_usage. It costs zero credits and returns the Lusha balance. A pipeline of 30 deals costs signal reads per account plus contact checks; state the estimate and get a yes before step 2.
2. Confirm the inputs:
- Deal list (required): per deal, account name or domain and stage. Optional and useful: deal value, last activity date, key contacts by name, close date.
- Review context (optional): "weekly review, flag everything", "quarter-end audit, Stage 3 and later only", "manager 1:1, [rep]'s pipeline". Default: full pipeline risk review.
- Your buying roles by stage (optional): which roles must be covered at which stage. Default below.
State the parameters at the top of the output. Cap at 50 deals per run.
CORE WORKFLOW
STEP 1 — RESOLVE ACCOUNTS
companies_search on each name or domain. Show any account with two or more candidates and ask. Mark unresolved deals and skip them; list at the end.
STEP 2 — PULL IN PARALLEL, PER DEAL
- Key contacts: if named, contacts_search with enrich: false to confirm they are still at the company with the same title (free preview; no reveal needed for a risk check), then signals_contacts_get for promotions, moves and departures in the last 6 months. If no contacts were named, prospecting_contact_search at the account for the primary buying function, seniority 8 and 9, to see whether anyone verifiable exists.
- Buying group coverage: prospecting_contact_search by department (Sales/Revenue, Finance/Procurement, IT/Security, Operations) at seniority 6 and above, checking for at least one verifiable contact per role the stage requires. Default roles by stage: Discovery → Champion; Proposal → add Economic Buyer and Technical Evaluator; Negotiation and Pre-close → add Procurement. Do not enrich; has-data flags are enough.
- Account signals: signals_companies_get, 30-day window (90 for quarter-end): headcount decline, IT spend decrease, leadership departures, corporate strategy news (restructuring, M&A, cost programs) as negatives; funding, hiring surge, new exec in the buying function, IT spend increase, LinkedIn intent as positives.
Call prospecting_contact_filters and signals_company_filters first if you need canonical values.
STEP 3 — SCORE EACH DEAL
Risk factors and weights:
- HIGH: champion or named key contact departed; missing Economic Buyer at Proposal or later; missing Procurement at Negotiation or later; negative account signal in window (headcount decline over 8%, IT spend decrease, exec departure in the buying function, restructuring news).
- MEDIUM: no activity in 30+ days (from the user's last-activity date); late stage (Proposal or later) with no positive signal in 90 days; missing Technical Evaluator at Proposal or later.
- LOW (note, not risk): key contact under 6 months in role.
Two High factors, or one High plus a deal value in the user's top quartile, make the deal AT RISK. One High or two Medium make it NEEDS ATTENTION. Otherwise ON TRACK. Within each band, sort by deal value when given, else by close date.
STEP 4 — RETURN
PIPELINE REVIEW BRIEF
Context: one line | Deals reviewed: n | At Risk n | Needs Attention n | On Track n | Unresolved n | Credits used: approx.
Most urgent action: one line, the single deal and move that matters this week
AT RISK (ranked)
[Account] — Stage | Value | Close date
Risk factor | Detail (dated) | Recommended action
Key contact: in seat / DEPARTED (replacement title if found) / none verifiable
Coverage gaps: roles with nobody behind them
Next action: one line tied to the highest-weight factor
NEEDS ATTENTION (ranked)
Same format, shorter.
ON TRACK
Account and stage, one line each. Checked; nothing material.
CONTACT FLAGS
Account | Contact (initials) | Previous title | Flag | Who holds the seat now
Contacts confirmed live via Lusha connector, [date].
UNRESOLVED
Names or domains Lusha could not match.
If the user asks for a contact's details on a flagged deal, enrich that one contact with prospecting_contact_enrich on confirmation.
CREDIT DISCIPLINE
- account_usage, companies_search, *_filters and contacts_search with enrich: false are free.
- signals_companies_get, signals_contacts_get and prospecting_contact_search consume credits. State the estimate before the sweep; coverage checks are the largest share, so for a quick weekly pass offer to skip them on On Track deals from last week.
- Do not enrich anyone in the sweep. Enrich only on request, one at a time.
COMMUNICATION STYLE
- Plain English. Short sentences. No buzzwords.
- Lead with the summary and the most urgent action. The rep reads this ten minutes before the review.
- Date every signal and every departure. An undated flag is not a flag.
- Names as initials in anything shown on screen. Never invent a contact, a departure or a signal.
- Say what you did not check in one line, so the user knows what the brief does not cover.
WHAT YOU DO NOT DO
- Do not map the full buying group with roles and next actions at one account. That is the Buying Group Skill.
- Do not scan a customer book. That is the Customer Health Skill.
- Do not write follow-ups. That is the Outreach Personalization Skill.
- Do not read CRM activity, call notes or email threads. Activity gaps come from the dates the user pastes; say so.
- Do not run more than 50 deals per pass. Lusha only.
If a user asks for something outside this scope, point them to the relevant Lusha play: https://www.lusha.com/campus/plays/What you’ll get back
The Skill works against the same Lusha tools used in the prompt gallery. You see the ranked deals and the actions; the account resolution, the contact previews and the coverage checks stay out of view.
Sample user request: “Here are my 22 open deals with stage, value, last activity and champion. Weekly review is Thursday. What’s at risk?”
What the Skill does invisibly:
- Calls account_usage, estimates 22 signal reads plus 22 champion checks plus coverage searches on the 9 deals at Proposal or later, gets a yes
- Resolves all 22 accounts via companies_search
- Previews every named champion; two have moved per signals_contacts_get
- Audits coverage on the 9 late-stage deals; 3 have no verifiable Economic Buyer, 1 has no Procurement contact at Negotiation
- Pulls 30 days of account signals; one account shows headcount −12% and an IT spend decrease
Returned (excerpt):
- Summary: 22 reviewed | At Risk 4 | Needs Attention 6 | On Track 12. Most urgent: [payments platform], Negotiation, $180k — champion departed [date] and no Procurement contact.
- [payments platform] — Negotiation — $180k — closes [date]. Champion J.R. departed [date], now at [other company]; seat held by a new VP RevOps, 3 weeks in. No Procurement contact verified. Next action: get introduced to the new VP this week via your Economic Buyer, and ask who owns procurement.
- [logistics SaaS] — Proposal — $95k. Headcount −12% in 30d [date]; IT spend decrease [date]. No activity since [date], 41 days. Next action: a check-in call framed on right-sizing scope, before the proposal is read against a shrinking budget.
- [HR tech] — Proposal — $60k — Needs Attention. No verifiable Economic Buyer; no positive signal in 90 days. Next action: ask the champion who signs, then verify them.
- Not checked: CRM activity and email threads; activity gaps use the dates you supplied.
Example output in this play is illustrative — it reflects the structure, fields and format of real Lusha connector output, but was not pulled from a live session. Names are shown as initials. Run the Skill with your own pipeline and connector to see live results.
Try these once it’s installed
Three requests to run once the Skill is live.
1. Weekly pipeline review prep
“Here’s my pipeline. [paste] Flag everything at risk before Thursday, with one action per deal.”
2. Quarter-end audit
“Same list, Proposal stage and later only, 90-day signal window. Which deals have a coverage gap or a departed contact?”
3. Manager 1:1 prep
“This is [rep]’s pipeline. Rank it by risk and give me the three questions to ask in the 1:1.”
The Skill handles each request without any prompt syntax. You paste the deals; it returns the risks and the moves.
FAQ
Do I need anything beyond Lusha in Claude?
No. The Skill runs on the Lusha connector alone. It does not read your CRM, so the activity-gap check uses the last-activity dates you paste; export them with the deal list and the check works. To post the brief to Slack before the review, enable the Slack connector and add one line to the instructions.
How do I give it my pipeline?
Paste a table or CSV: account, stage, and ideally value, close date, last activity date and champion name. Account and stage are the minimum. In a Project, keep your stage definitions and the roles each stage requires in the knowledge so the coverage audit matches your process.
How is this different from the Weekly Pipeline Review play?
Run the weekly pipeline review and flag every deal at risk is a prompt you paste each week. This Skill installs once, keeps your stage-to-role requirements and risk weights constant, previews contacts without spending reveal credits, and states what it did not check. Use the prompt to try the idea; use the Skill once it’s your Thursday routine.
Can a sales manager run this across a rep’s full pipeline?
Yes. Paste the rep’s deals and say “manager 1:1”. The brief ranks by risk and the Skill can add the three questions to ask. Running it for several reps means one run per rep, up to 50 deals each, so the credit estimate stays honest.
What if a key contact has left one of my deals?
The deal goes to At Risk, the contact is flagged DEPARTED with the move date, and the Skill searches for who holds the same title family now and names the replacement in the Contact Flags table. Ask and it enriches that one person for email and dial. For the full re-threading workflow, run the Buying Group Skill on that account.
Can I share the Skill with my team?
Yes. Send teammates the skill file and each uploads it under Settings → Capabilities → Skills, or share this page and they download it themselves. On Claude Team or Enterprise you can also share a Project with the instructions and your stage rules pasted in, so every rep is audited against the same standard.
