@sellable/mcp 0.1.232 → 0.1.233

package/dist/tools/leads.js

@@ -522,6 +522,7 @@ search_prospeo_companies({
   }
 })
 Do not invent company_oids. When seedCompanies or seedDomains are present, omit company_oids and let the backend resolve real Prospeo company IDs.
+For customer, best-customer, top-customer, or past-company lookalikes, never substitute the sender's current company or domain as a lookalike seed and never use the sender's current company/domain as a silent substitute. Use explicit customer/account/company/domain input first, then verified customer/worked-with/past-company evidence from research/proof, then ask for the missing seed or switch to non-lookalike company filters if YOLO requires moving without a seed. Label profile/work-history seeds as past-company/public proof clues, not confirmed customers unless the source proves customer status. If the user asks for a geography like Germany, preserve it in company discovery where supported and in the follow-on people search.
 After account approval, copy the companySearchToken exactly into confirm_prospeo_company_accounts; package-backed MCP may return a short mcp-prospeo-company-search-token:* reference to avoid long-token copy errors.
 For accounts in the news: { "company_news": { "categories": ["Funding & Investment"], "timeframe_days": 90 } }.
 For awards: { "company_awards": { "include": ["G2"], "match_mode": "CONTAINS" } }.
@@ -1498,6 +1499,7 @@ export const leadToolDefinitions = [
     {
         name: "search_prospeo_companies",
         description: 'Search Prospeo for company/account results through the public /search-company lane. Requires get_provider_prompt({ provider: "prospeo" }) first. Use this first for company lookalike/account asks such as "find companies like Red Rover that use AI and have an API", "find founders at companies like our best customers", or "find accounts in the news about funding or partnerships". Results are accounts, not finished people leads. Review the returned accounts with the user, then call confirm_prospeo_company_accounts with the companySearchToken to create a domainFilterId before using search_prospeo for people at those accounts. Supports company lookalike, confirmed AI Attributes including pricing, company news, awards, website search, products/services, integrations, key customers, operating languages, Google discovery, headcount by location, structured company ICP, and experimental website traffic/key executive filters. Do not invent company_oids; when seedCompanies or seedDomains are present, omit company_oids and let the backend resolve real Prospeo IDs. company_intent and support-channel guesses like phone/email/chat/ticket/social are unsupported. Public API rows do not include lookalike tier/score/reason. If output includes omittedFilters or warnings, report them as truthful MCP/backend safety handling rather than claiming Prospeo enforced those omitted constraints. ' +
+            "For best-customer, top-customer, customer, or past-company lookalikes, never substitute the sender's current company/domain as the seed unless current-company peers were explicitly requested; use explicit or verified customer/account/past-company seeds and preserve geography like Germany in account or people filters. " +
             prospeoCompanyAccountWorkflowGuidance,
         inputSchema: {
             type: "object",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sellable/mcp",
-  "version": "0.1.232",
+  "version": "0.1.233",
   "type": "module",
   "description": "Sellable MCP server for Claude Code and Codex campaign workflows",
   "main": "dist/index.js",

package/skills/create-campaign/SKILL.md

@@ -220,6 +220,23 @@ reference to avoid long-token copy errors. Account rows are not people leads
 yet. The confirmation creates the `domainFilterId` that constrains the follow-on
 `search_prospeo` people search.
 
+For lookalike seed selection, treat "best customer", "top customer", "past
+companies", "companies I worked with", and similar wording as customer/account
+or past-company seed asks. Never substitute the sender's current company or
+domain as a lookalike seed; never use the sender's current company/domain as a
+silent substitute unless the user explicitly asks for companies like the current
+employer, sender company, or its direct peers/competitors. Seed priority is:
+explicit user-provided customer/account/company/domain; verified
+customer/worked-with/past-company evidence from research/proof; then ask for the
+missing seed or switch to non-lookalike company filters if YOLO requires moving
+without a seed. If using profile/work-history seeds, label them as
+past-company/public proof clues, not confirmed customers unless the source proves
+customer status. If the user asks for a geography like Germany, preserve it in
+account discovery where supported (`company_location_search` or
+`company_icp.geographic_markets`) and in follow-on people search
+(`person_location_search`); do not drop geography when moving from lookalike
+accounts to people leads.
+
 Prospeo company/account search is useful when the source plan depends on
 website traffic (`company_website_traffic`), confirmed AI Attributes including
 `pricing`, `uses_ai`, `has_api`, `has_chrome_extension`, `has_sso`,

package/skills/create-campaign/core/providers/prospeo.json

@@ -24,13 +24,13 @@
     "useWhen": [
       "You want Prospeo filters or domain-based search",
       "You need company lookalike account discovery before finding people",
-      "You want companies like X, best-customer lookalikes, or accounts using AI/API/SSO/Chrome extensions",
+      "You want companies like X, best-customer/top-customer/past-company lookalikes, or accounts using AI/API/SSO/Chrome extensions",
       "You need companies hiring for specific roles using job-posting filters",
       "You need high deliverability from Prospeo"
     ],
     "avoidWhen": ["You need LinkedIn activity filters"],
     "reason": "Strong for hiring-led search, company/account lookalikes, Prospeo-specific filters, verified contacts, and domain lists.",
-    "prose": "Since you're targeting **{icp}**, I'd recommend **Prospeo**.\n\nHere's why:\n- Prospeo can discover lookalike accounts first, then turn approved accounts into a domainFilterId for people search\n- Prospeo can filter for companies hiring specific roles with job-posting filters\n- We can pair those company signals with buyer/referrer titles and verified-contact coverage\n\nFor lookalike accounts, I will show an account sample first; those account rows are not people leads yet. After approval, I will use the companySearchToken to confirm the accounts, then search people at the returned domainFilterId.\n\nShould I search Prospeo for {icp}?"
+    "prose": "Since you're targeting **{icp}**, I'd recommend **Prospeo**.\n\nHere's why:\n- Prospeo can discover lookalike accounts first, then turn approved accounts into a domainFilterId for people search\n- Prospeo can filter for companies hiring specific roles with job-posting filters\n- We can pair those company signals with buyer/referrer titles and verified-contact coverage\n\nFor lookalike accounts, I will show an account sample first; those account rows are not people leads yet. After approval, I will use the companySearchToken to confirm the accounts, then search people at the returned domainFilterId. For best-customer, top-customer, or past-company lookalikes, I will use explicit customer/account/past-company seeds, not the sender's current company, unless you explicitly ask for current-company peers.\n\nShould I search Prospeo for {icp}?"
   },
   "askOption": {
     "label": "Prospeo",

package/skills/create-campaign/references/provider-selection-strategy.md

@@ -99,7 +99,7 @@ Is your ICP LinkedIn-active (founders, sales, marketing, GTM, engineers)?
 Need hiring-by-role filters? -> Prospeo (has company job-posting filters)
 Need tech stack targeting? -> Apollo (has technology filters)
 Have specific company names/domains? -> Sales Navigator for small lists or Prospeo with domainFilterId
-Need companies like X, best-customer lookalikes, AI/API/SSO/Chrome extension filters, news/awards/integrations/key customers? -> Prospeo account discovery first
+Need companies like X, best-customer/top-customer/past-company lookalikes, AI/API/SSO/Chrome extension filters, news/awards/integrations/key customers? -> Prospeo account discovery first; use explicit customer/account/past-company seeds, not the sender's current company unless current-company peers were requested
 ```
 
 ## ICP-to-Provider Quick Reference

package/skills/create-campaign-v2/SKILL.md

@@ -188,6 +188,23 @@ Show the account sample first, ask approval, then pass the returned
 `confirm_prospeo_company_accounts`. The confirmed `domainFilterId` constrains
 the follow-on people search; account rows are not people leads yet.
 
+For lookalike seed selection, treat "best customer", "top customer", "past
+companies", "companies I worked with", and similar wording as customer/account
+or past-company seed asks. Never substitute the sender's current company or
+domain as a lookalike seed; never use the sender's current company/domain as a
+silent substitute unless the user explicitly asks for companies like the current
+employer, sender company, or its direct peers/competitors. Seed priority is:
+explicit user-provided customer/account/company/domain; verified
+customer/worked-with/past-company evidence from research/proof; then ask for the
+missing seed or switch to non-lookalike company filters if YOLO requires moving
+without a seed. If using profile/work-history seeds, label them as
+past-company/public proof clues, not confirmed customers unless the source proves
+customer status. If the user asks for a geography like Germany, preserve it in
+account discovery where supported (`company_location_search` or
+`company_icp.geographic_markets`) and in follow-on people search
+(`person_location_search`); do not drop geography when moving from lookalike
+accounts to people leads.
+
 Before any provider prompt/search/scout call, move the watched campaign to
 source selection, show `## Find Buyers Plan`, then open `request_user_input`
 without repeating the URL. The plan must appear before the question and only

package/skills/find-leads/SKILL.md

@@ -391,6 +391,22 @@ Use first for broad persona expansion, ABM/domain targeting, hiring-led targetin
 - For companies like X, our best customers, lookalike accounts, companies that use AI, companies with API/SSO/Chrome extension, or
   news/award/integration/key-customer account filters, use
   `search_prospeo_companies` before people search.
+- For lookalike seed selection, treat "best customer", "top customer", "past
+  companies", "companies I worked with", and similar wording as
+  customer/account or past-company seed asks. Never substitute the sender's
+  current company or domain as a lookalike seed; never use the sender's current
+  company/domain as a silent substitute unless the user explicitly asks for
+  companies like the current employer, sender company, or its direct
+  peers/competitors. Seed priority is: explicit user-provided
+  customer/account/company/domain; verified customer/worked-with/past-company
+  evidence from research/proof; then ask for the missing seed or switch to
+  non-lookalike company filters if YOLO requires moving without a seed. If using
+  profile/work-history seeds, label them as past-company/public proof clues, not
+  confirmed customers unless the source proves customer status. If the user asks
+  for a geography like Germany, preserve it in account discovery where supported
+  (`company_location_search` or `company_icp.geographic_markets`) and in
+  follow-on people search (`person_location_search`); do not drop geography when
+  moving from lookalike accounts to people leads.
 - Use Prospeo company/account search when the ask depends on website traffic
   (`company_website_traffic`), confirmed AI Attributes including `pricing`,
   `uses_ai`, `has_api`, `has_chrome_extension`, `has_sso`, `has_open_source`,

package/skills/providers/prospeo.md

@@ -87,6 +87,23 @@ backend resolves real Prospeo company IDs. Do not invent company_oids such as
 placeholder IDs from examples. Only send `company_lookalike.company_oids` when
 they are real Prospeo company IDs returned by a prior tool/search.
 
+For lookalike seed selection, treat "best customer", "top customer", "past
+companies", "companies I worked with", and similar wording as customer/account
+or past-company seed asks. Never substitute the sender's current company/domain
+as a lookalike seed, and never use the sender's current company/domain as a
+silent substitute unless the user explicitly asks for companies like the current
+employer, sender company, or its direct peers/competitors. Seed priority is:
+explicit user-provided customer/account/company/domain; verified
+customer/worked-with/past-company evidence from research/proof; then ask for the
+missing seed or switch to non-lookalike company filters if YOLO requires moving
+without a seed. If using profile/work-history seeds, label them as
+past-company/public proof clues, not confirmed customers unless the source proves
+customer status. If the user asks for a geography like Germany, preserve it in
+account discovery where supported (`company_location_search` or
+`company_icp.geographic_markets`) and in follow-on people search
+(`person_location_search`); do not drop geography when moving from lookalike
+accounts to people leads.
+
 For structured ICP sizing, pair `company_icp.company_sizes` with
 `company_headcount_range` when possible. The MCP normalizer derives headcount
 ranges for `micro`, `smb`, `midmarket`, `enterprise`, and `large_enterprise`
@@ -109,6 +126,8 @@ Avoidable-400 guardrails:
 - For seeded company lookalikes, keep the first call simple: seed company/domain + `company_lookalike.minimum_tier` + confirmed attributes, headcount, or industry. Do not add `company_website_search`, `company_keywords`, or `company_icp` until the account sample proves the seed works.
 - For seeded company lookalikes, do not combine `has_api` and `has_sso` in the first call; start with `has_api` and refine after a valid account sample if SSO still matters.
 - Do not send placeholder seed names such as `another approved best-customer seed`; use only concrete company names or domains you have actually resolved.
+- Do not silently use the sender company as a customer lookalike seed; use
+  explicit customer/account/past-company evidence instead.
 - If the user references another approved seed but does not name it, ask for the
   seed or run a one-seed lookalike without `match_all`; do not invent a second
   seed from examples, competitors, or exclusions.
@@ -275,6 +294,13 @@ Preference rules:
 - Run `company_key_customers` as a standalone first-pass filter. Do not combine `company_key_customers` with ICP, website-search, keyword, attribute, industry, or headcount filters until the standalone pass proves useful.
 - For seeded lookalikes, avoid first-call `company_website_search`, `company_keywords`, and `company_icp`; use resolved seeds plus lookalike tier and simple attributes/headcount/industry first.
 - For seeded lookalikes, avoid first-call `has_api` + `has_sso`; use one confirmed attribute first, then refine.
+- For customer, best-customer, top-customer, or past-company lookalikes, never
+  use the sender's current company/domain as a silent substitute; use explicit
+  customer/account/past-company evidence, then label profile-derived seeds as
+  past-company/public proof clues unless customer status is verified.
+- If the user gives geography like Germany, keep that geography in the company
+  discovery or follow-on people filters instead of dropping it after account
+  confirmation.
 - Do not invent missing approved seeds. If a second seed is not named, ask for it
   or run one seed without `match_all`.
 - Prefer `seedDomains` for single-seed lookalikes. For multi-seed `match_all`