← LushaCONTENT HISTORY

Update to Lusha

Snapshot Nov 9, 2026 · 00:08 UTC · version 3.1.0

Collection source: downloaded plugin package.

WHAT CHANGED

Instructions updated for prospect

Skill instructions — Now says: ## Lusha call rules 1. Pass `conversation_id` from the most recent Lusha response on every call. Start every `reason_for_invocation` with `prospect: ` (or...

Observed in instructions or declared skills. Runtime behavior has not been tested.

Save Lusha and check future changes in Following.

Up to 3 plugins free · no card required.

All fields and original values.

Skill instructions

Before

Oct 25, 2026 · 12:04 UTC

Before enriching, sum the `canReveal[].credits` for the fields you'll reveal, describe this as quota already included in the user's existing Lusha account, and wait for confirmation on large batches. This workflow cannot change the user'...

After

Nov 9, 2026 · 00:08 UTC

## Lusha call rules 1. Pass `conversation_id` from the most recent Lusha response on every call. Start every `reason_for_invocation` with `prospect: ` (or with the calling skill's name, when another skill delegated here). 2. State how mu...

Compare saved observations

Download comparison JSON

SKILL.md text changes

− removed · + added

--- before
+++ after
@@ -7,6 +7,13 @@
 
 Go from an ICP description to a ranked, phone-enriched lead list. Filters are resolved before search — never guess filter values.
 
+## Lusha call rules
+
+1. Pass `conversation_id` from the most recent Lusha response on every call. Start every `reason_for_invocation` with `prospect: ` (or with the calling skill's name, when another skill delegated here).
+2. State how much of the quota already included in the user's existing Lusha account each reveal uses, and wait for a yes on large batches. This workflow cannot change the user's account entitlement. On a 402: if the existing entitlement is insufficient, say so and offer to continue with previews or a smaller batch. Never suggest changing the user's account entitlement.
+3. Keep the chain short: every call counts toward the user's AI usage.
+4. If a response carries `next_step_hints` and the user picks one of its offers, pass its `ref` as `next_step_ref`.
+
 ## Step 1 — Parse the ICP
 
 Extract structured filters from the user's natural language description. Some filters take free-form text directly; others must be resolved to canonical values first.
@@ -40,13 +47,26 @@
 
 Use `prospecting_contact_search` with resolved contact filters. Scope to the company results from Step 2 where applicable. Request up to 25 results.
 
+**No results?** Don't stop. Say exactly what was searched, then offer the widening that fits, most useful first:
+1. An exact title (e.g. "CTO") → the department plus seniority (`departments` + `seniority` ids).
+2. The narrowest company filter (size, location or industry) → drop it.
+3. A location → its country or region.
+
 ## Step 4 — Enrich Top Results
 
 Search results are previews — they carry no phones/emails but include a `canReveal[]` list per contact showing which fields can be revealed and the existing-account quota required in `canReveal[].credits`.
 
 Use `prospecting_contact_enrich` with the contact `id`s to reveal phones and email. Pass `reveal` set from the results' `canReveal[].field` to control exactly which fields use the user's existing-account quota. Up to **50** contacts per call — split larger sets across calls.
 
-Before enriching, sum the `canReveal[].credits` for the fields you'll reveal, describe this as quota already included in the user's existing Lusha account, and wait for confirmation on large batches. This workflow cannot change the user's account entitlement. If the existing entitlement is insufficient, offer to continue with previews or a smaller batch.
+Before enriching, sum the `canReveal[].credits` for the fields you'll reveal, describe this as quota already included in the user's existing Lusha account, and wait for confirmation on large batches. This workflow cannot change the user's account entitlement. Use `account_usage` first if the user wants to check how much existing-account quota remains. If the existing entitlement is insufficient, offer to continue with previews or a smaller batch.
+
+**What a reveal returns.**
+- **Third-party quota rates.** `canReveal[].credits` is Lusha's own quota rate. If the account has the data waterfall on, a Lusha miss can be filled by a third-party source at its own quota rate (`account_usage` lists them, e.g. a phone at 8 of the existing-account quota). Say so when stating the quota used. Offer `waterfallEnabled: false` for a Lusha-only reveal.
+- **`COMPLIANCE_RESTRICTED`** on a row means that contact can't be shown, for compliance reasons, and no quota was used. Say so and offer the next person.
+- **`doNotCall: true`** marks a phone that is masked and not to be called. Show it as "Do not call", never as a number to dial.
+- **A different company.** If the enrich result shows a different company from the search, the person has changed jobs. Show the new company and say so.
+
+**Background reveals.** A `job` block in an enrich response means some reveals (usually from third-party sources) are still running. Show what has landed and how many are still running (`job.outstandingCount`). Then check `contacts_enrich_job_status` after `pollAgainInSeconds` until `isTerminal` is true, and read the final contacts with `contacts_enrich_job_results` (`contactLimit: 25`, following `contactPage.nextContactOffset` while `hasMore`). Never enrich the same ids again: that may use the existing-account quota twice. The job tools use no quota. Larger sets still go in calls of 50; each call may carry its own job.
 
 ## Step 5 — Present the Lead List
 
@@ -77,4 +97,7 @@
 2. **Add intent filter** — narrow to companies actively researching a topic
 3. **Add tech stack filter** — narrow to companies using a specific technology
 4. **Run signal-prospect** — cross this list against current buying signals
-5. **Export** — format as CSV for copy-paste
\ No newline at end of file
+5. **Score the list** — rank these companies by ICP fit and buying signals into A/B/C tiers with `score-my-list`
+6. **Save to a Workspace table** — hand the contact ids to `save-or-export` (contacts tables use no quota)
+7. **Export to CRM** — through `save-or-export`, which checks the CRM connection first and offers to connect one if there is none
+8. **Export** — format as CSV for copy-paste
Full technical diff · 1 changed fields

changed /skill_md_contents

BEFORE
"---\nname: prospect\ndescription: \"Build a targeted list of contacts or companies from Lusha and return verified phone numbers alongside emails. Use when the user says \\\"find me [title] at [company type]\\\", \\\"build a list of [ICP description]\\\", \\\"prospect [criteria]\\\", \\\"who should I be calling at [industry]\\\", or any request to generate a lead list from an ICP or persona description.\\n\"\n---\n\n# Prospect\n\nGo from an ICP description to a ranked, phone-enriched lead list. Filters are resolved before search — never guess filter values.\n\n## Step 1 — Parse the ICP\n\nExtract structured filters from the user's natural language description. Some filters take free-form text directly; others must be resolved to canonical values first.\n\n**Contact filters (`prospecting_contact_search`):**\n- Job titles → pass directly as `jobTitles` (free-form strings, e.g. \"VP of Sales\"). No resolution call needed.\n- Department / seniority → resolve via `prospecting_contact_filters` (type: `departments`, `seniority`). Use these for broad role targeting when a specific title isn't given.\n- Country → resolve via `prospecting_contact_filters` (type: `all_countries`); Location → type: `locations` (requires `locationSearchText`).\n\n**Company filters (`prospecting_company_search`):**\n- Industry → resolve via `prospecting_company_filters` (type: `industries_labels`)\n- Size → resolve via `prospecting_company_filters` (type: `sizes`)\n- Revenue → resolve via `prospecting_company_filters` (type: `revenues`)\n- Location → resolve via `prospecting_company_filters` (type: `locations`, requires `q`)\n- Tech stack → resolve via `prospecting_company_filters` (type: `technologies`, requires `q`)\n- Buying intent → resolve via `prospecting_company_filters` (type: `intent_topics`)\n\nResolve every non-title filter to canonical values before searching — passing raw natural-language strings as structured filter values is the most common cause of search failures. Each `prospecting_*_filters` call resolves one filter type; run the independent lookups in parallel.\n\nIf the ICP is too vague to resolve (no title, no industry, no company size), ask one clarifying question before proceeding. At minimum, a title or department and at least one company-level constraint are required.\n\nSee `references/filter-guide.md` for filter resolution details.\n\n## Step 2 — Search Companies\n\nUse `prospecting_company_search` with resolved company filters. Request up to 25 results. This scopes the contact search to qualified accounts.\n\nIf the user only specified contact-level criteria (no company filters), skip this step and go directly to Step 3.\n\n## Step 3 — Search Contacts\n\nUse `prospecting_contact_search` with resolved contact filters. Scope to the company results from Step 2 where applicable. Request up to 25 results.\n\n## Step 4 — Enrich Top Results\n\nSearch results are previews — they carry no phones/emails but include a `canReveal[]` list per contact showing which fields can be revealed and the existing-account quota required in `canReveal[].credits`.\n\nUse `prospecting_contact_enrich` with the contact `id`s to reveal phones and email. Pass `reveal` set from the results' `canReveal[].field` to control exactly which fields use the user's existing-account quota. Up to **50** contacts per call — split larger sets across calls.\n\nBefore enriching, sum the `canReveal[].credits` for the fields you'll reveal, describe this as quota already included in the user's existing Lusha account, and wait for confirmation on large batches. This workflow cannot change the user's account entitlement. If the existing entitlement is insufficient, offer to continue with previews or a smaller batch.\n\n## Step 5 — Present the Lead List\n\n### Filters Applied\nShow the user exactly what was used so they can verify:\n\n| Filter | Value |\n|--------|-------|\n| ... | ... |\n\n### Lead List\n\n| # | Name | Title | Company | Industry | Size | Direct Phone | Mobile | Email | Intent Signal |\n|---|------|-------|---------|----------|------|-------------|--------|-------|---------------|\n\n- Surface direct phone and mobile as separate columns — do not merge or hide them\n- Mark missing phone numbers with `—` not blank cells\n- Include intent signal column only if `intent_topics` filter was used\n\n### Summary\n- Results found: X (showing top Y)\n- Contacts with verified phone: Z\n- Existing-account quota used: N\n\n## Step 6 — Offer Next Actions\n\n1. **Refine** — adjust filters and re-run\n2. **Add intent filter** — narrow to companies actively researching a topic\n3. **Add tech stack filter** — narrow to companies using a specific technology\n4. **Run signal-prospect** — cross this list against current buying signals\n5. **Export** — format as CSV for copy-paste"
AFTER
"---\nname: prospect\ndescription: \"Build a targeted list of contacts or companies from Lusha and return verified phone numbers alongside emails. Use when the user says \\\"find me [title] at [company type]\\\", \\\"build a list of [ICP description]\\\", \\\"prospect [criteria]\\\", \\\"who should I be calling at [industry]\\\", or any request to generate a lead list from an ICP or persona description.\\n\"\n---\n\n# Prospect\n\nGo from an ICP description to a ranked, phone-enriched lead list. Filters are resolved before search — never guess filter values.\n\n## Lusha call rules\n\n1. Pass `conversation_id` from the most recent Lusha response on every call. Start every `reason_for_invocation` with `prospect: ` (or with the calling skill's name, when another skill delegated here).\n2. State how much of the quota already included in the user's existing Lusha account each reveal uses, and wait for a yes on large batches. This workflow cannot change the user's account entitlement. On a 402: if the existing entitlement is insufficient, say so and offer to continue with previews or a smaller batch. Never suggest changing the user's account entitlement.\n3. Keep the chain short: every call counts toward the user's AI usage.\n4. If a response carries `next_step_hints` and the user picks one of its offers, pass its `ref` as `next_step_ref`.\n\n## Step 1 — Parse the ICP\n\nExtract structured filters from the user's natural language description. Some filters take free-form text directly; others must be resolved to canonical values first.\n\n**Contact filters (`prospecting_contact_search`):**\n- Job titles → pass directly as `jobTitles` (free-form strings, e.g. \"VP of Sales\"). No resolution call needed.\n- Department / seniority → resolve via `prospecting_contact_filters` (type: `departments`, `seniority`). Use these for broad role targeting when a specific title isn't given.\n- Country → resolve via `prospecting_contact_filters` (type: `all_countries`); Location → type: `locations` (requires `locationSearchText`).\n\n**Company filters (`prospecting_company_search`):**\n- Industry → resolve via `prospecting_company_filters` (type: `industries_labels`)\n- Size → resolve via `prospecting_company_filters` (type: `sizes`)\n- Revenue → resolve via `prospecting_company_filters` (type: `revenues`)\n- Location → resolve via `prospecting_company_filters` (type: `locations`, requires `q`)\n- Tech stack → resolve via `prospecting_company_filters` (type: `technologies`, requires `q`)\n- Buying intent → resolve via `prospecting_company_filters` (type: `intent_topics`)\n\nResolve every non-title filter to canonical values before searching — passing raw natural-language strings as structured filter values is the most common cause of search failures. Each `prospecting_*_filters` call resolves one filter type; run the independent lookups in parallel.\n\nIf the ICP is too vague to resolve (no title, no industry, no company size), ask one clarifying question before proceeding. At minimum, a title or department and at least one company-level constraint are required.\n\nSee `references/filter-guide.md` for filter resolution details.\n\n## Step 2 — Search Companies\n\nUse `prospecting_company_search` with resolved company filters. Request up to 25 results. This scopes the contact search to qualified accounts.\n\nIf the user only specified contact-level criteria (no company filters), skip this step and go directly to Step 3.\n\n## Step 3 — Search Contacts\n\nUse `prospecting_contact_search` with resolved contact filters. Scope to the company results from Step 2 where applicable. Request up to 25 results.\n\n**No results?** Don't stop. Say exactly what was searched, then offer the widening that fits, most useful first:\n1. An exact title (e.g. \"CTO\") → the department plus seniority (`departments` + `seniority` ids).\n2. The narrowest company filter (size, location or industry) → drop it.\n3. A location → its country or region.\n\n## Step 4 — Enrich Top Results\n\nSearch results are previews — they carry no phones/emails but include a `canReveal[]` list per contact showing which fields can be revealed and the existing-account quota required in `canReveal[].credits`.\n\nUse `prospecting_contact_enrich` with the contact `id`s to reveal phones and email. Pass `reveal` set from the results' `canReveal[].field` to control exactly which fields use the user's existing-account quota. Up to **50** contacts per call — split larger sets across calls.\n\nBefore enriching, sum the `canReveal[].credits` for the fields you'll reveal, describe this as quota already included in the user's existing Lusha account, and wait for confirmation on large batches. This workflow cannot change the user's account entitlement. Use `account_usage` first if the user wants to check how much existing-account quota remains. If the existing entitlement is insufficient, offer to continue with previews or a smaller batch.\n\n**What a reveal returns.**\n- **Third-party quota rates.** `canReveal[].credits` is Lusha's own quota rate. If the account has the data waterfall on, a Lusha miss can be filled by a third-party source at its own quota rate (`account_usage` lists them, e.g. a phone at 8 of the existing-account quota). Say so when stating the quota used. Offer `waterfallEnabled: false` for a Lusha-only reveal.\n- **`COMPLIANCE_RESTRICTED`** on a row means that contact can't be shown, for compliance reasons, and no quota was used. Say so and offer the next person.\n- **`doNotCall: true`** marks a phone that is masked and not to be called. Show it as \"Do not call\", never as a number to dial.\n- **A different company.** If the enrich result shows a different company from the search, the person has changed jobs. Show the new company and say so.\n\n**Background reveals.** A `job` block in an enrich response means some reveals (usually from third-party sources) are still running. Show what has landed and how many are still running (`job.outstandingCount`). Then check `contacts_enrich_job_status` after `pollAgainInSeconds` until `isTerminal` is true, and read the final contacts with `contacts_enrich_job_results` (`contactLimit: 25`, following `contactPage.nextContactOffset` while `hasMore`). Never enrich the same ids again: that may use the existing-account quota twice. The job tools use no quota. Larger sets still go in calls of 50; each call may carry its own job.\n\n## Step 5 — Present the Lead List\n\n### Filters Applied\nShow the user exactly what was used so they can verify:\n\n| Filter | Value |\n|--------|-------|\n| ... | ... |\n\n### Lead List\n\n| # | Name | Title | Company | Industry | Size | Direct Phone | Mobile | Email | Intent Signal |\n|---|------|-------|---------|----------|------|-------------|--------|-------|---------------|\n\n- Surface direct phone and mobile as separate columns — do not merge or hide them\n- Mark missing phone numbers with `—` not blank cells\n- Include intent signal column only if `intent_topics` filter was used\n\n### Summary\n- Results found: X (showing top Y)\n- Contacts with verified phone: Z\n- Existing-account quota used: N\n\n## Step 6 — Offer Next Actions\n\n1. **Refine** — adjust filters and re-run\n2. **Add intent filter** — narrow to companies actively researching a topic\n3. **Add tech stack filter** — narrow to companies using a specific technology\n4. **Run signal-prospect** — cross this list against current buying signals\n5. **Score the list** — rank these companies by ICP fit and buying signals into A/B/C tiers with `score-my-list`\n6. **Save to a Workspace table** — hand the contact ids to `save-or-export` (contacts tables use no quota)\n7. **Export to CRM** — through `save-or-export`, which checks the CRM connection first and offers to connect one if there is none\n8. **Export** — format as CSV for copy-paste\n"
Full snapshot data
{
  "description": "Build a targeted list of contacts or companies from Lusha and return verified phone numbers alongside emails. Use when the user says \"find me [title] at [company type]\", \"build a list of [ICP description]\", \"prospect [criteria]\", \"who should I be calling at [industry]\", or any request to generate a lead list from an ICP or persona description.\n",
  "included_files": [
    {
      "relative_path": "references/filter-guide.md",
      "size_in_bytes": 2395
    }
  ],
  "name": "prospect",
  "skill_md_contents": "---\nname: prospect\ndescription: \"Build a targeted list of contacts or companies from Lusha and return verified phone numbers alongside emails. Use when the user says \\\"find me [title] at [company type]\\\", \\\"build a list of [ICP description]\\\", \\\"prospect [criteria]\\\", \\\"who should I be calling at [industry]\\\", or any request to generate a lead list from an ICP or persona description.\\n\"\n---\n\n# Prospect\n\nGo from an ICP description to a ranked, phone-enriched lead list. Filters are resolved before search — never guess filter values.\n\n## Lusha call rules\n\n1. Pass `conversation_id` from the most recent Lusha response on every call. Start every `reason_for_invocation` with `prospect: ` (or with the calling skill's name, when another skill delegated here).\n2. State how much of the quota already included in the user's existing Lusha account each reveal uses, and wait for a yes on large batches. This workflow cannot change the user's account entitlement. On a 402: if the existing entitlement is insufficient, say so and offer to continue with previews or a smaller batch. Never suggest changing the user's account entitlement.\n3. Keep the chain short: every call counts toward the user's AI usage.\n4. If a response carries `next_step_hints` and the user picks one of its offers, pass its `ref` as `next_step_ref`.\n\n## Step 1 — Parse the ICP\n\nExtract structured filters from the user's natural language description. Some filters take free-form text directly; others must be resolved to canonical values first.\n\n**Contact filters (`prospecting_contact_search`):**\n- Job titles → pass directly as `jobTitles` (free-form strings, e.g. \"VP of Sales\"). No resolution call needed.\n- Department / seniority → resolve via `prospecting_contact_filters` (type: `departments`, `seniority`). Use these for broad role targeting when a specific title isn't given.\n- Country → resolve via `prospecting_contact_filters` (type: `all_countries`); Location → type: `locations` (requires `locationSearchText`).\n\n**Company filters (`prospecting_company_search`):**\n- Industry → resolve via `prospecting_company_filters` (type: `industries_labels`)\n- Size → resolve via `prospecting_company_filters` (type: `sizes`)\n- Revenue → resolve via `prospecting_company_filters` (type: `revenues`)\n- Location → resolve via `prospecting_company_filters` (type: `locations`, requires `q`)\n- Tech stack → resolve via `prospecting_company_filters` (type: `technologies`, requires `q`)\n- Buying intent → resolve via `prospecting_company_filters` (type: `intent_topics`)\n\nResolve every non-title filter to canonical values before searching — passing raw natural-language strings as structured filter values is the most common cause of search failures. Each `prospecting_*_filters` call resolves one filter type; run the independent lookups in parallel.\n\nIf the ICP is too vague to resolve (no title, no industry, no company size), ask one clarifying question before proceeding. At minimum, a title or department and at least one company-level constraint are required.\n\nSee `references/filter-guide.md` for filter resolution details.\n\n## Step 2 — Search Companies\n\nUse `prospecting_company_search` with resolved company filters. Request up to 25 results. This scopes the contact search to qualified accounts.\n\nIf the user only specified contact-level criteria (no company filters), skip this step and go directly to Step 3.\n\n## Step 3 — Search Contacts\n\nUse `prospecting_contact_search` with resolved contact filters. Scope to the company results from Step 2 where applicable. Request up to 25 results.\n\n**No results?** Don't stop. Say exactly what was searched, then offer the widening that fits, most useful first:\n1. An exact title (e.g. \"CTO\") → the department plus seniority (`departments` + `seniority` ids).\n2. The narrowest company filter (size, location or industry) → drop it.\n3. A location → its country or region.\n\n## Step 4 — Enrich Top Results\n\nSearch results are previews — they carry no phones/emails but include a `canReveal[]` list per contact showing which fields can be revealed and the existing-account quota required in `canReveal[].credits`.\n\nUse `prospecting_contact_enrich` with the contact `id`s to reveal phones and email. Pass `reveal` set from the results' `canReveal[].field` to control exactly which fields use the user's existing-account quota. Up to **50** contacts per call — split larger sets across calls.\n\nBefore enriching, sum the `canReveal[].credits` for the fields you'll reveal, describe this as quota already included in the user's existing Lusha account, and wait for confirmation on large batches. This workflow cannot change the user's account entitlement. Use `account_usage` first if the user wants to check how much existing-account quota remains. If the existing entitlement is insufficient, offer to continue with previews or a smaller batch.\n\n**What a reveal returns.**\n- **Third-party quota rates.** `canReveal[].credits` is Lusha's own quota rate. If the account has the data waterfall on, a Lusha miss can be filled by a third-party source at its own quota rate (`account_usage` lists them, e.g. a phone at 8 of the existing-account quota). Say so when stating the quota used. Offer `waterfallEnabled: false` for a Lusha-only reveal.\n- **`COMPLIANCE_RESTRICTED`** on a row means that contact can't be shown, for compliance reasons, and no quota was used. Say so and offer the next person.\n- **`doNotCall: true`** marks a phone that is masked and not to be called. Show it as \"Do not call\", never as a number to dial.\n- **A different company.** If the enrich result shows a different company from the search, the person has changed jobs. Show the new company and say so.\n\n**Background reveals.** A `job` block in an enrich response means some reveals (usually from third-party sources) are still running. Show what has landed and how many are still running (`job.outstandingCount`). Then check `contacts_enrich_job_status` after `pollAgainInSeconds` until `isTerminal` is true, and read the final contacts with `contacts_enrich_job_results` (`contactLimit: 25`, following `contactPage.nextContactOffset` while `hasMore`). Never enrich the same ids again: that may use the existing-account quota twice. The job tools use no quota. Larger sets still go in calls of 50; each call may carry its own job.\n\n## Step 5 — Present the Lead List\n\n### Filters Applied\nShow the user exactly what was used so they can verify:\n\n| Filter | Value |\n|--------|-------|\n| ... | ... |\n\n### Lead List\n\n| # | Name | Title | Company | Industry | Size | Direct Phone | Mobile | Email | Intent Signal |\n|---|------|-------|---------|----------|------|-------------|--------|-------|---------------|\n\n- Surface direct phone and mobile as separate columns — do not merge or hide them\n- Mark missing phone numbers with `—` not blank cells\n- Include intent signal column only if `intent_topics` filter was used\n\n### Summary\n- Results found: X (showing top Y)\n- Contacts with verified phone: Z\n- Existing-account quota used: N\n\n## Step 6 — Offer Next Actions\n\n1. **Refine** — adjust filters and re-run\n2. **Add intent filter** — narrow to companies actively researching a topic\n3. **Add tech stack filter** — narrow to companies using a specific technology\n4. **Run signal-prospect** — cross this list against current buying signals\n5. **Score the list** — rank these companies by ICP fit and buying signals into A/B/C tiers with `score-my-list`\n6. **Save to a Workspace table** — hand the contact ids to `save-or-export` (contacts tables use no quota)\n7. **Export to CRM** — through `save-or-export`, which checks the CRM connection first and offers to connect one if there is none\n8. **Export** — format as CSV for copy-paste\n"
}

SHA-256 of public snapshot: 846fcdf31e9f696d23397a9ecf56558069940c9e7b2d3cc3bb12a2e8531388bb