@sellable/mcp 0.1.143 → 0.1.145

package/skills/providers/prospeo.md

@@ -62,7 +62,8 @@ search_prospeo({
 - Pass `searchId` on subsequent pages to paginate.
 - Use `import_leads` with `provider: \"prospeo\"` and the `searchId` to create a lead list and start import.
 - **IMPORTANT:** If `import_leads` returns `needsModeSelection: true`, use `AskUserQuestion` to ask "add to existing leads or replace?" Do NOT assume.
-- After the list finishes and the user confirms it looks good, call `confirm_lead_list` with the `jobId` and `targetLeadCount` from `import_leads` to import into the campaign table.
+- Default source target is 300+ good-fit leads, capped at 2,500 source candidates for now.
+- After the list finishes and the user confirms it looks good, call `confirm_lead_list` with the `jobId` and the review-batch `targetLeadCount` from the active campaign defaults to import only the review batch into the campaign table.
 - `import_leads` owns the watched move to `confirm-lead-list` after a lead list/job exists.
 - `confirm_lead_list` owns the watched move to `filter-choice` after the bounded review batch exists.
 - Post-confirm readback order is required:

package/skills/providers/sales-nav.md

@@ -349,9 +349,9 @@ Step 4 - Final Search + Confirm:
 What would you like?"
 
 User: "Save it"
-→ import_leads({campaignOfferId: "cmp_xxx", searchId: "search_xxx", targetLeadCount: 100})
+→ import_leads({campaignOfferId: "cmp_xxx", searchId: "search_xxx", targetLeadCount: 300})
 → (wait for lead list to finish, ask user to confirm)
-→ confirm_lead_list({campaignOfferId: "cmp_xxx", jobId: "<jobId from import_leads>", targetLeadCount: 100})
+→ confirm_lead_list({campaignOfferId: "cmp_xxx", jobId: "<jobId from import_leads>", targetLeadCount: 25})
 → wait_for_campaign_table_ready({campaignId: "cmp_xxx"})
 → get_campaign_context({campaignId: "cmp_xxx", refresh: true}) + get_rows_minimal(...)
 </iteration_example>
@@ -382,6 +382,8 @@ User: "Save it"
 <limits>
 - 25 results per page
 - Maximum 100 pages (2,500 leads)
+- Default source target: 300+ good-fit leads, capped at 2,500 source
+  candidates for now
 - Maximum 5 search calls per session
 - If user needs more than 2,500: explain limit, suggest splitting by region
 </limits>

package/skills/providers/signal-discovery.md

@@ -98,11 +98,12 @@ You must estimate:
   - expected good-fit prospects per right-content post after dedupe/cleanup
 - `postsNeededForTarget`
   - number of right-content posts needed to reach the target good-fit lead
-    count, defaulting to 300 unless the campaign says otherwise
+    count, defaulting to 150 for Signal Discovery unless the campaign says
+    otherwise
 - `requiredEngagersToScrape`
-  - `ceil(targetGoodFitLeads / sampledFitRate)`; for example 20 good-fit
-    prospects per 100 engagers means a 300-good-fit source target needs about
-    1,500 engagers scraped
+  - `ceil(targetGoodFitLeads / sampledFitRate)`; for example 15 good-fit
+    prospects per 100 engagers means a 150-good-fit source target needs about
+    1,000 engagers scraped
 - `projectedRange`
   - the conservative range implied by the observed sample
 
@@ -126,7 +127,7 @@ Use conservative logic:
    - stale posts
    - adjacent communities that are not actual buyers
 4. Explain the pass-through briefly and explicitly:
-   - preferred: "`sampledCount`: 40, `passCount`: 9, `passRate`: ~22%, `goodFitPer100Engagers`: ~22 before cleanup / ~13-16 after cleanup, `requiredEngagersToScrape`: ~1,875-2,300 for a 300-good-fit target after cleanup, `avgReachableEngagersPerPost`: 240, `goodFitProspectsPerPost`: ~31-38, `postsNeededForTarget`: ~8-10, `recentStrongPostCount`: 15-25, `freshEnoughPostCount`: 8-12, `projectedRange`: 300-380 from selected posts"
+   - preferred: "`sampledCount`: 40, `passCount`: 9, `passRate`: ~22%, `goodFitPer100Engagers`: ~22 before cleanup / ~13-16 after cleanup, `requiredEngagersToScrape`: ~940-1,150 for a 150-good-fit target after cleanup, `avgReachableEngagersPerPost`: 240, `goodFitProspectsPerPost`: ~31-38, `postsNeededForTarget`: ~4-5, `recentStrongPostCount`: 15-25, `freshEnoughPostCount`: 8-12, `projectedRange`: 150-190 from selected posts"
    - fallback: "I could not fetch engagers, so this is inferred from post and author quality only"
 5. If the evidence is too weak, say so and return a low-confidence estimate instead of pretending precision.
 6. Do not manually enumerate dozens of engagers in the final answer. Summarize the sample by `sampledCount`, `passCount`, `passRate`, `projectedRange`, and 3-6 representative examples.
@@ -378,7 +379,8 @@ For `create-campaign-v2` source approval, do not treat the default
 `selectionTarget` of 3 posts as enough by itself. Before the final source
 recommendation, estimate source capacity from real sample math:
 
-- source target good-fit leads (default 300 unless the campaign says otherwise)
+- source target good-fit leads (default 150 for Signal Discovery unless the
+  campaign says otherwise)
 - eligible right-content posts by lane/content type
 - reachable engagers from those posts
 - sampled ICP-fit rate as `n/N` plus an easy percentage/range
@@ -447,7 +449,7 @@ selections, headlineICPCriteria })`, then call
 targetLeadCount, targetEngagerCount, maxPostsToScrape })` for the approved
 source-capacity plan without asking for another yes/no gate. Then
 `confirm_lead_list` imports only the bounded review batch into the campaign
-table. Do not confuse the source scrape target with the 15-row review batch.
+table. Do not confuse the source-candidate target with the review-batch size.
 
 The promotion/select step is required campaign state. Use post IDs from the
 current campaign-scoped search result, not stale IDs copied from a source review
@@ -460,8 +462,8 @@ the source-list materialization.
 ```json
 import_leads({
   "campaignOfferId": "cmp_xxx",
-  "targetLeadCount": 300,
-  "targetEngagerCount": 1500,
+  "targetLeadCount": 1000,
+  "targetEngagerCount": 1000,
   "maxPostsToScrape": 5
 })
 ```
@@ -474,7 +476,7 @@ After the lead list finishes and the user confirms it looks good, call:
 confirm_lead_list({
   "campaignOfferId": "cmp_xxx",
   "jobId": "<jobId from import_leads>",
-  "targetLeadCount": 15
+  "targetLeadCount": 25
 })
 ```
 

package/skills/research/config.json

@@ -0,0 +1,9 @@
+{
+  "parallelMode": "wide",
+  "agentCount": 6,
+  "maxToolCallsPerAgent": 2,
+  "senderMaxAgents": 2,
+  "senderMaxToolCallsPerAgent": 3,
+  "progressMode": true,
+  "debugMode": true
+}