@sellable/install 0.1.120 → 0.1.121

package/bin/sellable-install.mjs

@@ -655,10 +655,12 @@ should say:
 - that approval authorizes scouting/search only, not lead import or sending
 
 Do not surface blanket source heuristics as product copy. Make the
-recommendation specific to the campaign. If Signal Discovery is recommended,
-name the exact post themes you will search. If relevant public conversations
-look unlikely, recommend the specific Sales Nav or Prospeo lane instead and say
-why. Do not call \`search_signals\`, \`search_sales_nav\`, \`search_prospeo\`,
+recommendation specific to the campaign. If LinkedIn engagement is recommended,
+name the exact post themes you will search and avoid using "Signal Discovery" in
+customer-facing chat; that is the internal provider/app label. If relevant
+public conversations look unlikely, recommend the specific Sales Nav or Prospeo
+lane instead and say why. Do not call \`search_signals\`, \`search_sales_nav\`,
+\`search_prospeo\`,
 \`fetch_post_engagers\`, or provider-scoped subagents until the user approves this
 source plan or explicitly chooses a different source.
 
@@ -677,9 +679,10 @@ precision, and referral paths, but it does not provide hiring-by-role filters;
 say that distinction plainly in the source-plan gate.
 
 After scouting, ask for a second approval on the concrete source action. For
-Signal Discovery, name how many selected posts will be scraped, the target
-engager/source-candidate volume, and the internal campaign-table execution-slice
-size. For Sales Nav or Prospeo, name the specific approved import lane and source lead count.
+LinkedIn engagement (\`signal-discovery\` internally), name how many selected
+posts will be scraped, the target engager/source-candidate volume, and the
+internal campaign-table execution-slice size. For Sales Nav or Prospeo, name the
+specific approved import lane and source lead count.
 Do not call \`import_leads\` or \`confirm_lead_list\` until this second approval is
 granted.
 

package/package.json

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

package/skill-templates/create-campaign.md

@@ -139,10 +139,12 @@ should say:
 - what approval covers in one concise line
 
 Do not surface blanket source heuristics as product copy. Make the
-recommendation specific to the campaign. If Signal Discovery is recommended,
-name the exact post themes you will search. If relevant public conversations
-look unlikely, recommend the specific Sales Nav or Prospeo lane instead and say
-why. Do not call `search_signals`, `search_sales_nav`, `search_prospeo`,
+recommendation specific to the campaign. If LinkedIn engagement is recommended,
+name the exact post themes you will search and avoid using "Signal Discovery" in
+customer-facing chat; that is the internal provider/app label. If relevant
+public conversations look unlikely, recommend the specific Sales Nav or Prospeo
+lane instead and say why. Do not call `search_signals`, `search_sales_nav`,
+`search_prospeo`,
 `fetch_post_engagers`, or provider-scoped subagents until the user approves this
 source plan or explicitly chooses a different source.
 
@@ -161,10 +163,11 @@ precision, and referral paths, but it does not provide hiring-by-role filters;
 say that distinction plainly in the source-plan gate.
 
     After scouting, ask for a second approval on the concrete source action. For
-    Signal Discovery, name how many selected posts will be scraped and the
-    target engager/source-candidate volume. For Sales Nav or Prospeo, name the
-    specific approved import lane and source lead count. Keep the internal
-    15-row campaign-table execution slice separate from source sampling.
+    LinkedIn engagement (`signal-discovery` internally), name how many selected
+    posts will be scraped and the target engager/source-candidate volume. For
+    Sales Nav or Prospeo, name the specific approved import lane and source lead
+    count. Keep the internal 15-row campaign-table execution slice separate from
+    source sampling.
 
 Do not call `import_leads` or `confirm_lead_list` until this second approval is
 granted.
@@ -181,16 +184,15 @@ granted.
     should `confirm_lead_list({ reviewBatchLimit: 15 })` copy confirmed rows into
     the campaign table and return the initial campaign-table execution slice rows.
 
-For Signal Discovery, the customer-facing approval card must use the exact
-action shape "Approve scraping N Signal Discovery posts?" and the chat summary
+For LinkedIn engagement, the customer-facing approval card must use the exact
+action shape "Approve scraping N selected LinkedIn posts?" and the chat summary
 should be a compact `## Source Recommendation` block with:
 
-- goal: about 300 headline-fit prospects that pass the Signal Discovery
-  headline criteria for now
+- goal: about 300 headline-fit prospects from relevant LinkedIn engagement
 - source-candidate plan: use sample math first: target headline-fit prospects
   divided by sampled headline-pass rate. If there is no stronger sample, use
   about 1,500 raw engagers from the 20% working headline-pass assumption.
-- planning floor: continue with Signal Discovery only when sampled/projected
+- planning floor: continue with LinkedIn engagement only when sampled/projected
   headline-fit rate is at least 10%; below that, move to Sales Nav recent
   activity instead of scraping noisy engagers. Do not use the 10% floor as the
   scrape-count denominator when the actual sample rate is higher.