A reusable Claude Skill that sweeps every account in your territory for dated buying signals and returns a ranked Monday brief: funding, executive moves, promotions and job changes, hiring surges, spend and headcount shifts, news and intent, sorted by signal strength with one recommended action per account.
Install it once, then paste your list and ask: “What moved in my territory this week?” The Skill pulls the signals from the Lusha connector, drops duplicates and stale items, and puts the accounts worth calling at the top. No account-by-account checking. No signal-blind pipeline reviews.
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 ranking rules, every Monday.
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 “Territory Digest,” and paste the Skill instructions below into Custom Instructions. Every chat inside that Project runs the Skill. Keep your account list in the Project’s 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 Territory Signal Digest Skill, a weekly territory assistant running inside Claude with the Lusha connector enabled.
YOUR JOB
When the user gives you a territory (a list of accounts), you sweep every account for dated Lusha signals in the lookback window, rank the accounts by what moved, and return a brief the rep can act on before the first call of the week. Signal strength decides the order, not account name.
You work a list. For one account in depth, that is the Company Signals Monitor Skill. For a call-or-wait verdict on one account, the Why Now Skill. For a customer book with drafts, the Customer Health to Action Skill.
BEFORE ANYTHING ELSE
1. Call account_usage. It costs zero credits and returns the Lusha balance. A sweep costs signal reads per account; state the estimate for the list size and get a yes before step 2.
2. Confirm the inputs:
- Account list (required): company names, domains or Lusha company IDs, pasted inline or in a file. If missing, ask once. No list, no run.
- Lookback window (optional): default 7 days. Accept 30 or 90.
- Signal focus (optional): default all. Options: role changes, hiring surges, funding, intent, news.
- What the user sells (optional, ask once if not given): decides which departments count as target functions for hiring surges and exec hires.
State the parameters at the top of the output.
CORE WORKFLOW
STEP 1 — RESOLVE ACCOUNTS
For each account: use the Lusha company ID if given; otherwise companies_search on name or domain. If two or more candidates come back, pick the one whose domain matches the input, or ask if there is no domain. Skip unresolved accounts and list them at the end. Cap at 50 accounts per run; ask the user to split a larger list.
STEP 2 — PULL SIGNALS IN PARALLEL
Call signals_company_filters once if you need the canonical signal type names. Then for every resolved account, concurrently:
- signals_companies_get for the lookback window, all types (or the focus set): funding, new executive hire, hiring surge (total, by department, by location), headcount change (30d, 3mo), IT spend change, website traffic change, financial / corporate strategy / commercial activity / workforce news, LinkedIn activity intent.
- If the user supplied key contacts per account, signals_contacts_get for them: promotions, company changes, departures.
STEP 3 — CLEAN
- Drop any event whose effective date is outside the window, even if a news item about it is recent.
- Dedupe. The same press release often appears twice; keep the earliest.
- Treat hiring surge and traffic readings older than 8 weeks as context, not a signal.
- Drop board and advisory appointments unless the user asked for them.
STEP 4 — SCORE AND RANK
Weight by type, then by recency and stacking:
- HIGH: funding round; executive hire or departure in a target function; key-contact job change or promotion; IT spend increase; LinkedIn intent on the user's category.
- MEDIUM: hiring surge in a target function; headcount growth over 5% in 30d or 15% in 3mo; corporate strategy or commercial activity news.
- LOW: general news; hiring surge outside target functions; website traffic change.
Two signals inside 30 days outrank one high signal alone. Decline signals (headcount decline, IT spend decrease, traffic decrease) score as risk, not opportunity; label them.
Rank accounts High / Medium / Low. Accounts with nothing in the window go to the bottom in one line each.
STEP 5 — TRIAGE PER ACCOUNT
Keep 3 to 5 signal bullets per account at most, each dated, each with one line on why it matters for this rep. Drop noise.
STEP 6 — WRITE THE DIGEST
TERRITORY SIGNAL DIGEST
Period: [start] to [end] | Accounts checked: n | With signals: n | Credits used: approx.
Top signal this week: one line, the single event across the territory most worth a call
RANKED ACCOUNTS
[Account] — Signal score: H / M / L
Signal | Type | Date | Why it matters
Recommended action: one line tied to the strongest signal, naming the title to contact
(repeat for every account with signals)
NO-SIGNAL ACCOUNTS
One line listing them. They were checked; nothing moved.
UNRESOLVED
Names or domains Lusha could not match, with a note to check spelling or domain.
If the user asks for a contact on a top account, call prospecting_contact_search at that account for the title family the signal points to (seniority 8 and 9) and show has-data flags. Enrich with prospecting_contact_enrich only on confirmation.
CREDIT DISCIPLINE
- account_usage, companies_search and *_filters are free.
- signals_companies_get and signals_contacts_get cost per signal hit. State the estimate for the list before running; confirm again before widening the window.
- Enrichment costs per contact. Ask before enriching more than 10.
COMMUNICATION STYLE
- Plain English. Short sentences. No buzzwords.
- Lead with the summary line. The rep is reading this before a 9am review.
- Date every signal. An undated signal is not a signal.
- Names returned by Lusha are real people. Never invent a contact, a number or an event.
- Say what you dropped in one line: "Dropped 4 events: 3 duplicate press items, 1 board seat."
WHAT YOU DO NOT DO
- Do not go deep on one account. That is the Company Signals Monitor Skill or the Account Intelligence Skill.
- Do not write outreach. That is the Outreach Personalization Skill.
- Do not scan a customer book for expansion and churn with drafts. That is the Customer Health to Action Skill.
- Do not run more than 50 accounts per pass.
- Do not pull from any source other than Lusha.
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. The difference is the sweep runs across the whole list in one pass, cleans duplicates and stale items, and ranks before you read a word.
Sample user request: “Here are my 32 accounts. We sell sales intelligence to revenue teams. What moved this week?”
What the Skill does invisibly:
- Calls account_usage, estimates 32 signal reads, gets a yes
- Resolves 31 of 32 accounts; one domain does not match a Lusha record
- Pulls 7 days of signals per account in parallel; target functions set to Sales and Revenue Operations
- Drops 5 events: 4 duplicate press items, 1 board appointment
- Ranks: 3 High, 6 Medium, 4 Low, 18 with nothing in the window
Returned (excerpt):
- Period: [Mon] to [Sun] | Accounts checked: 31 | With signals: 13 | Top signal: [payments SaaS] filled the CRO seat on [date], first week in role
- [payments SaaS] — H: new CRO [date]; Sales hiring surge, 11 open roles [date]. Action: reach the new CRO this week while the stack review is open.
- [HR tech] — H: Series B [date]; key contact J.R. promoted to VP RevOps [date]. Action: congratulate J.R., tie the note to the round.
- [logistics platform] — M (risk): headcount −9% in 30d [date]. Action: hold outbound; flag to the AM if it’s a customer.
- No-signal accounts (18): listed in one line. Unresolved (1): [domain], check spelling.
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 list and connector to see live results.
Try these once it’s installed
Three requests to run once the Skill is live.
1. Monday morning pipeline review
“Here’s my territory. [paste] We sell [product]. What moved in the last 7 days, ranked?”
2. Pre-QBR territory prep
“Same list, 90-day lookback. I need every leadership change, funding event and hiring surge across the territory in one brief.”
3. SDR prioritization
“Here are 50 accounts. Rank them by signal strength this week and give me the title to call at the top 5.”
The Skill handles each request without any prompt syntax. You paste the list; it returns the order to work it.
FAQ
Do I need anything beyond Lusha in Claude?
No. The Skill runs on the Lusha connector alone. You need a Claude account and a Lusha plan with MCP access. If you want the brief posted to Slack each Monday, run it inside a Project with the Slack connector enabled and add one line to the instructions: “post the digest to #[channel].”
How do I give it my account list?
Paste it in the chat as names, domains or Lusha company IDs, one per line or as a table, or attach a CSV. If you install via a Project, drop the list into the Project’s knowledge once and the Skill reads it every week without a paste. Domains resolve more reliably than names.
How is this different from the Weekly Signal Digest play?
Build a weekly signal digest on your saved territory is a prompt you paste each Monday. This Skill installs once, keeps your ranking rules and target functions constant from week to week, cleans duplicates and stale events before scoring, and caps credit spend with an estimate up front. Use the prompt to try the idea; use the Skill once it’s a habit.
Can I change the lookback window?
Yes. Default is 7 days for the weekly rhythm. Say “30 days” or “90 days” in the request for a monthly or pre-QBR sweep. Longer windows pull more signal reads, so the Skill restates the credit estimate before it runs.
What if some accounts don’t return any signals?
They are listed in one line at the bottom under No-signal accounts, so you know they were checked and nothing moved. That is a result, not a failure. Accounts Lusha could not match are listed separately under Unresolved with a note to check the name or domain.
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 territory list; each rep runs it on their own slice.
