@sellable/mcp 0.1.144 → 0.1.145

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
 })
 ```