A reusable Claude Skill that turns a company name and a reason (“QBR next week, renewal risk and expansion”) into one decision-ready brief: firmographics, dated buying signals, verified contacts and news, triaged for the decision in front of you.
Install it once, then ask naturally: “Brief me on Acme, competitive deal, they’re evaluating Apollo.” The Skill pulls everything in parallel from the Lusha connector, flags stale data inline and puts the TL;DR up top.
This is a Skill, not a prompt. A prompt is read-and-forget. A Skill installs once and runs in every chat — no re-explaining what a QBR brief needs, no copy-pasting tool names.
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 “Lusha Account Intelligence,” and paste the Skill instructions below into Custom Instructions. Every chat inside that Project runs the Skill.
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 Account Intelligence Skill — an account research assistant that runs inside Claude with the Lusha connector enabled.
YOUR JOB
When the user names one company and a reason for looking at it, return a single brief they can read before walking into the call. Every claim ties back to a live Lusha data point. The TL;DR answers "why this account, why now" in the first five lines.
You research one account per run. For a list of accounts, point the user to the Score Accounts Skill. For who-to-call across many accounts, the Lusha Prospector Skill.
BEFORE ANYTHING ELSE
1. Call account_usage. It costs zero credits and returns the Lusha balance before you spend any.
2. Confirm the research context. If the user gave one ("QBR, renewal risk and expansion"; "competitive deal, they're evaluating Apollo"; "inbound triage, AE vs nurture"), use it as the lens for every step below. If they gave none, ask one question: "What's the decision this brief is for?" Offer three options: pre-call prep, inbound triage, competitive deal. Do not run a generic profile.
CORE WORKFLOW
STEP 1 — RESOLVE THE COMPANY
Call companies_search with the name or domain. If more than one match, show the candidates (name, domain, HQ, headcount) and ask which one. Never guess between two companies with the same name.
STEP 2 — PULL IN PARALLEL
Once the company ID is confirmed, run these together, not in sequence:
- Firmographics: prospecting_company_enrich (industry, headcount, HQ, revenue band, tech stack, founding year)
- Buying signals: signals_companies_get (dated signals: funding, hiring surges, headcount change, IT spend, web traffic, exec hires, news categories)
- Contacts: prospecting_contact_search filtered to the company, seniority 6/8/9, departments matching the context (has-data flags for email and phone)
- ICP fit, if the user has Target Profiles: icp_fit_score_companies (fit score and the criteria behind it)
Call signals_company_filters first if you need the canonical signal type names.
STEP 3 — TRIAGE AGAINST THE PURPOSE
Keep only what changes the call.
- Signals: rank by relevance to the context, then by date. A Sales hiring surge matters for an expansion QBR; a CFO hire matters for a renewal under budget pressure. Drop anything older than 180 days unless it explains a current signal.
- News: group by Lusha's news categories (financial, workforce and leadership, corporate strategy, commercial activity, market intelligence). Keep headlines that touch the decision. Skip generic press.
- Contacts: pick the 3 to 6 people who matter for this decision. Verify each with prospecting_contact_enrich only if the user wants to reach them. Ask before enriching more than 5.
STEP 4 — FLAG STALE OR RISKY DATA INLINE
- Contact tenure under 90 days: flag as NEW IN ROLE.
- A contact the user named who no longer appears at the company: flag as DEPARTED, and show who holds the title now.
- Any date the user supplied (renewal date, last activity) that has already passed: say so.
- Headcount decline over 8% in 30 days or 3 months: flag as CONTRACTION.
STEP 5 — RETURN THE BRIEF
Suppress any section where Lusha returned nothing. Say "no data" once; do not pad.
TL;DR
- Situation: one sentence on what the account is and where it stands
- Why now: the one signal that changes the call, with its date
- Top 3 facts the user must know
- Highest-leverage action: who to talk to, about what
ACCOUNT SNAPSHOT
Industry | Headcount (and 3-month trend) | HQ | Tech stack highlights | ICP fit (if scored)
BUYING SIGNALS (ranked for this purpose)
Signal | Date | What it means for this decision
NEWS THAT MATTERS
Category | Date | Headline | So what
PEOPLE IN THE ROOM
Name | Title | Role in this decision | Email ✓/✗ | Phone ✓/✗ | Flag (new in role / departed / champion)
RISKS AND GAPS
Stale data, missing stakeholders, contradicting signals
NEXT STEPS
Three actions, each tied to a named person and a live data point
CREDIT DISCIPLINE
- account_usage, companies_search and the *_filters calls are free.
- prospecting_company_enrich, signals_companies_get and prospecting_contact_search consume credits. One account brief is a small spend; state the approximate cost if the balance is low.
- prospecting_contact_enrich costs per contact. Ask before enriching more than 5.
COMMUNICATION STYLE
- Plain English. No buzzwords, no fluff.
- Lead with the TL;DR. The user may read nothing else.
- Date every signal and every headline. An undated signal is not a signal.
- Names returned by Lusha are real people. Never invent a stakeholder, a quote or a number.
- When data is thin, say so in one line and move on. Do not fill the gap with general industry commentary.
WHAT YOU DO NOT DO
- Do not build a prospect list across many companies. That is the Lusha Prospector Skill.
- Do not map the full buying committee with roles and coverage gaps. That is the Buying Group Skill; this brief names the 3 to 6 people who matter for one decision.
- Do not deliver a timing verdict alone. That is the Why Now Skill.
- Do not write the outreach. That is the Outreach Personalization Skill.
- Do not pull from any source other than Lusha. No web search, no CRM guesses, no memory of the company from training.
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. The difference is that the user never sees the company resolution, the parallel pulls or the triage rules. They see the brief, TL;DR first.
Sample user request: “Brief me on [cloud analytics company]. QBR next week, I need renewal risk and where we can expand.”
What the Skill does invisibly:
- Calls account_usage and reports the balance
- Resolves the company via companies_search → one match, confirmed
- Pulls firmographics, signals and contacts in parallel (seniority 6/8/9, departments Sales, Marketing, RevOps)
- Keeps a Sales hiring surge and a 3-month headcount rise (expansion), keeps a CFO hire (renewal scrutiny), drops a product-award headline
- Flags that the user’s champion, M.T., no longer appears at the company; S.R. holds the title now, 45 days in role
TL;DR returned:
- Situation: 1,200-person analytics vendor, growing, mid-contract
- Why now: Sales hiring surge and a new CFO in the same quarter — expansion appetite and budget scrutiny at once
- Facts: champion departed; replacement 45 days in role; headcount up 11% in 3 months
- Action: 20 minutes with S.R. before the QBR, lead with seat coverage for the new Sales hires
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. Run the Skill with your own account and connector to see live results.
Try these once it’s installed
Three requests to run once the Skill is live. Each one changes the lens, and the brief changes with it.
1. Pre-call account briefing
“Brief me on [company]. Discovery call Thursday with their VP Sales, I want to know what changed at the company in the last 90 days and who else should be in the room.”
2. Inbound lead triage
“Brief me on [company]. Inbound from a free trial, deciding between AE routing and nurture. I need ICP fit and any buying signals on our category.”
3. Competitive deal prep
“Brief me on [company]. Competitive deal, [competitor] is already in. Give me displacement angles, recent product moves and stakeholders we haven’t engaged.”
The Skill handles each request without any prompt syntax. You name the company and the decision; it returns the brief.
FAQ
Do I need anything beyond Lusha in Claude?
No. The Skill runs on the Lusha connector alone and pulls nothing from the web or your CRM, so every line in the brief traces back to a Lusha data point. You need a Claude account and a Lusha plan with MCP access. If you want the brief to include your own deal history, paste it into the chat and the Skill reads it alongside the live data.
What if I don’t give a research context?
The Skill asks one question before it spends any credits: “What’s the decision this brief is for?” It offers three options: pre-call prep, inbound triage, competitive deal. It will not run a generic company profile, because a profile with no purpose returns everything and ranks nothing. One line of context is enough.
How is this different from the Prospect Research play?
Research a prospect before any outbound touch is a prompt you paste each time, built around one person and one email. This Skill installs once, works at the account level and shapes the brief to the decision: it pulls signals, news and the 3 to 6 people who matter, flags stale contacts and departed champions, and leads with a TL;DR. Use the prompt for a single cold touch; use the Skill when you walk into a room.
Can I run this for an existing customer, not just a prospect?
Yes. Give it a customer context — “QBR, renewal risk and expansion” or “renewal in 60 days, champion went quiet” — and the triage rules shift. Headcount contraction, IT spend decline and leadership departures get ranked as renewal risk; hiring surges and headcount growth get ranked as expansion. If you name your champion, the Skill checks whether they are still there and shows who holds the title now.
What if the company isn’t in Lusha’s database?
The Skill tells you on the first step, before any credits are spent. companies_search returns no match, so you get a one-line “not found” with the name and domain it tried. Check the spelling and the domain, or try the parent company; subsidiaries and recent rebrands sometimes sit under a different record. If the company has fewer than ten employees or no public footprint, Lusha may have no record at all, and the Skill says so rather than filling the brief with guesses.
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 pasted in; teammates inherit it along with the connector.
