@sellable/mcp 0.1.156 → 0.1.158

package/dist/tools/leads.js

@@ -725,8 +725,8 @@ function buildFilterChoiceWatchNarration({ sourceLeadCount, reviewRowCount, samp
 function buildSignalDiscoverySearchWatchNarration() {
     return {
         stage: "find-leads",
-        headline: "Searching Signal Discovery",
-        visibleState: "The browser is showing Signal Discovery while LinkedIn post searches run.",
+        headline: "Searching LinkedIn posts",
+        visibleState: "The browser is showing the LinkedIn post search step while approved themes run.",
         agentIntent: "Codex is searching the approved post themes and will ask before scraping selected engagers into a source list.",
         nextAction: "Review selected posts before scraping",
         safety: "Scrape approval is the next gate.",
@@ -734,11 +734,11 @@ function buildSignalDiscoverySearchWatchNarration() {
 }
 function buildSignalDiscoveryResultsWatchNarration(postsReturned) {
     const postCopy = typeof postsReturned === "number"
-        ? `${postsReturned.toLocaleString("en-US")} post${postsReturned === 1 ? "" : "s"} matched the approved search themes and are visible in Signal Discovery.`
-        : "Signal Discovery results are visible for review.";
+        ? `${postsReturned.toLocaleString("en-US")} post${postsReturned === 1 ? "" : "s"} matched the approved search themes and are visible for review.`
+        : "LinkedIn post results are visible for review.";
     return {
         stage: "find-leads",
-        headline: "Review Signal Discovery posts",
+        headline: "Review LinkedIn posts",
         visibleState: postCopy,
         agentIntent: "Codex is promoting the strongest posts, then it will ask before scraping the selected engager pool.",
         nextAction: "Approve selected posts before scraping",
@@ -749,9 +749,9 @@ function buildSelectedPostApprovalWatchNarration(selectedPostCount) {
     return {
         stage: "find-leads",
         headline: "Approve selected-post scrape",
-        visibleState: `${selectedPostCount.toLocaleString("en-US")} LinkedIn post${selectedPostCount === 1 ? "" : "s"} selected in Signal Discovery.`,
+        visibleState: `${selectedPostCount.toLocaleString("en-US")} LinkedIn post${selectedPostCount === 1 ? "" : "s"} selected for the source test.`,
         agentIntent: "Codex is asking before scraping this selected engager pool into a source list.",
-        nextAction: `Approve scraping ${selectedPostCount.toLocaleString("en-US")} Signal Discovery post${selectedPostCount === 1 ? "" : "s"}`,
+        nextAction: `Approve scraping ${selectedPostCount.toLocaleString("en-US")} selected LinkedIn post${selectedPostCount === 1 ? "" : "s"}`,
         safety: "Scrape approval is the next gate.",
     };
 }
@@ -775,12 +775,12 @@ function buildSignalDiscoverySourceRecommendation({ selectedPosts, }) {
     const estimatedGoodFit = totalEngagement * defaultFitRate;
     return `## Source Recommendation
 
-Use Signal Discovery first.
+Use LinkedIn engagement first.
 
-**Goal:** ~${targetGoodFitLeads.toLocaleString("en-US")} headline-fit prospects that pass the Signal Discovery headline criteria<br>
+**Goal:** ~${targetGoodFitLeads.toLocaleString("en-US")} headline-fit prospects from relevant LinkedIn engagement<br>
 **Working assumption:** ~${Math.round(defaultFitRate * 100)}% of raw post engagers pass headline filtering unless a real sample supports a different rate<br>
 **Engagers needed:** ~${sourceCandidateTarget.toLocaleString("en-US")} raw engagers<br>
-**Planning floor:** continue with Signal Discovery only when sampled/projected headline-fit rate is at least ${Math.round(minPlanningFitRate * 100)}%; below that, switch to Sales Nav recent activity<br>
+**Planning floor:** continue with LinkedIn engagement only when sampled/projected headline-fit rate is at least ${Math.round(minPlanningFitRate * 100)}%; below that, switch to Sales Nav recent activity<br>
 **Review checkpoint:** copy the confirmed source list into the campaign, then process the first ${reviewBatchSize.toLocaleString("en-US")} leads for fit and message review before scaling
 
 ### Selected posts
@@ -804,7 +804,7 @@ This gives enough volume to target ~${targetGoodFitLeads.toLocaleString("en-US")
 
 Approval card should say:
 
-**Approve scraping ${selectedCount} Signal Discovery post${selectedCount === 1 ? "" : "s"}?**`;
+**Approve scraping ${selectedCount} selected LinkedIn post${selectedCount === 1 ? "" : "s"}?**`;
 }
 function normalizeImportProvider(provider) {
     if (provider === "apollo-ai" || provider === "apollo")
@@ -2324,11 +2324,16 @@ export async function importLeads(input) {
     const sourcingSteps = new Set([
         null,
         "pick-provider",
+        "contact-search",
         "apollo",
+        "apollo-select-leads",
         "sales-nav",
+        "sales-nav-select-leads",
         "prospeo",
+        "prospeo-select-leads",
         "signal-discovery",
         "signal-discovery-results",
+        "leads",
     ]);
     const shouldDefaultStep = currentStep === undefined && sourcingSteps.has(campaignCurrentStep ?? null);
     const effectiveCurrentStep = shouldDefaultStep
@@ -3089,15 +3094,15 @@ export async function selectPromisingPosts(input) {
         const { reviewBatchSize } = getSignalDiscoverySourcePlanDefaults();
         sourceRecommendation = `## Source Recommendation
 
-Use Signal Discovery first.
+Use LinkedIn engagement first.
 
-**Recommendation:** approve scraping the ${selectionResult.selectedCount} selected Signal Discovery post${selectionResult.selectedCount === 1 ? "" : "s"}.
+**Recommendation:** approve scraping the ${selectionResult.selectedCount} selected LinkedIn post${selectionResult.selectedCount === 1 ? "" : "s"}.
 
 	**First pass:** build the source list, copy it into the campaign, then process only the first ${reviewBatchSize.toLocaleString("en-US")} leads so we can inspect quality before scaling.
 
 Approval card should say:
 
-**Approve scraping ${selectionResult.selectedCount} Signal Discovery post${selectionResult.selectedCount === 1 ? "" : "s"}?**`;
+**Approve scraping ${selectionResult.selectedCount} selected LinkedIn post${selectionResult.selectedCount === 1 ? "" : "s"}?**`;
     }
     return {
         success: true,

package/package.json

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

package/skills/create-campaign/SKILL.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.

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

@@ -133,7 +133,7 @@ copy.
 
 Default source order when the user has not supplied a source:
 
-1. LinkedIn post engagement / Signal Discovery
+1. LinkedIn post engagement (internal provider: `signal-discovery`)
 2. Sales Nav recent activity
 3. broader Sales Nav role/title filters
 4. Prospeo account/contact expansion
@@ -160,12 +160,14 @@ the question, and this first approval authorizes source scouting/search only:
 - 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 the campaign looks unlikely to have relevant
-public conversations, recommend the specific Sales Nav or Prospeo lane instead
-and say why. An approval like "Approve Prospeo plan" satisfies this gate; persist
-the provider and search next. Do not ask a second source-plan question. Do not
-call `search_signals`, `search_sales_nav`, `search_prospeo`,
+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 the campaign
+looks unlikely to have relevant public conversations, recommend the specific
+Sales Nav or Prospeo lane instead and say why. An approval like "Approve Prospeo
+plan" satisfies this gate; persist the provider and search next. Do not ask a
+second source-plan question. 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.
 
@@ -174,18 +176,19 @@ sequential by default. Run `source-scout-linkedin-engagement`,
 `source-scout-sales-nav`, and `source-scout-prospeo-contact` in parallel only
 when the user explicitly requested source comparison, a prior lane failed, or
 the first viable lane is borderline and a cheap fallback check is needed.
-Use a 10% planning floor after conservative cleanup. If Signal Discovery falls
-below that floor, move to Sales Nav. If Sales Nav falls below that floor after
-reasonable refinement, move to Prospeo. Prospeo is the terminal fallback; if it
-also falls below 10%, tighten the ICP/source direction instead of inventing
-another provider.
+Use a 10% planning floor after conservative cleanup. If LinkedIn engagement
+falls below that floor, move to Sales Nav. If Sales Nav falls below that floor
+after reasonable refinement, move to Prospeo. Prospeo is the terminal fallback;
+if it also falls below 10%, tighten the ICP/source direction instead of
+inventing another provider.
 
 After scouting, show a second approval gate for the concrete source action.
-For Signal Discovery, state selected-post count, target engager/source-candidate
-volume, internal campaign-table execution-slice size, cleanup risk, and fallback;
-label the approval like "Approve scraping 3 Signal Discovery posts?" For Sales
-Nav or Prospeo, name the specific search/import lane and source lead count. Do
-not call `import_leads` or `confirm_lead_list` until this gate is approved.
+For LinkedIn engagement (`signal-discovery` internally), state selected-post
+count, target engager/source-candidate volume, internal campaign-table
+execution-slice size, cleanup risk, and fallback; label the approval like
+"Approve scraping 3 selected LinkedIn posts?" For Sales Nav or Prospeo, name the
+specific search/import lane and source lead count. Do not call `import_leads` or
+`confirm_lead_list` until this gate is approved.
 
 For Sales Nav and Prospeo, do not ask to import only the internal 15-row
 campaign-table execution slice at the source-action gate. First-page samples are
@@ -205,15 +208,15 @@ export count, not the campaign execution-slice size. For Signal Discovery, pass
 `confirmed: true`; the tool owns moving the watch UI to source-list progress
 after a lead-list/job id exists.
 
-For Signal Discovery, use this compact source-action approval shape after
+For LinkedIn engagement, use this compact source-action approval shape after
 selected posts exist:
 
 ```markdown
 ## Source Recommendation
 
-Use Signal Discovery first.
+Use LinkedIn engagement first.
 
-**Goal:** ~300 headline-fit prospects that pass the Signal Discovery headline criteria<br>
+**Goal:** ~300 headline-fit prospects from relevant LinkedIn engagement<br>
 **Working assumption:** ~20% of raw post engagers pass headline filtering unless a real sample supports a different rate<br>
 **Engagers needed:** ~1,500 raw engagers<br>
 **Planning floor:** continue only when sampled/projected headline-fit rate is at least 10%; below that, switch to Sales Nav recent activity<br>

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

@@ -239,12 +239,12 @@ source. That approval only authorizes scouting/search. Second, after the
 source evidence exists, show counts, samples, fit math, cleanup risk, and ask
 for source approval before import.
 
-For Signal Discovery, the second gate is not "approve source" in the abstract.
+For LinkedIn engagement, the second gate is not "approve source" in the abstract.
 It is a concrete scrape approval: show a compact `## Source Recommendation`
-with the ~150 good-fit prospect goal, 15% raw-engager assumption, selected-post
-table, total visible pool, estimated good-fit pool, 10% planning floor,
+with the ~300 headline-fit prospect goal, source sample assumption, selected-post
+table, total visible pool, estimated headline-fit pool, 10% planning floor,
 first-pass campaign setup, and fallback. The approval question should be "Approve
-scraping N Signal Discovery posts?"
+scraping N selected LinkedIn posts?"
 
 That scrape approval is single-use. Once the user approves it, do not replay
 the source card or ask for the same approval again. Acknowledge the approval in
@@ -254,13 +254,13 @@ one sentence and call `import_leads` for the approved source immediately.
 
 Source selection is sequential by default. Start with the first recommended
 source lane from `flow.v2.json`; for the current campaign shape that is usually
-Signal Discovery / LinkedIn engagement. Only try the next fallback after the
+LinkedIn engagement. Only try the next fallback after the
 current lane is not viable, the user asks for a comparison, or the first lane is
 borderline and needs a second source to avoid a bad recommendation. The fallback
 order must stay plain: use Sales Nav to find ICP people who are actively posting
 on LinkedIn; if that is not enough, search Sales Nav by titles; if that is still
 not enough, use Prospeo for a broader account/contact path.
-Use a 10% planning floor after conservative cleanup. If Signal Discovery falls
+Use a 10% planning floor after conservative cleanup. If LinkedIn engagement falls
 below that floor, move to Sales Nav. If Sales Nav falls below that floor after
 reasonable refinement, move to Prospeo. Prospeo is the terminal fallback; if it
 also falls below 10%, tighten the ICP/source direction instead of inventing

package/skills/create-campaign-v2/core/flow.v2.json

@@ -399,14 +399,14 @@
             "what approval authorizes"
           ],
           "choices": [
-            "Approve Signal Discovery scouting plan",
+            "Approve LinkedIn engagement scouting plan",
             "Approve Sales Nav scouting plan",
             "Approve Prospeo scouting plan",
             "Choose different source",
             "Pause here"
           ],
           "approvalChoiceLabelsByProvider": {
-            "signal-discovery": "Approve Signal Discovery scouting plan",
+            "signal-discovery": "Approve LinkedIn engagement scouting plan",
             "sales-nav": "Approve Sales Nav scouting plan",
             "prospeo": "Approve Prospeo scouting plan"
           },
@@ -508,13 +508,13 @@
           "action": "ask_source_review_choice",
           "uses": "request_user_input",
           "choices": [
-            "Approve scraping N Signal Discovery posts",
+            "Approve scraping N selected LinkedIn posts",
             "Run the approved source import",
             "Revise source",
             "Pause here"
           ],
           "approvalChoiceLabelsByProvider": {
-            "signal-discovery": "Approve scraping {selectedPostCount} Signal Discovery posts?",
+            "signal-discovery": "Approve scraping {selectedPostCount} selected LinkedIn posts?",
             "sales-nav": "Import the approved Sales Nav source list",
             "prospeo": "Import the approved Prospeo source list"
           },

package/skills/create-campaign-v2/references/filter-leads.md

@@ -152,9 +152,9 @@ Use this test:
 - Did the campaign rows show adjacent companies that the customer would likely
   reject only after seeing the list?
 
-If yes, add an explicit exclude rule. Include named competitors from the brief,
-campaign rows, or user context when available, plus the general category
-exclusion so new lookalike competitors are also blocked.
+If yes, add an explicit exclude rule. Use the review batch as evidence. Include named competitors
+from the brief, campaign rows, or user context when available, plus the general
+category exclusion so new lookalike competitors are also blocked.
 
 ## Marketplace Safety
 

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

@@ -236,14 +236,14 @@ campaignOfferId, confirmed: true })` -> `search_signals({ campaignOfferId,
 selectionMode: "replace", selections, headlineICPCriteria })` ->
      `import_leads({ campaignOfferId, provider: "signal-discovery",
 	targetEngagerCount: 1500 })`.
-     For Signal Discovery, the promotion/select step is load-bearing. Use
+     For LinkedIn engagement (`signal-discovery` internally), the promotion/select step is load-bearing. Use
      post IDs from the current campaign-scoped `search_signals` response or
      posts the user has visibly promoted in the campaign UI. Never use post IDs
      copied only from a source-scout summary unless they have been re-resolved
      through the current campaign search state. After `select_promising_posts`,
      require `selectedCount > 0` before calling `import_leads`. If it returns
      `selectedCount: 0`, do not switch providers and do not retry import.
-     Explain that the campaign has no promoted Signal Discovery posts yet,
+     Explain that the campaign has no promoted LinkedIn posts yet,
      re-run a narrow campaign-scoped `search_signals` call to recover current
      post rows, or ask the user to promote the desired posts in the UI and then
      retry `import_leads`.