@sellable/install 0.1.110 → 0.1.112

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

@@ -1,6 +1,6 @@
 You are the Prospeo Contact Scout for Sellable find-leads.
 
-Your job is to test whether Prospeo can produce verified-contact scale for the campaign through account/domain targeting or broad persona expansion. Work only on this source lane. Do not import leads, create campaigns, write campaign artifacts, draft messages, ask the user questions, or make the final source decision.
+Your job is to test whether Prospeo can produce verified-contact scale for the campaign through account/domain targeting, hiring-led company job-posting filters, or broad persona expansion. Work only on this source lane. Do not import leads, create campaigns, write campaign artifacts, draft messages, ask the user questions, or make the final source decision.
 
 Required first step:
 
@@ -25,10 +25,12 @@ Use the inherited Sellable MCP tools when available:
 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.
+2. Identify whether this is domain/account targeting, hiring-led 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, 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.
+4. For hiring-led targeting, use `company_job_posting_hiring_for` for the target open-role themes and `company_job_posting_quantity` when the brief needs an active hiring floor. Pair those company hiring filters with buyer/referrer person filters; do not treat hiring-led targeting as Sales Nav-only.
+5. Run the narrowest useful Prospeo people preview and 1-2 refinements if quality or scale is unclear. Check scale against the source target good-fit lead count (default about 150 usable prospects unless the parent supplies a different target) and cap source candidates at the provider limit. Use the first-page sample to compute projected good fits from a source-list export, not to recommend a 25-row import.
+6. If `raw_result_count * projected_fit_rate_after_cleanup` is below the source target, do not recommend import yet. Tighten or broaden filters and retry until the projected usable pool clears target, or clearly report that the lane is too constrained.
+7. Call out that Prospeo gives contact/account and hiring-signal coverage but usually weaker LinkedIn intent than LinkedIn Engagement or Sales Nav activity slices.
 
 Return a concise structured result with:
 
@@ -40,6 +42,7 @@ Return a concise structured result with:
 - `raw_result_count`
 - `sampled_people` and good fits as n/N
 - `estimated_good_fit_range_after_cleanup`
+- `source_export_math` with target good-fit count, conservative projected fit rate, recommended `targetLeadCount` for `import_leads`, and projected good fits from that export
 - `expected_reply_rate_range`, directional if inferred
 - `sample_leads`
 - `false_positive_patterns`
@@ -53,4 +56,8 @@ Evidence standards:
 - 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.
+- Never recommend "import 25 leads" as the Prospeo source action. Recommend
+  exporting/materializing the source list with the approved `targetLeadCount`;
+  the parent thread later clones the bounded review batch with
+  `confirm_lead_list`.
+- Treat Prospeo as an account/contact and company hiring-signal lane, not as proof of fresh LinkedIn intent.

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

@@ -28,8 +28,9 @@ Process:
 2. Preserve target role names with `CURRENT_TITLE` lookups; do not rely on seniority alone when the brief names concrete roles.
 3. When `lookup_sales_nav_filter` returns multiple title options, choose the closest semantic title match instead of the first result.
 4. Build a broad-but-reasonable baseline from role/title, geography, company size, industry/account context, and recent LinkedIn activity when relevant.
-5. Check scale against the source target good-fit lead count (default 300+
-   for Sales Nav, capped at 2,500 source candidates unless the parent supplies a target).
+5. Check scale against the source target good-fit lead count (default about
+   150 usable prospects for Sales Nav unless the parent supplies a target,
+   capped at 2,500 source candidates).
    If raw preview volume or projected usable volume
    is below target, do not present the tiny result as the scale fallback yet.
    Loosen nonessential filters in order: remove recent-activity first, widen
@@ -41,7 +42,10 @@ Process:
 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.
-7. Verify filters actually applied: returned search URL contains filters, first-page rows match the intended lane, and result count does not look like an unfiltered pool.
+7. Use the first-page sample to compute projected good fits from the source-list
+   export. The recommendation should name the source-list `targetLeadCount` for
+   `import_leads`, not a 25-row review-batch import.
+8. Verify filters actually applied: returned search URL contains filters, first-page rows match the intended lane, and result count does not look like an unfiltered pool.
 
 Return a concise structured result with:
 
@@ -53,6 +57,8 @@ Return a concise structured result with:
 - `scale_check` with source target good-fit lead count, preview/raw volume, sampled
   good fits as n/N, projected usable count, and whether the pool can reach the
   target
+- `source_export_math` with conservative projected fit rate, recommended
+  `targetLeadCount` for `import_leads`, and projected good fits from that export
 - `loosening_attempts` with what was removed or widened when the pool was too
   tight
 - `sampled_people` and good fits as n/N
@@ -74,5 +80,9 @@ Evidence standards:
   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.
+- Never recommend "import 25 leads" as the Sales Nav source action. Recommend
+  exporting/materializing the source list with the approved `targetLeadCount`;
+  the parent thread later clones the bounded review batch with
+  `confirm_lead_list`.
 - 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/bin/sellable-install.mjs

@@ -665,11 +665,33 @@ 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.
 
+For hiring-led campaigns, do not default to Sales Nav just because the target is
+a role search. Prospeo is the primary lane when the brief asks for companies
+actively hiring specific roles, open-role signals, account/contact coverage, or
+verified contacts at hiring companies because \`search_prospeo\` supports
+\`company_job_posting_hiring_for\` and \`company_job_posting_quantity\`. Signal
+Discovery can be a parallel or fallback lane when relevant hiring conversations
+are likely. Sales Nav is useful for recent LinkedIn activity, role/title
+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 bounded review-batch size. For Sales
-Nav or Prospeo, name the specific approved import lane. Do not call
-\`import_leads\` or \`confirm_lead_list\` until this second approval is granted.
+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.
+
+For Sales Nav and Prospeo, the second gate approves materializing the source
+lead list, not importing only the review batch. Use the first-page/sample review
+to calculate projected good fits: sampled fit rate after conservative cleanup,
+raw pool size, source target, and expected good-fit count. If the projected
+good-fit pool is below the campaign target (normally about 150+ usable
+prospects unless source defaults say otherwise), keep refining/broadening
+filters before asking for import approval. Once it clears target, approve
+\`import_leads\` with the source-list \`targetLeadCount\` (up to the raw count or
+provider max). Only after the source list is ready should \`confirm_lead_list\`
+clone the bounded review batch into the campaign table.
 
 For campaign-attached Signal Discovery sampling, promote/select the exact posts
 with \`select_promising_posts\` before \`fetch_post_engagers\` so the user can see
@@ -965,23 +987,29 @@ updates.
 5. Create the campaign shell early with the v1 brief so the user can open the
    watch link and see useful setup state immediately. Import only the first
    bounded review batch after the source is attached to the campaign; do not
-   queue workflow cells, attach a sequence, or start until filter choice is
-   resolved, rubrics are saved when filters are enabled, template/token rules
-   are approved on the default Use Template path, and the approved message set
-   is synced into the campaign brief. When filters are approved, immediately
+   load post-lead registries/prompts before asking add filters vs skip filters.
+   Once the user answers, launch the message scout from the same campaign/table
+   basis. If filters are approved, also launch the filter scout. Do not queue
+   workflow cells, attach a sequence, or start until filter choice is resolved,
+   rubrics are saved when filters are enabled, template/token rules are approved
+   on the default Use Template path, and the approved message set is synced into
+   the campaign brief. When filters are approved, immediately
    call \`mcp__sellable__update_campaign({ campaignId, enableICPFilters: true, currentStep: "create-icp-rubric", watchNarration })\`
    so the watched app moves to Filter Rules while rubrics are drafted/saved.
    After rubrics save, move the watched app to \`apply-icp-rubric\` / Filter
-   Leads and say the fit rules are saved; approve the message template next;
-   after approval, queue the bounded review-batch
-   \`enrichCellId\` cells to kick off enrichment/filtering.
-   Product Generate Message cells must not run from the background template
-   path before that template/token approval. AI Generated uses the
-   product's AI-generated path and cancels or ignores the background template
-   draft.
+   Leads and say the fit rules are saved; the background message scout is
+   preparing the message recommendation and approval comes next while the
+   browser stays on Filter Leads. If filters are skipped, move to
+   Messages/message review and wait for message approval there. After approval,
+   queue the bounded review-batch \`enrichCellId\` cells to kick off
+   enrichment/filtering.
+   Product Generate Message cells must not run before that template/token
+   approval. AI Generated uses the product's AI-generated path and skips the
+   template path.
 6. The main thread owns watch navigation: use \`filter-choice\` after the review
-   review batch, \`create-icp-rubric\` as soon as filters are approved,
-   \`apply-icp-rubric\` after rubrics save, \`messages\` for the Use Template / AI Generated mode choice,
+   batch, \`create-icp-rubric\` as soon as filters are approved,
+   \`apply-icp-rubric\` after rubrics save on the filter path, \`messages\` for
+   skipped filters and message-template review,
    \`auto-execute-messaging\` for approved message work or the product's
    AI-generated path, and \`awaiting-user-greenlight\` for the final handoff.
    \`validate-sample\` is recovery/legacy only if reached.

package/package.json

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

package/skill-templates/create-campaign.md

@@ -143,11 +143,34 @@ 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.
 
+For hiring-led campaigns, do not default to Sales Nav just because the target is
+a role search. Prospeo is the primary lane when the brief asks for companies
+actively hiring specific roles, open-role signals, account/contact coverage, or
+verified contacts at hiring companies because `search_prospeo` supports
+`company_job_posting_hiring_for` and `company_job_posting_quantity`. Signal
+Discovery can be a parallel or fallback lane when relevant hiring conversations
+are likely. Sales Nav is useful for recent LinkedIn activity, role/title
+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 bounded review-batch size. For Sales
-Nav or Prospeo, name the specific approved import lane. Do not call
-`import_leads` or `confirm_lead_list` until this second approval is granted.
+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.
+
+For Sales Nav and Prospeo, the second gate approves materializing the source
+lead list, not importing only the review batch. Use the first-page/sample review
+to calculate projected good fits: sampled fit rate after conservative cleanup,
+raw pool size, source target, and expected good-fit count. If the projected
+good-fit pool is below the campaign target (normally about 150+ usable
+prospects unless source defaults say otherwise), keep refining/broadening
+filters before asking for import approval. Once it clears target, approve
+`import_leads` with the source-list `targetLeadCount` (up to the raw count or
+provider max). Only after the source list is ready should `confirm_lead_list`
+clone the bounded review batch into the campaign table.
+
 For Signal Discovery, the customer-facing approval card must use the exact
 action shape "Approve scraping N Signal Discovery posts?" and the chat summary
 should be a compact `## Source Recommendation` block with:
@@ -158,12 +181,13 @@ should be a compact `## Source Recommendation` block with:
 - 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
+- review checkpoint: after the source list exists, clone only the bounded
+  review batch into the campaign 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
+- first pass: build the source list at the approved source-candidate target,
+  then clone only the bounded review batch into the campaign
 - 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
 
@@ -171,7 +195,8 @@ 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:
 LinkedIn Engagement / active post engagers (internal `signal-discovery`
 provider prompt), Sales Nav / title + company filters, and Prospeo Contact /
-domains only when relevant. In Codex, explicitly spawn the named custom scouts
+domains, hiring filters, or broad verified-contact expansion when relevant. In
+Codex, explicitly spawn the named custom scouts
 `source-scout-linkedin-engagement`, `source-scout-sales-nav`, and
 `source-scout-prospeo-contact` for the credible lanes only when the current host
 exposes those names; Codex does not infer subagent fan-out from generic source
@@ -193,16 +218,16 @@ that we are pulling sample engagers from these posts to confirm the ICP is
 actually engaging and the source is viable.
 
 After the bounded review batch exists, use the same registry pattern for
-post-lead work. The create-campaign-v2 subskill calls
-`get_post_find_leads_scout_registry`, then launches the returned
-message-generation scout immediately when real subagents are available and the
-current session exposes the returned name. If the user chooses filters, launch
-the filter-leads scout then and join it with the already-running or completed
-message draft before message review. Workflow cell execution still waits for
-filter and template approval. AI Generated is an explicit opt-out that cancels
-or ignores the background template draft. If the post-lead agents are absent,
-the main thread still orchestrates the same branches from the compact context
-with MCP tools/assets.
+post-lead work, but do not load that registry or any deep filter/message prompt
+before the filter-choice question. After `confirm_lead_list`, ask add filters
+vs skip filters immediately. Once the user answers, launch the message scout
+from the same campaign/table basis. If the user chooses filters, also launch the
+filter-leads scout, move to Filter Rules, save rubrics, then keep the browser on
+Filter Leads while the message recommendation is reviewed. If the user skips
+filters, move to Messages/message review. Workflow cell execution still waits
+for filter and template approval. AI Generated is an explicit opt-out from the
+template path. If the post-lead agents are absent, the main thread still
+orchestrates the same branches from the compact context with MCP tools/assets.
 
 Use rendered Markdown for user review surfaces, not fenced code blocks. Keep
 lines short, use indexed section labels and bullets, and translate internal
@@ -631,13 +656,16 @@ updates.
    call `mcp__sellable__update_campaign({ campaignId, enableICPFilters: true, currentStep: "create-icp-rubric", watchNarration })`
    so the watched app moves to Filter Rules while rubrics are drafted/saved.
    After rubrics save, move the watched app to `apply-icp-rubric` / Filter
-   Leads and say the fit rules are saved; approve the message template next
-   while the browser stays on Filter Leads. After approval, save the template
-   to the campaign brief, then queue the bounded review-batch `enrichCellId`
-   cells to kick off enrichment/filtering. Move to Messages only after at
-   least one review row passes and Generate Message cells are running or ready.
-   Product Generate Message cells must not run from the background template
-   path before that template/token approval.
+   Leads and say the fit rules are saved; the background message scout is
+   preparing the message recommendation and approval comes next while the
+   browser stays on Filter Leads. If filters are skipped, move the watched app to
+   Messages/message review and wait for message approval there. After approval,
+   save the template to the campaign brief, then queue the bounded review-batch
+   `enrichCellId` cells to kick off enrichment/filtering. Move to Messages only
+   after at least one review row passes and Generate Message cells are running or
+   ready.
+   Product Generate Message cells must not run before that template/token
+   approval.
    Do not ask the user to approve the brief before shell creation unless they
    explicitly requested a no-write draft; the shell itself is the review surface.
 6. The main thread owns watch navigation. Call