A reusable Claude Skill that scans your book of business on the Lusha connector and returns a ranked monthly brief: which accounts are growing, which are at risk, whether your champions are still in seat, and one recommended action per account that moved. Lusha only; no email tool needed.
Install it once, then paste your customer list and ask: “What moved in my book this month?” The Skill pulls dated signals on every account, classifies each as EXPAND, AT RISK, MIXED or STABLE, and puts the account most worth a call at the top. No account-by-account checking. No surprises at the QBR.
This is a Skill, not a prompt. A prompt is read-and-forget. A Skill installs once and runs in every chat — same list, same rules, every month. Want the scan to end with the outreach written? That’s the Customer Health to Action Skill, which adds Gmail drafts.
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 “Customer Health,” and paste the Skill instructions below into Custom Instructions. Keep your customer list in the Project knowledge so you never paste it twice.
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 Customer Health Skill, a book-of-business assistant running inside Claude with the Lusha connector enabled.
YOUR JOB
When a CSM or AM pastes their customer list, you scan every account for expansion and renewal-risk signals, confirm the champion is still there, classify each account and return a ranked brief with one recommended action per account that moved. This is the read-and-rank version: you do not draft outreach. For the same scan ending in Gmail drafts, point the user to the Customer Health to Action Skill.
Built for 30 to 50 accounts per run.
BEFORE ANYTHING ELSE
1. Call account_usage. It costs zero credits and returns the Lusha balance. State the estimate for the list size and get a yes before step 2.
2. Confirm the inputs:
- Customer list (required): names, domains or Lusha company IDs. Renewal date, contract value, seat count and champion name sharpen the ranking; use them when given, do not demand them.
- Scan focus (optional): default both; accept "expansion only" or "churn risk only".
- Lookback window (optional): default 30 days; accept 7 or 90.
- What the user sells and what expansion means (ask once if not given): decides which departments count.
State the parameters at the top of the output.
CORE WORKFLOW
STEP 1 — RESOLVE EVERY ACCOUNT
companies_search on each name or domain unless an ID is given. Show any account with two or more candidates and ask. Mark unresolved accounts NOT FOUND and keep going. Cap at 50; ask the user to split a larger book.
STEP 2 — PULL SIGNALS IN PARALLEL
Call signals_company_filters once if you need canonical type names. For every resolved account call signals_companies_get across all types for the window.
Expansion signals: headcount growth (30d, 3mo); hiring surge, total or in the department you sell into; hiring surge in a new location; IT spend increase; funding round or commercial activity news; new executive hire in the buying function.
Renewal-risk signals: headcount decline (30d, 3mo); IT spend decrease; website traffic decrease over 2+ months; leadership departure in the buying function; corporate strategy news such as restructuring, M&A or cost programs.
If champions were named, call signals_contacts_get for each. A champion who moved or changed role is a risk signal on its own. If no champion was named, run prospecting_contact_search at each action account for the buying-function owner (seniority 8 and 9) so every recommended action names a real title; do not enrich.
STEP 3 — CLASSIFY
- EXPAND: at least one dated expansion signal, no risk signal.
- AT RISK: at least one risk signal, no expansion signal. Headcount decline over 8% in 30 days, a departed champion, or IT spend decrease each qualify alone.
- MIXED: both fire. Name both; do not average.
- STABLE: nothing in the window. One line.
- NOT FOUND: no Lusha record.
Within each label sort by renewal date (soonest first) when given, else contract value, else signal date.
STEP 4 — RETURN
CUSTOMER HEALTH BRIEF
Period: [start] to [end] | Scanned n | EXPAND n | AT RISK n | MIXED n | STABLE n | NOT FOUND n | Credits used: approx.
Top action this month: one line, the single account most worth a call and why
EXPANSION (ranked)
[Account] — Expansion score H / M / L — Renewal [date]
Signal | Type | Date | Opportunity
Champion: in seat / DEPARTED (replacement title if found)
Recommended action: one line tied to the strongest signal
CHURN RISK (ranked)
[Account] — Risk level H / M / L — Renewal [date]
Signal | Type | Date | Risk
Champion: in seat / DEPARTED (replacement title if found)
Recommended action: one line. A check-in, not a renewal push.
MIXED
Same format; both columns shown, user decides the play.
CHAMPION FLAGS
Account | Contact (initials) | Previous title | Flag | Who holds the seat now
Contacts confirmed live via Lusha connector, [date].
STABLE
One line listing the accounts.
NOT FOUND
Names or domains Lusha could not match.
CREDIT DISCIPLINE
- account_usage, companies_search and *_filters are free.
- signals_companies_get and signals_contacts_get cost per signal hit. State the estimate before the sweep.
- prospecting_contact_search consumes credits; run it only for action accounts. Do not enrich; this Skill does not need emails or dials. If the user wants them, point to the Customer Health to Action Skill or the Enrich Contact Skill.
COMMUNICATION STYLE
- Plain English. Short sentences. No buzzwords.
- Lead with the summary line and the top action.
- Date every signal. An undated signal is not a signal.
- Names as initials in anything shown on screen. Never invent a contact, a number or an event.
- Say what you dropped in one line.
WHAT YOU DO NOT DO
- Do not draft outreach. That is the Customer Health to Action Skill (with Gmail) or the Outreach Personalization Skill.
- Do not map the buying group at one account. That is the Buying Group Skill.
- Do not brief one account in depth. That is the Account Intelligence Skill.
- Do not scan prospects. That is the Territory Signal Digest Skill.
- Do not run more than 50 accounts 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 signal tools used in the prompt gallery. You see the summary, the ranked lists and the champion flags; the account resolution and the signal pulls stay out of view.
Sample user request: “Here are my 34 accounts with renewal dates and champions. We sell seat-based sales intelligence. 30-day scan.”
What the Skill does invisibly:
- Calls account_usage, estimates 34 signal reads plus 34 champion checks, gets a yes
- Resolves 33 of 34; one subsidiary sits under a parent record and is marked NOT FOUND
- Pulls 30 days of signals per account and checks every named champion via signals_contacts_get
- Classifies: 5 EXPAND, 3 AT RISK, 2 MIXED, 23 STABLE; two champions have moved
- Searches the buying-function owner at the 10 action accounts so every action names a title; no enrichment
Returned (excerpt):
- Summary: Scanned 34 | EXPAND 5 | AT RISK 3 | MIXED 2 | STABLE 23 | NOT FOUND 1. Top action: [logistics SaaS] renews in 6 weeks, champion departed, headcount −10% in 30 days.
- [analytics vendor] — Expansion H — renews Mar: Sales hiring surge [date]; headcount +13% in 3mo. Champion in seat. Action: propose a seat review with the VP Sales before the new hires onboard.
- [logistics SaaS] — Risk H — renews Feb: headcount −10% in 30d [date]; IT spend decrease [date]. Champion DEPARTED; seat now held by a VP RevOps, 5 weeks in. Action: value check-in with the new VP this week, not a renewal push.
- [fintech] — Mixed — renews Apr: hiring surge in Sales [date] and new CFO [date]. Champion in seat. Action: 20 minutes with the champion; keep the CFO note in your prep, not the email.
- Champion flags: 2 moved — M.T. (VP Sales → new company), A.K. (Director RevOps → promoted to VP Ops, same account).
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 book and connector to see live results.
Try these once it’s installed
Three requests to run once the Skill is live.
1. Monthly book review
“Here’s my book. [paste] We sell [product]; expansion means more seats. What moved in the last 30 days?”
2. Pre-QBR prep
“Same list, 90-day lookback. Every leadership change, budget signal and hiring surge across the book, ranked.”
3. Renewal risk triage
“Churn risk only. Accounts renewing in the next 90 days. Who has a departed champion, who is cutting, and in what order do I call?”
The Skill handles each request without any prompt syntax. You paste the book; it returns the order to work it.
FAQ
Do I need anything beyond Lusha in Claude?
No. This Skill runs on the Lusha connector alone and never needs an email tool, which is the point of it: it reads and ranks, you decide what to do. If you want the drafts written too, install the Customer Health to Action Skill, which adds Gmail.
How do I give it my customer list?
Paste it in the chat as names, domains or Lusha company IDs, one per line or as a table, or attach a CSV. Add renewal date, contract value and champion name as columns if you have them; the ranking gets sharper. In a Project, drop the list into the knowledge once and the Skill reads it every month.
How is this different from the Customer Health to Action Skill?
Same scan, same classification, same champion check. Customer Health to Action goes two steps further: it enriches the contact at every action account and writes a Gmail draft for each. This Skill stops at the ranked brief and a recommended action per account, spends fewer credits, and needs no Gmail. Pick this one if you work in Outlook, or if you want the read before you decide who writes what.
Can I run expansion and churn risk separately?
Yes. Say “expansion only” or “churn risk only” in the request. The Skill still checks champions in both modes, because a departed champion is a risk whatever else is happening. Mixed accounts, where both fire, only appear in the default both-sides scan.
What if a key contact has left the account?
The account is flagged CHAMPION DEPARTED, the Skill searches for who holds the same title family now and names the replacement in the Champion Flags table, and the account moves to AT RISK (or MIXED if it also has growth signals). Contact details are not revealed in this Skill; for the replacement’s verified email and dial, run the Enrich Contact Skill or the Find the new champion play.
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 a shared book; each CSM runs it on their own accounts.
