Territory Signal Digest Skill

Your territory changes every week. This skill tells you what moved, who changed roles, and which accounts are worth calling before your Monday pipeline review.

Overview

The Territory Signal Digest Skill runs a weekly signal sweep across every account in your territory and returns a ranked brief — sorted by signal strength, not account name. Promotions, job changes, funding rounds, hiring surges, and intent spikes all surface together, with the highest-signal accounts at the top.

Give it your account list once. Every week it pulls the latest signals via the Lusha in Claude connector, ranks accounts by what’s actually moving, and returns a brief you can act on before your first call of the week. No manual account-by-account checking. No signal-blind pipeline reviews.

The result is a Monday morning brief that tells you where to spend your time this week — backed by live Lusha data, not gut feel.

What it does

  • Full territory sweep — runs signals across every account in your list in one pass. Promotions, job changes, funding, hiring surges, and intent spikes.
  • Signal-ranked output — accounts sorted by signal strength, not alphabetically. The accounts worth calling this week are at the top.
  • Role change detection — flags contacts who have been promoted, changed companies, or joined recently. Both a risk signal and an opportunity.
  • Hiring surge detection — surfaces accounts surging hiring in functions relevant to your deal motion. A leading indicator of budget and tooling decisions.
  • Weekly cadence — designed to run every Monday morning. Install once, run weekly, never start a pipeline review blind again.

Use cases

Monday morning pipeline review

Before your first call of the week, run the skill across your territory. It returns every account that moved since last week — ranked by signal strength. You walk into your pipeline review knowing exactly which accounts to prioritize and why.

Pre-QBR territory prep

Before a quarterly review, run the skill to surface every signal across your territory from the last 90 days. Leadership changes, funding events, hiring surges, and intent spikes all surface in one brief — giving you the context to talk about every account without pulling 40 separate reports.

SDR territory prioritization

For SDRs working a large account list, run the skill weekly to identify which accounts have the strongest signals right now. Rather than working the list top to bottom, you work it signal first — highest-signal accounts get the first call, every week.

Skill definition

The instructions Claude uses to run this skill. Copy it into a .md file in your Claude Code skills folder, or paste it into a Claude project as a custom instruction.

---
name: territory-signal-digest-skill
description: >
  Run a weekly signal sweep across every account in your territory.
  Takes an account list and returns a ranked brief — promotions,
  job changes, funding rounds, hiring surges, and intent spikes,
  sorted by signal strength. Designed to run every Monday morning
  before a pipeline review.
connectors:
  required: lusha
  optional: crm, slack
campus_url: https://www.lusha.com/campus/plays/territory-signal-digest-skill/
category: Skills
---

# Territory Signal Digest Skill

Run a weekly signal sweep across every account in a territory.
Rank accounts by signal strength. Surface what moved since last
week. Return a brief the rep can act on before their first call.

## Input

The user will provide via $ARGUMENTS:

- Account list (required) — a list of company names, domains,
  or Lusha company IDs. Paste inline or reference a saved list.
- Lookback window (optional) — how far back to pull signals.
  Default: 7 days for weekly digest. Accept: 30 days, 90 days.
- Signal focus (optional) — which signal types to prioritize.
  Default: all. Options:
  - Role changes (promotions, job changes, departures)
  - Hiring surges (open roles in target functions)
  - Funding (rounds, investment announcements)
  - Intent (buying signals on your category)
  - News (product launches, M&A, leadership moves)

If account list is missing, ask once. If declined, return an
error — the skill cannot run without a list of accounts.

## Workflow

1. Anchor on the digest purpose.
   Read the lookback window and signal focus from $ARGUMENTS.
   Default to 7-day lookback and all signal types if not supplied.
   State the parameters at the top of the output so the reader
   knows what the digest covers.

2. Resolve accounts via Lusha.
   For each account in the list:
   - If a Lusha company ID is supplied, use it directly.
   - Otherwise resolve via companies_search using the name
     or domain.
   - Flag any accounts that could not be resolved and skip them.
     List unresolved accounts at the end of the output.

3. Pull signals in parallel.
   For each resolved account, run these calls concurrently:
   - Buying signals: intent topics, signal score 60+, ranked
     by score. Lookback window as specified.
   - News and scoops: last 7 days (or specified window).
     Leadership moves, funding, product launches, M&A, layoffs.
   - Hiring signals: open roles in target functions posted in
     the lookback window.
   - Contact changes: promotions, job changes, departures for
     key contacts at the account.

4. Score and rank accounts.
   Assign each account a signal score based on:
   - Number of signals found
   - Signal strength (intent score, recency, signal type weight)
   - Signal type weights:
     - Funding round: high
     - Executive hire or departure: high
     - Intent on your category: high
     - Hiring surge in target function: medium
     - Product launch or M&A: medium
     - General news: low

   Rank accounts from highest to lowest signal score.
   Accounts with no signals go to the bottom — list them
   briefly so the rep knows they were checked.

5. Triage signals per account.
   For each account in the ranked list, keep only the signals
   that are worth the rep's attention this week. Drop noise.
   One account should not have more than 3-5 signal bullets
   unless every signal is genuinely high value.

6. Write the digest.
   Lead with a summary line: how many accounts were checked,
   how many had signals, and the single most important signal
   across the whole territory this week.
   Then the ranked account list.

## Output Format

### Territory Signal Digest

Period: [start date] — [end date]
Accounts checked: [n]
Accounts with signals: [n]
Top signal this week: [one line — the single most important
signal across the whole territory]

---

### Ranked Account List

For each account, in signal-rank order:

**[Account Name]** — Signal score: [H / M / L]

| Signal | Type | Date | Why it matters |
|---|---|---|---|

Recommended action: [one line — what to do with this account
this week, tied to the strongest signal]

---

Repeat for every account with signals.

---

### No-Signal Accounts

Accounts checked with no signals in the lookback window:
[list of account names]

These accounts were checked — nothing moved this week.

---

### Unresolved Accounts

Accounts that could not be matched in Lusha:
[list of account names or domains]

Recommend verifying company name or domain and re-running.

---

Example outputs in this skill are illustrative — they reflect the
structure, fields, and format of real Lusha connector output, but
were not pulled from a live session. Run the skill with your own
data and connectors to see live results.
Built by: Lusha
Tools: Claude, Lusha
Type: Skill

FAQ

  • Do I need anything beyond Lusha in Claude?

    No. The skill runs entirely through the Lusha in Claude connector. Connect it once in Claude settings. Optional: connect Slack if you want the digest posted to a channel automatically after it runs.

  • How do I give it my account list?

    Paste your account list directly into the chat — company names, domains, or Lusha company IDs, one per line. If you run this weekly, the fastest setup is a Claude Project with your territory list saved as a custom instruction. The skill reads it automatically every time.

  • How is this different from the Weekly Signal Digest play?

    The Weekly Signal Digest play is a one-time prompt — run it, get a digest. This skill is installable and reusable. Save your territory list once in a Claude Project and the skill runs against it every week without re-pasting anything.

  • Can I change the lookback window?

    Yes. The default is 7 days for a weekly digest. You can set it to 30 or 90 days — useful for pre-QBR territory prep or when you’re picking up a new territory and need to catch up on what’s moved recently.

  • What if some accounts don't return any signals?

    They still appear in the digest — in a No-Signal Accounts section at the bottom. You know they were checked and nothing moved. That’s useful information too: it tells you where not to spend time this week.

Related Plays

Ready to run this?

Connect once, run anywhere. Works in Claude, ChatGPT, n8n, Clay, or any agent connected to Lusha.

Get free access Read the Docs