@sellable/install 0.1.168 → 0.1.170

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sellable/install",
-  "version": "0.1.168",
+  "version": "0.1.170",
   "type": "module",
   "description": "One-command installer for Sellable MCP in Claude Code and Codex",
   "bin": {

package/skill-templates/create-campaign.md

@@ -214,9 +214,11 @@ before person search, use the Prospeo account approval flow:
 First return an account sample and ask the user to approve the account set.
 Only call `confirm_prospeo_company_accounts` with the `companySearchToken`
 returned by `search_prospeo_companies` and selected Prospeo company IDs; never
-reconstruct raw account rows or domains manually. Account rows are not people
-leads yet. The confirmation creates the `domainFilterId` that constrains the
-follow-on `search_prospeo` people search.
+reconstruct raw account rows or domains manually; always copy the `companySearchToken` exactly.
+Package-backed MCP may return a short `mcp-prospeo-company-search-token:*`
+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.
 
 Prospeo company/account search is useful when the source plan depends on
 website traffic (`company_website_traffic`), confirmed AI Attributes including
@@ -232,9 +234,28 @@ the MCP backend resolves real Prospeo company IDs. Do not invent company_oids.
 For company ICP geography, `geographic_scope` only accepts `single_country` or
 `multi_country`; put North America style regions in `geographic_markets` as
 specific markets such as United States and Canada. Product is not a
-company_icp.departments value; use `titles_include` for product roles. Do not
-use `company_intent`, and do not invent unsupported support-channel filters or
-AI Attribute guesses like phone/email/chat/ticket/social.
+company_icp.departments value; use `titles_include` for product roles.
+`company_keywords.include/exclude` values must be at least 3 characters; use
+`artificial intelligence` instead of `AI`, or use confirmed attributes such as
+`uses_ai` when that is the actual signal. Do not use `company_intent`, and do
+not invent unsupported support-channel filters or AI Attribute guesses like
+phone/email/chat/ticket/social.
+Use `company_key_customers` as a standalone first-pass account filter; in short,
+run company_key_customers as a standalone first-pass. Do not combine
+`company_key_customers` with `company_website_search`, `company_icp`,
+`company_keywords`, or broad AI Attributes in the first call. Do not use `AI`,
+`API`, `GTM`, or `SaaS` as company keyword terms; use confirmed attributes or
+spell out artificial intelligence, application programming interface, go to
+market, and software as a service. Do not send `company_keywords.exclude`
+without an include keyword, and do not duplicate `company_industry` when
+`company_icp.industries` already carries the industry. For post-confirm people
+search, prefer `person_job_title.boolean_search` for long role synonym lists
+instead of many `person_job_title.include` values plus broad department/seniority
+filters.
+Do not use `AI`, `API`, `GTM`, or `SaaS` as company keyword terms.
+Do not combine `company_key_customers` with ICP, website-search, keyword,
+attribute, industry, or headcount filters until the standalone pass proves
+useful.
 
     After scouting, ask for a second approval on Start Import. For
     LinkedIn engagement (`signal-discovery` internally), name how many