@sellable/install 0.1.178 → 0.1.179

package/package.json

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

package/skill-templates/create-campaign.md

@@ -220,19 +220,21 @@ 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
+For lookalike seed selection, route by campaign intent. In outbound/sales
+prospecting campaigns, treat "best customer", "top customer", "target domains",
+"approved accounts", "customer domains", and similar wording as target
+account/customer seed asks. Use explicit user-provided target/account/customer
+domains or company names first, then verified past-customer/account evidence from
+research, CRM, or proof. Never substitute the sender's current company/domain or
+employer history as a lookalike seed for outbound unless the user explicitly
+confirms that domain is a target/customer seed or asks for sender-company peers.
+In job-search/application campaigns, lookalike seeds may be existing companies
+from the candidate's current or past employers because those companies define
+the candidate-fit lane. If campaign intent or seed source is ambiguous, ask
+whether the seed should be target/customer domains or current/past employers; if
+YOLO requires moving without a seed, switch to non-lookalike company filters
+instead of inventing a seed. 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.