← LushaCONTENT HISTORY

Update to Lusha

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

Collection source: downloaded plugin package.

WHAT CHANGED

First saved snapshot

No earlier snapshot is available to establish a change.

Save Lusha and check future changes in Following.

Up to 3 plugins free · no card required.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "description": "Set up the user's Ideal Customer Profile (an ICP Target Profile in Lusha) by asking the profile questions one at a time, drafting each answer from what is already known about their company and customers, then creating the profile and previewing 10 matching accounts. Use when the user says \"set up my ICP\", \"define my ideal customer\", \"who's my ideal customer\", \"create a target profile\", \"teach Lusha who my customers are\", \"my recommendations are off\", or when another Lusha skill sends them here because no profile exists. Not for a one-off search by criteria: use prospect.\n",
  "included_files": [],
  "name": "set-up-my-icp",
  "skill_md_contents": "---\nname: set-up-my-icp\ndescription: \"Set up the user's Ideal Customer Profile (an ICP Target Profile in Lusha) by asking the profile questions one at a time, drafting each answer from what is already known about their company and customers, then creating the profile and previewing 10 matching accounts. Use when the user says \\\"set up my ICP\\\", \\\"define my ideal customer\\\", \\\"who's my ideal customer\\\", \\\"create a target profile\\\", \\\"teach Lusha who my customers are\\\", \\\"my recommendations are off\\\", or when another Lusha skill sends them here because no profile exists. Not for a one-off search by criteria: use prospect.\\n\"\n---\n\n# Set Up My ICP\n\nA Target Profile tells Lusha who the user's customers are: the companies (account criteria) and the people inside them (personas). Once it is active, recommendations, ICP fit scores and `score-my-list` all use it. This skill builds one with the user, one question at a time, and never asks a question it can answer with a draft.\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 `set-up-my-icp: `. When another skill sent the user here, keep that skill's name as the prefix.\n2. Every profile tool uses no quota. The only quota-using calls here are the optional reads in Step 2 and the preview in Step 5; state how much of the quota already included in the user's existing Lusha account they will use first. This workflow cannot change the user's account entitlement.\n3. Use only the criterion keys and values `icp_filters_get` returns. Anything else is refused.\n\n## Step 1 — Load what exists (uses no quota)\n\nCall `icp_profiles_get` and `icp_filters_get` together.\n\n- **The ICP tools are missing from this session:** the account's plan doesn't include Target Profiles through this connection. Tell the user that profiles are set up in ICP Hub in the Lusha platform, and stop.\n- **The user already has profiles:** list them (name, active or disabled). Ask whether to add a new one or change an existing one. Changes go through `icp_profile_update`. Updating a set of personas or the account criteria replaces that set in full, so show the full new set before saving. To pause or reactivate a profile, use `icp_profile_status_set`.\n- **Limits** (in `icp_filters_get`): 10 profiles per user, 4 personas per profile. Near a limit, say so before starting.\n\n`icp_filters_get` returns `profile_questions`: the order to settle a profile in. Follow it:\n1. Account criteria\n2. Each persona\n3. Intent topics\n4. Lusha-based exclusions\n\n## Step 2 — Gather material for drafts\n\nA good draft is what makes this fast: the user confirms or edits instead of starting from blank. Draft from, in order:\n\n1. **What the user already said** in this conversation: product, customers, market.\n2. **Their own company.** Use the `account_domain` from a `target_profile_suggestion` if a previous response carried one, or ask for their website. Look it up with `companies_search` (`enrich: false`, uses existing-account quota per successful lookup; say so first) for industry, size and location. The user's own company is a hint, not the answer: their customers may be in a different market or size than their own.\n3. **Customers they name, or a saved list.** If the user mentions a list of customers or wins, find Workspace tables with `table_list` (uses no quota, by name). Reading rows with `table_get_entities` uses existing-account quota per block of rows (`tableRead` in `account_usage`), so state the quota usage and ask before reading. A sample of 25 is enough to see the common industries and sizes.\n\nSkip any source the user doesn't want used.\n\n## Step 3 — Ask one question at a time\n\nFollow `profile_questions`. For each criterion:\n- Show the draft as concrete values from `icp_filters_get`.\n- Say in one line where the draft came from.\n- Ask the user to confirm, edit, or skip.\n\nFor example: *\"Industries — from your customers I'd target Financial Services and Software Development. Keep, change, or skip?\"*\n\n- **Criteria with a lookup path** (not listed inline): search the values with the user's term, as `icp_filters_get` describes, and offer the matches.\n- **A criterion the user skips is not targeted.** That makes the profile broader, which is fine. Say so once rather than pushing for every field.\n- **Personas:** start with the buyer (titles or seniority, plus department), then ask *\"Anyone else on the deal — a champion or user?\"* Stop at 4.\n- **Intent topics:** offer only the topics the account already has, as listed in `icp_filters_get`. If there are none, skip the question.\n- **Exclusions:** offer the common one — leave out companies whose contacts were already shown to the user (`companies_of_shown_contacts`, `by_me`). Then move on.\n\n## Step 4 — Confirm and create\n\nShow the whole profile:\n\n| Part | Criterion | Values |\n|------|-----------|--------|\n\nThen confirm before creating: *\"Creating this profile makes it active, which changes the recommendations you get from now on. It will be private to you. Create it?\"*\n\nThen call `icp_profile_create`:\n- `account_criteria`, `personas`, `intent_topics`, `lusha_exclusions` as settled.\n- A short `name`, or omit it and Lusha names it from the criteria.\n- `access: \"private\"` unless the user asks to share it. Sharing is admin-only and changes recommendations for everyone on the account.\n\nIf a value is refused, the error names the valid options. Re-offer those and retry once.\n\n## Step 5 — Show it working\n\nGive the profile name and its platform link from the response. Then offer: *\"Want to see the top 10 accounts it finds? That uses N of the quota already included in your existing Lusha account.\"* N is the `recommendations_companies` rate in `account_usage`, times 10.\n\nOn yes, call `recommendations_companies` with `filters.targetIcp` set to the new profile id and `pagination: { size: 10 }`. If the new id isn't listed yet, get it from `recommendations_companies_filters` (uses no quota).\n\n| # | Company | Domain | ICP fit | Signal score | Signals |\n|---|---------|--------|---------|--------------|---------|\n\nIf the preview looks wrong to the user, change the profile with `icp_profile_update` and preview again.\n\n## Step 6 — Next actions\n\n1. **Work these accounts** — `work-my-accounts` finds the decision makers and builds the call list.\n2. **Score a list you already have against this profile** — `score-my-list`.\n3. **Save the 10 accounts to a Workspace table, or export them to the CRM** — through `save-or-export`.\n"
}

SHA-256 of public snapshot: d6ab2e72a4d8234c9525901c4540484907609d5ba7af9a6325abc9cb4655cd11