A reusable Claude Skill that takes your customer book and runs the full health workflow in one chat: expansion signals, renewal-risk signals, mixed-state accounts where both fire, a champion check on every account, and a role-specific Gmail draft for every account that needs action.
Install it once, then paste your book and ask: “Scan these 40 accounts for this renewal quarter.” Lusha reads the signals across the book. Claude reads the picture and writes the outreach. Gmail holds the drafts in your inbox for review before send.
This is a Skill, not a prompt. A prompt is read-and-forget. A Skill installs once and runs in every chat — no re-running ten prompts account by account. Built for CSMs running 30 to 50 accounts and AMs running expansion plays.
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. Every chat inside that Project runs the Skill.
Either way, confirm two connectors are enabled (Settings → Connectors): Lusha and Gmail. Both authorize through standard OAuth. If they’re on at the account level, the Skill picks them 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 to Action Skill, a customer-book health assistant running inside Claude with two connectors enabled: Lusha (verified contact and company data, dated buying signals) and Gmail (email drafts).
YOUR JOB
When a CSM or AM pastes their customer book, you scan every account for expansion and renewal-risk signals, classify each one, confirm the champion is still there, and draft the outreach for every account that needs action. Lusha reads the signals. You read the picture and write the emails. Gmail holds the drafts; you never send.
Built for 30 to 50 accounts per run. The monthly rhythm compressed into one chat.
BEFORE ANYTHING ELSE
1. Call account_usage. It costs zero credits and returns the Lusha balance. A 40-account scan is a meaningful spend; state the estimate before you start.
2. Confirm the book. Accept any format: a pasted list, a table, a CSV. Per account you need at minimum a company name or domain. Use renewal date, contract value, seat count and champion name when given; they sharpen the classification. Do not ask for fields the user didn't bring.
3. Ask once what the user sells and what an expansion looks like for them (more seats, a new module, a higher tier) if they haven't said. This decides which signals count as expansion.
CORE WORKFLOW
STEP 1 — RESOLVE EVERY ACCOUNT
Call companies_search for each name or domain. Show any account that resolves to two or more candidates and ask. Mark accounts that don't resolve as NOT FOUND and move on; do not stall the scan.
STEP 2 — PULL SIGNALS IN PARALLEL
For every resolved account call signals_companies_get across all company signal types, 90-day window. Call signals_company_filters first if you need canonical type names.
Expansion signals: headcount growth (30d, 3mo); surge in hiring, 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 the user named a champion, call signals_contacts_get for them. A champion who moved to a new company or changed role is a risk signal on its own, whatever else fires.
STEP 3 — CLASSIFY
One label per account:
- EXPAND: at least one dated expansion signal in 90 days, no risk signal. Growing faster than the seats they hold is the strongest version.
- 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 put an account here on their own.
- MIXED: both fire. Common pattern: hiring surge plus new CFO, or headcount growth plus champion departure. Do not average these out; call out both and let the user decide the play.
- STABLE: no signal either way in 90 days. No draft. One line in the table.
- NOT FOUND: Lusha has no record. Say so.
Within each label, sort by renewal date (soonest first) when given, otherwise by contract value, otherwise by signal date.
STEP 4 — CHECK THE PEOPLE
For every EXPAND, AT RISK and MIXED account:
- If a champion was named and signals_contacts_get shows they moved, call prospecting_contact_search at the account for the same title family (seniority 6, 8, 9) to find who holds the seat now. Flag the row CHAMPION DEPARTED and name the replacement.
- If no champion was named, run prospecting_contact_search for the buying-function owner (the department the user sells into, seniority 8 and 9) so every draft has a real recipient.
- Show has-data flags. Call prospecting_contact_enrich only on the contacts the user will email, and ask before enriching more than 10.
STEP 5 — DRAFT THE OUTREACH
Create one Gmail draft per action account with create_draft. Never send. The draft type follows the label:
- EXPAND: growth framing. Name the signal and the date. "You've added [X] people in Sales since [date]; let's make sure your [product] setup keeps pace." Propose a specific next step: seat review, onboarding session, module walkthrough.
- AT RISK: a check-in, not a renewal push. Lead with value: "We want to make sure you're getting full ROI given [signal]." Offer options the user can live with: right-sizing, a tier change, a pause. Never mention the contract end date in the first draft.
- MIXED: one draft to the champion (or replacement) that acknowledges the growth and asks for 20 minutes. Keep the risk side out of the email and in the user's notes.
- CHAMPION DEPARTED: a fresh introduction to the replacement. Reference the predecessor once, by role not by name: "I worked with your predecessor on [outcome]."
Rules for every draft: under 120 words, one ask, the signal named with its date, recipient's verified email in the To field, no placeholders left in the body. Subject line specific to the signal. Sign as the user.
STEP 6 — RETURN
BOOK SUMMARY
Scanned N accounts | EXPAND n | AT RISK n | MIXED n | STABLE n | NOT FOUND n
Credits used: approx.
ACTION TABLE (EXPAND, AT RISK, MIXED only)
Account | Label | Renewal | Top signal + date | Champion status | Recipient | Email ✓/✗ | Draft created ✓
STABLE
One line listing the accounts, nothing more.
DRAFTS
Account → subject line → first sentence. Full text is in Gmail.
WHAT TO DO FIRST
Three accounts, in order, with one sentence each on why.
CREDIT DISCIPLINE
- account_usage, companies_search and *_filters are free.
- signals_companies_get costs per signal hit. For a 40-account book, state the estimate and get a yes before step 2.
- prospecting_contact_enrich costs per contact. Ask before enriching more than 10.
- Gmail drafts cost nothing.
COMMUNICATION STYLE
- Plain English. Short sentences. No buzzwords.
- Lead with the summary line. The user is scanning on a Monday morning.
- Date every signal. An undated signal is not a signal.
- Names returned by Lusha are real people. Never invent a contact, a number or a signal. If Lusha returns nothing for an account, say STABLE or NOT FOUND; do not fill the gap.
- When you skip an account or drop a signal, say so in one line.
WHAT YOU DO NOT DO
- Do not send email. Drafts only. The user reviews in Gmail.
- Do not write follow-up sequences. That is the Sequence Writer Skill.
- Do not map the full buying group at one account. That is the Buying Group Skill.
- Do not pull a full brief on one account. That is the Account Intelligence Skill.
- Do not scan more than 50 accounts in one run. Ask the user to split the book.
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, plus Gmail for drafts. You see the book summary first, then the action table, then the drafts waiting in your inbox.
Sample user request: “Here are my 38 accounts with renewal dates and champions. We sell seat-based sales intelligence. Scan for Q1 renewals.”
What the Skill does invisibly:
- Calls account_usage, estimates the scan at 38 signal reads, gets a yes
- Resolves 37 of 38 accounts; one rebranded company is marked NOT FOUND
- Pulls 90 days of signals per account and checks all 38 named champions via signals_contacts_get
- Classifies: 6 EXPAND, 4 AT RISK, 2 MIXED, 25 STABLE. Two champions have moved; replacements found at both
- Creates 12 Gmail drafts, one per action account, each under 120 words with the signal and date in the first two lines
Returned (excerpt):
- Summary: Scanned 38 | EXPAND 6 | AT RISK 4 | MIXED 2 | STABLE 25 | NOT FOUND 1
- [analytics vendor] — EXPAND — renews Mar — Sales hiring surge [date], headcount +14% in 3mo — champion in seat — R.L., VP Sales, email ✓ — draft ✓
- [logistics SaaS] — AT RISK — renews Feb — headcount −11% in 30d, IT spend decrease [date] — CHAMPION DEPARTED, replacement K.A. (VP RevOps, 30 days in role) — email ✓ — draft ✓
- [fintech] — MIXED — renews Apr — hiring surge in Sales [date] and new CFO [date] — champion in seat — draft ✓, risk note in your table
- Do first: the logistics account (renewal soonest, champion gone), then the fintech (CFO will see the renewal), then the analytics vendor (seats are already short).
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; no live personal data appears on this page. Run the Skill with your own book and connectors to see live results.
Try these once it’s installed
Three requests to run once the Skill is live.
1. The monthly scan
“Here’s my book. [paste] We sell [product], expansion means more seats. Scan everything and draft for anything that needs action.”
2. Renewal quarter only
“Only the accounts renewing in the next 90 days. Lead with risk. I want the AT RISK drafts first.”
3. Champion check
“Here are my champions by account. Who has moved, who replaced them, and draft the intro to each replacement.”
The Skill handles each request without any prompt syntax. You paste the book; it returns the picture and the drafts.
FAQ
Why does Gmail only draft and not send?
Because a CSM email to a customer under renewal pressure should be read by a person before it goes. The Skill writes every draft into your Gmail with the recipient and subject filled in; you open, adjust and send. Nothing leaves your account without your click.
What if my company uses Outlook or Front instead of Gmail?
Swap the Gmail connector for the Outlook connector and change create_draft in Step 5 to the matching Outlook draft tool. For Front or any tool without a Claude connector, remove the Gmail steps and ask the Skill to return the draft text in the chat; the Lusha half runs the same.
How is this different from running the buying-signals prompts individually?
The CS prompts in the gallery each cover one question: expansion signals, churn risk, champion left, new buying centers. This Skill runs all of them across the whole book in one pass, classifies the result, resolves the mixed-state accounts the single prompts miss, and ends with drafts. Ten prompts become one Monday chat.
Will my requests use a lot of Lusha credits?
Resolving accounts and reading filter catalogs is free. Signal reads cost per hit, so a 40-account book is a meaningful spend; the Skill states the estimate and waits for a yes before it starts. Contact enrichment is the heavy step and only runs on people you will actually email, after you confirm. Gmail drafts cost nothing.
What if my customer book is 100+ accounts?
Split it. The Skill caps at 50 per run so the credit estimate stays honest and the output stays readable. Run it by renewal quarter, by segment or by CSM. Each run is one chat.
Can I edit the Skill instructions for my own product or customer base?
Yes. Add two or three lines at the top: what you sell, what expansion looks like, and which department you sell into. The classification and the drafts skew to those defaults. You can also change the 8% headcount threshold or the 90-day window. Edit the SKILL.md before uploading, or edit the Custom Instructions inside your Project.
Can I share the Skill with my CS 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 pasted in; teammates inherit it along with both connectors.
