@sellable/install 0.1.107 → 0.1.108

package/agents/source-scout-linkedin-engagement.md

@@ -57,7 +57,8 @@ currentStep: "signal-discovery" })` before sampling so the watched Signal
    leads per 100 engagers before and after a conservative dedupe/cleanup
    factor, required engagers to scrape (`source target / fit rate`), average
    reachable engagers per right-content post, expected usable leads per
-   right-content post after dedupe/cleanup, and posts needed to hit the target.
+   right-content post after dedupe/cleanup, posts needed to hit the target, and
+   whether sampled/projected fit clears the 10% planning floor.
 8. Select/promote enough right-content posts to plausibly hit the target. If the
    warm Signals pool is useful but too small, return the expected warm range and
    recommend Sales Nav/Prospeo for scale instead of padding with noisy posts.
@@ -74,8 +75,9 @@ Return a concise structured result with:
   engagers, ICP-fit rate as `n/N` plus percentage/range, good-fit prospects per
   100 engagers, required engagers to scrape, average reachable engagers per
   post, expected usable prospects per post after cleanup, posts needed for
-  target, selected post count, review-batch import limit, expected usable lead
-  range, and scale fallback
+  target, whether the 10% planning floor clears after cleanup, selected post
+  count, review-batch import limit, expected usable lead range, and scale
+  fallback
 - `estimated_good_fit_range`
 - `message_context_strength`, directional and source-specific
 - `false_positive_patterns`
@@ -99,3 +101,5 @@ Evidence standards:
   bounded review batch.
 - If `fetch_post_engagers` is unavailable or fails, report that explicitly and mark the estimate lower-confidence.
 - Keep LinkedIn Engagement viable when selected posts can produce roughly 150+ ICP-fit warm prospects before final filtering, even if Sales Nav is more scalable.
+- If sampled/projected fit after cleanup is below 10%, reject the Signals scrape
+  path and recommend Sales Nav recent activity as the next source.

package/agents/source-scout-prospeo-contact.md

@@ -27,7 +27,7 @@ Process:
 1. Read the campaign brief, source intake, kickoff doc, or lane prompt supplied by the parent.
 2. Identify whether this is domain/account targeting or broad persona expansion.
 3. For domain targeting, use or create the standalone `domainFilterId` before searching; never pass raw domains directly into `search_prospeo`.
-4. Run the narrowest useful Prospeo people preview and 1-2 refinements if quality or scale is unclear. Check scale against a default 300+ good-fit target, capped at 2,500 source candidates unless the parent supplies a different target.
+4. Run the narrowest useful Prospeo people preview and 1-2 refinements if quality or scale is unclear. Check scale against a default 300+ good-fit target, capped at 2,500 source candidates unless the parent supplies a different target, and require at least 10% projected good-fit after cleanup.
 5. Call out that Prospeo gives contact/account coverage but usually weaker LinkedIn intent than LinkedIn Engagement or Sales Nav activity slices.
 
 Return a concise structured result with:
@@ -50,4 +50,7 @@ Evidence standards:
 
 - Never pass raw domains, company website arrays, or company-name arrays into `search_prospeo`.
 - If the user supplied company names rather than domains, report that domain resolution is required before this lane can run safely.
+- Prospeo is the terminal fallback. If projected good-fit after cleanup remains
+  below 10% after reasonable refinement, recommend tightening the ICP/source
+  direction rather than switching providers again.
 - Treat Prospeo as an account/contact coverage lane, not as proof of fresh LinkedIn intent.

package/agents/source-scout-sales-nav.md

@@ -35,6 +35,9 @@ Process:
    Loosen nonessential filters in order: remove recent-activity first, widen
    adjacent title variants, widen geography/company-size constraints, and only
    keep hard ICP requirements from the brief.
+   Also check the 10% planning floor after cleanup. If the best reasonable
+   Sales Nav lane remains below 10% projected good-fit, move to Prospeo instead
+   of recommending Sales Nav.
 6. Run the baseline plus 1-2 refinements or loosening passes if the first pass
    is noisy or under-scaled. Label the final pool as constrained if it still
    cannot plausibly reach the target after loosening.
@@ -69,5 +72,7 @@ Evidence standards:
   larger than the warm-post path. If Sales Nav is offered for scale, it should
   either project to the target good-fit count or clearly say it is too tight and
   name the next broadening/Prospeo option.
+- If projected good-fit after cleanup is below 10%, do not recommend Sales Nav
+  as the winning source; recommend Prospeo as the next provider.
 - Do not hand-wave missing filter IDs.
 - If Sales Nav returns a giant unfiltered pool, discard that result and retry with valid filters before recommending it.

package/package.json

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

package/skill-templates/create-campaign.md

@@ -155,14 +155,17 @@ should be a compact `## Source Recommendation` block with:
 - good-fit target: about 150 prospects after cleanup, enrichment, and filters
 - source-candidate plan: about 1,000 raw engagers using a conservative 15%
   fit-rate assumption unless sampled data supports a different number
+- planning floor: continue with Signal Discovery only when sampled/projected
+  fit is at least 10% after cleanup; below that, move to Sales Nav recent
+  activity instead of scraping noisy engagers
 - review checkpoint: import the first 25 leads for fit and message review
 - a selected-post table with post author/topic, why it fits, and visible
   engagement
 - total visible pool and estimated good-fit pool
 - first pass: build the source list, then import only the review
   batch
-- fallback: switch to Sales Nav recent activity if the review batch is
-  vendor-heavy, agency-heavy, or off-ICP
+- fallback: switch to Sales Nav recent activity if sampled/projected fit falls
+  below 10%, or if the review batch is vendor-heavy, agency-heavy, or off-ICP
 
 When the user has not supplied a source and multiple source angles are viable,
 scout those angles as independent branches when the host can actually do it: