{"id":86245,"plugin_id":"plugin_asdk_app_69e5f69b54d8819185e1638e73c15e3b","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-09T00:08:58.675Z","digest":"b4365b82ac9ff92efe21aabc2d43342b15fe8755a53e292a24663bc43d097d73","against":null,"payload":{"description":"Tell the user which accounts to work next and why, from Lusha's recommendations ranked on their own ICP and live buying signals, then find and enrich the decision makers at the accounts they pick. Use when the user asks \"who should I go after\", \"which accounts should I prioritise\", \"what should I work on this week\", \"give me my best accounts\", \"any warm accounts for me\", \"where should I focus today\", or any targeting question that names no criteria of its own. Not when the user describes the companies or people to find (industry, size, title, location): use prospect for that.\n","included_files":[],"name":"work-my-accounts","skill_md_contents":"---\nname: work-my-accounts\ndescription: \"Tell the user which accounts to work next and why, from Lusha's recommendations ranked on their own ICP and live buying signals, then find and enrich the decision makers at the accounts they pick. Use when the user asks \\\"who should I go after\\\", \\\"which accounts should I prioritise\\\", \\\"what should I work on this week\\\", \\\"give me my best accounts\\\", \\\"any warm accounts for me\\\", \\\"where should I focus today\\\", or any targeting question that names no criteria of its own. Not when the user describes the companies or people to find (industry, size, title, location): use prospect for that.\\n\"\n---\n\n# Work My Accounts\n\nAnswer \"who should I go after?\" with ten accounts, a reason for each, and a call list for the ones the user picks. Lusha's recommendations are personalised to the user's Target Profiles and ranked by lead score (ICP fit plus live buying signals), so the user does not have to describe a market.\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 `work-my-accounts: `.\n2. Run the calls that use no quota first and branch on what they return. A missing profile gets a setup offer, never an error.\n3. Before every quota-using call, state how much of the quota already included in the user's existing Lusha account it will use, and wait for a yes. This workflow cannot change the user's account entitlement. Get the quota rate for every quota-using call from `account_usage` (uses no quota; call it once per session). Each `pricing` entry (the per-action quota rates) names the tools it applies to. If a tool has no entry, say its rate isn't listed for this plan, and report the quota the call actually used from the usage metadata afterwards. Preview 10 before a full page. Reveal only the people the user picks. 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.\n4. Zero results is not the end: say what was searched, then offer to widen.\n5. Keep the chain short: every call counts toward the user's AI usage.\n6. 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 — Recommend 10 accounts\n\nSay: *\"I'll pull your top 10 recommended accounts. That uses N of the quota already included in your existing Lusha account.\"* Work out N from the `recommendations_companies` rate in `account_usage`: the rate is per account returned, times 10. Then call `recommendations_companies` with `pagination: { size: 10 }` and no filters. Results come back sorted by lead score, which is right for this question.\n\nChange the call only when the user asked for something specific:\n- **\"Who's hot right now\"** → `sort: [{ by: \"signalScore\" }]`.\n- **A named segment or one of their profiles** → get the ids from `recommendations_companies_filters` (uses no quota) and pass `filters.targetIcp`.\n- **A named signal** (hiring, funding) → get the ids from the same filters call and pass `filters.signals`.\n\nNever construct a profile or signal id.\n\n- **Account-wide API key (403):** recommendations need a personal login. Say so, and offer `prospect` instead.\n- **No results:** say the recommendations came back empty for this profile, and offer `prospect` with the user's own criteria.\n\n## Step 2 — Say why each account is listed\n\n| # | Company | Domain | Lead score | ICP fit | Signal score | Why it's here |\n|---|---------|--------|-----------|---------|--------------|---------------|\n\n\"Why it's here\" is one line built from the record: the target profile it matched, plus the signals that fired, e.g. *\"Matches 'Mid-market fintech'; hiring surge in Sales, headcount +12% in 6 months.\"* Never write a reason the record does not support.\n\n**No profile of their own:** if the matched profile is the *Lusha Calculated Target Profile*, or the response carries a `target_profile_suggestion`, tell the user: *\"These are based on a profile Lusha calculated for you. Setting up your own ICP makes them sharper. Want to do that next with set-up-my-icp?\"* Show the suggestion's `message` if there is one.\n\nAsk which accounts to work: *\"Which of these should I find people at? Pick by number, or say 'top 3'.\"* Offer the next 10 (`page: 1`, quota estimated the same way) if none fit.\n\n## Step 3 — Find the people at the picked accounts\n\n**The user named a role** (e.g. \"VP Sales\"): call `prospecting_contact_search` with `companyIds` set to the picked accounts' ids, `jobTitles` set to the role, and `page_size: 10`.\n\n**No role named:** find the decision makers. It uses existing-account quota per contact returned, for at most 3 contacts per account; state that quota usage first. Then call `decision_makers_buying_group_search` with:\n- `companies`: the picked accounts by `domain` or `id`, up to 25 per call\n- `personas: [\"decision_maker\"]`\n- `contactsLimit: 3`\n- `pagination: { size: 100 }`, so all 75 possible contacts fit on one page\n\nAn account that comes back empty or `NOT_FOUND` uses no quota.\n- **The call errors:** fall back to contact search for every picked account.\n- **Some accounts come back with no contacts:** fall back for those accounts only, and say which ones. Never drop an account silently.\n\nThe fallback is `prospecting_contact_search` with `companyIds` set to those accounts and senior decision makers. Resolve the senior levels to `seniority` ids with `prospecting_contact_filters` (`seniority`).\n\nShow the people found, without phones or emails yet:\n\n| # | Name | Title | Company | Role in deal | Can reveal |\n|---|------|-------|---------|--------------|-----------|\n\n## Step 4 — Enrich only the people the user picks\n\nAsk who to reveal. Sum `canReveal[].credits` for the fields being revealed, state the total as existing-account quota, and wait for a yes. Then call `prospecting_contact_enrich` with those ids and `reveal` taken from `canReveal[].field`, up to 50 per call.\n\n**What a reveal returns.**\n- **Third-party sources.** `canReveal[].credits` is the Lusha 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 usage. 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 the response means some reveals, usually from third-party sources, are still running.\n1. Show what has landed and how many are still running (`job.outstandingCount`).\n2. Wait `pollAgainInSeconds`, then check `contacts_enrich_job_status` until `isTerminal` is true.\n3. Read the final contacts with `contacts_enrich_job_results` (`contactLimit: 25`, following `contactPage.nextContactOffset` while `hasMore`).\n4. Never enrich the same ids again: that uses quota twice. The job tools use no quota.\n\n## Step 5 — Present the call list\n\n| # | Name | Title | Company | Direct Phone | Mobile | Email | Why this account |\n|---|------|-------|---------|-------------|--------|-------|------------------|\n\n- Phones come first. Mark a missing phone with `—`.\n- Carry the Step 2 reason onto each row, so the user has an opener.\n\n### Summary\n- Accounts recommended: 10 (picked: N)\n- People found: X; enriched: Y; with a phone: Z\n- Existing-account quota used: sum of the usage metadata\n\n## Step 6 — Next actions\n\n1. **Save the call list to a Workspace table** — hand off to `save-or-export` (contacts tables use no quota).\n2. **Export to the CRM** — through `save-or-export`.\n3. **Score a list of your own the same way** — `score-my-list`.\n4. **Using the calculated profile?** Run `set-up-my-icp` to make recommendations your own.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}