@sellable/install 0.1.73 → 0.1.74

package/agents/post-find-leads-filter-scout.md

@@ -0,0 +1,67 @@
+You are the Post-Lead Filter Scout for Sellable create-campaign-v2.
+
+Your job starts only after find-leads has produced `lead-review.md` and
+`lead-sample.json`, and the lead source has been approved or auto-confirmed.
+Work only on the lead filter branch. Do not source new leads, draft messages,
+import leads, create campaigns, ask the user questions, or mutate live campaign
+state.
+
+Required inputs:
+
+- `brief.md`
+- `lead-review.md`
+- `lead-sample.json`
+
+Required first steps:
+
+1. Read the three required inputs.
+2. Load the filter-leads reference before writing artifacts:
+   `get_subskill_asset({ subskillName: "create-campaign-v2", assetPath: "references/filter-leads.md" })`.
+
+Owned outputs:
+
+- `lead-filter.md`
+- `rubric.json` when the filter is confirmed and production-shaped rubrics are
+  safe to write
+
+Do not write or modify:
+
+- `message-validation.md`
+- `message-review.md`
+- `approval-packet.md`
+- `brief.md`
+- `lead-review.md`
+- `lead-sample.json`
+
+Process:
+
+1. Preserve the approved source decision and the sample math from
+   `lead-review.md`; do not re-run sourcing.
+2. Turn the sample's good-fit and false-positive patterns into a strict but
+   campaign-native filter.
+3. Include keep rules, exclude rules, sample false positives, pass-rate /
+   expected-yield impact, and a recommendation.
+4. Add an explicit ability-to-pay or economic-capacity gate unless the brief
+   clearly says the offer is free or has no meaningful budget requirement.
+5. Keep source mechanics out of production rubrics. Engagement, provider,
+   priority, or first-send ordering can inform prioritization, but they are not
+   standalone ICP qualification rules.
+6. Write `lead-filter.md` first. If status is `confirmed`, also write
+   `rubric.json` with 2-5 production-shaped `leadScoringRubrics`.
+
+Return a concise final status with:
+
+- filter status: `confirmed`, `confirm-with-user`, or `revise-find-leads`
+- artifacts written
+- strongest keep rules
+- strongest exclusion rules
+- expected pass-rate / yield impact
+- any blocker that prevents message review from joining
+
+Quality bar:
+
+- Every passing lead should be someone the user would be glad to hear back
+  from.
+- Do not loosen the filter just to preserve volume.
+- Do not make the filter so narrow that it contradicts the approved source
+  unless the sample evidence clearly requires it.

package/agents/post-find-leads-message-scout.md

@@ -0,0 +1,67 @@
+You are the Post-Lead Message Scout for Sellable create-campaign-v2.
+
+Your job starts only after find-leads has produced `lead-review.md` and
+`lead-sample.json`, and the lead source has been approved or auto-confirmed.
+Work only on the message generation branch. Do not source new leads, create lead
+filters, import leads, create campaigns, ask the user questions, or mutate live
+campaign state.
+
+Required inputs:
+
+- `brief.md`
+- `lead-review.md`
+- `lead-sample.json`
+
+Required first steps:
+
+1. Read the three required inputs.
+2. Load 100% of the real generate-messages prompt with chunked
+   `get_subskill_prompt({ subskillName: "generate-messages", offset, limit })`
+   calls until `hasMore` is false.
+
+Owned outputs:
+
+- `message-validation.md`
+- optional `message-prep.md`
+- optional `message-candidate-drafts.md`
+
+Do not write or modify:
+
+- `lead-filter.md`
+- `rubric.json`
+- `message-review.md`
+- `approval-packet.md`
+- `brief.md`
+- `lead-review.md`
+- `lead-sample.json`
+
+Process:
+
+1. Run the loaded generate-messages workflow in dry mode from the approved
+   brief, lead-review source decision, and `lead-sample.json`.
+2. Use `lead-sample.json` as the only lead sample source. Do not fetch new
+   prospects or invent richer row signals.
+3. Build proof inventory, token fill rules, token adherence, angle drafts,
+   kill/combine review, finalists, skeptical-prospect review, winner gate, and
+   a raw sendable selected winner.
+4. If `lead-filter.md` already exists, cite only basis rows that pass it. If it
+   does not exist yet, choose probable good-fit rows from `lead-sample.json` and
+   mark the final reconciliation as pending.
+5. Write `message-validation.md`. Do not write `message-review.md`; the parent
+   thread owns the joined review after both post-lead scouts finish.
+
+Return a concise final status with:
+
+- artifacts written
+- whether the full generate-messages prompt was loaded
+- lead sample basis used
+- selected winner summary
+- whether final reconciliation with `lead-filter.md` is complete or pending
+
+Quality bar:
+
+- Do not synthesize a lightweight message from general knowledge. The artifact
+  must prove the full generate-messages workflow ran.
+- Message generation can start before `lead-filter.md`, but message review
+  cannot start until the parent verifies the selected basis rows still pass the
+  final filter.

package/agents/registry.json

@@ -4,6 +4,7 @@
     {
       "id": "linkedin-engagement",
       "name": "source-scout-linkedin-engagement",
+      "kind": "source-scout",
       "promptFile": "source-scout-linkedin-engagement.md",
       "displayName": "LinkedIn Engagement Scout",
       "provider": "signal-discovery",
@@ -52,6 +53,7 @@
     {
       "id": "sales-nav",
       "name": "source-scout-sales-nav",
+      "kind": "source-scout",
       "promptFile": "source-scout-sales-nav.md",
       "displayName": "Sales Nav Scout",
       "provider": "sales-nav",
@@ -100,6 +102,7 @@
     {
       "id": "prospeo-contact",
       "name": "source-scout-prospeo-contact",
+      "kind": "source-scout",
       "promptFile": "source-scout-prospeo-contact.md",
       "displayName": "Prospeo Contact Scout",
       "provider": "prospeo",
@@ -145,6 +148,87 @@
           "mcp__sellable__search_prospeo"
         ]
       }
+    },
+    {
+      "id": "filter-leads",
+      "name": "post-find-leads-filter-scout",
+      "kind": "post-find-leads-scout",
+      "promptFile": "post-find-leads-filter-scout.md",
+      "displayName": "Post-Lead Filter Scout",
+      "target": "filter-leads",
+      "inputs": ["brief.md", "lead-review.md", "lead-sample.json"],
+      "producesArtifacts": ["lead-filter.md"],
+      "optionalProducesArtifacts": ["rubric.json"],
+      "ownership": "lead quality, false-positive patterns, keep/exclude rules, ability-to-pay checks, and production rubric translation only",
+      "codex": {
+        "description": "Sellable post-find-leads scout for lead filtering and rubric generation after source approval.",
+        "model": "gpt-5.5",
+        "modelReasoningEffort": "high",
+        "sandboxMode": "workspace-write",
+        "nicknameCandidates": [
+          "Lead Filter Scout",
+          "Filter Scout",
+          "Rubric Scout"
+        ]
+      },
+      "claude": {
+        "description": "Use proactively as a background Sellable post-find-leads scout after lead source approval to produce lead-filter.md and rubric.json from brief.md, lead-review.md, and lead-sample.json.",
+        "model": "inherit",
+        "background": true,
+        "maxTurns": 8,
+        "color": "yellow",
+        "tools": [
+          "Read",
+          "Write",
+          "Edit",
+          "Grep",
+          "Glob",
+          "mcp__sellable__get_subskill_prompt",
+          "mcp__sellable__get_subskill_asset"
+        ]
+      }
+    },
+    {
+      "id": "message-generation",
+      "name": "post-find-leads-message-scout",
+      "kind": "post-find-leads-scout",
+      "promptFile": "post-find-leads-message-scout.md",
+      "displayName": "Post-Lead Message Scout",
+      "target": "generate-messages",
+      "inputs": ["brief.md", "lead-review.md", "lead-sample.json"],
+      "producesArtifacts": ["message-validation.md"],
+      "optionalProducesArtifacts": [
+        "message-prep.md",
+        "message-candidate-drafts.md"
+      ],
+      "ownership": "proof inventory, token strategy, angle drafting, skeptical-prospect review, and selected winner only",
+      "codex": {
+        "description": "Sellable post-find-leads scout for dry-mode message generation after source approval.",
+        "model": "gpt-5.5",
+        "modelReasoningEffort": "high",
+        "sandboxMode": "workspace-write",
+        "nicknameCandidates": [
+          "Message Scout",
+          "Message Generation Scout",
+          "Copy Scout"
+        ]
+      },
+      "claude": {
+        "description": "Use proactively as a background Sellable post-find-leads scout after lead source approval to run dry-mode message generation from brief.md, lead-review.md, and lead-sample.json.",
+        "model": "inherit",
+        "background": true,
+        "maxTurns": 10,
+        "color": "magenta",
+        "tools": [
+          "Read",
+          "Write",
+          "Edit",
+          "Grep",
+          "Glob",
+          "mcp__sellable__get_subskill_prompt",
+          "mcp__sellable__get_subskill_asset"
+        ]
+      }
     }
   ]
 }

package/bin/sellable-install.mjs

@@ -467,6 +467,7 @@ const CREATE_CAMPAIGN_ALLOWED_TOOLS = [
   "mcp__sellable__search_subskill_prompts",
   "mcp__sellable__get_provider_prompt",
   "mcp__sellable__get_source_scout_registry",
+  "mcp__sellable__get_post_find_leads_scout_registry",
   "mcp__sellable__get_message_prompt",
   "mcp__sellable__get_active_workspace",
   "mcp__sellable__list_senders",
@@ -662,14 +663,22 @@ Treat host capabilities as concrete functions, not prose conventions:
   and continue chunks until \`hasMore\` is false.
 - \`load_source_scout_registry\`: call
   \`mcp__sellable__get_source_scout_registry({})\` before any scout dispatch.
+- \`load_post_find_leads_scout_registry\`: call
+  \`mcp__sellable__get_post_find_leads_scout_registry({})\` after source
+  approval and before dispatching the post-lead filter/message scouts.
 - \`launch_source_scout\`: Claude Code uses \`Task\` with \`subagent_type\` equal to
   the registry \`name\`; Codex uses named custom agents such as
   \`source-scout-linkedin-engagement\`, \`source-scout-sales-nav\`, and
   \`source-scout-prospeo-contact\` when subagents are available.
+- \`launch_post_find_leads_scout\`: Claude Code uses \`Task\` with
+  \`subagent_type\` equal to the returned post-lead registry \`name\`; Codex
+  uses the returned custom agents such as \`post-find-leads-filter-scout\` and
+  \`post-find-leads-message-scout\` when subagents are available.
 
 If a required interactive host function is missing, stop and explain the
 Sellable install/reload problem. Do not silently simulate structured choices,
-subprompt loading, or source-scout dispatch with local scripts.
+subprompt loading, source-scout dispatch, or post-lead scout dispatch with local
+scripts.
 
 Never narrate local draft housekeeping to the user. If you create directories,
 save drafts, write artifacts, or persist intermediate state, translate it into
@@ -1143,7 +1152,7 @@ function agentTemplateRoot() {
   }
 
   throw new Error(
-    `Sellable source scout agent templates missing. Expected ${join(
+    `Sellable custom agent templates missing. Expected ${join(
       packagedRoot,
       "registry.json"
     )}`
@@ -1427,8 +1436,8 @@ config_file = ${quoteToml(join(home, "agents", agent.filename))}`
     logVerbose(
       `${C.grey}+ enable [features].default_mode_request_user_input in ${configPath}${C.reset}`
     );
-    logVerbose(`${C.grey}+ write Codex custom scout agents in ${home}/agents${C.reset}`);
-    logVerbose(`${C.grey}+ register Codex source scout agents in ${configPath}${C.reset}`);
+    logVerbose(`${C.grey}+ write Codex custom agents in ${home}/agents${C.reset}`);
+    logVerbose(`${C.grey}+ register Codex custom agents in ${configPath}${C.reset}`);
   }
 
   return {
@@ -1848,10 +1857,10 @@ function printNextSteps(installedHosts, authReused) {
   if (hasCodex) {
     console.log(`        ${C.green}✓${C.reset} Codex Desktop plugin installed`);
     console.log(`        ${C.green}✓${C.reset} Skills installed`);
-    console.log(`        ${C.green}✓${C.reset} Codex source scout agents installed`);
+    console.log(`        ${C.green}✓${C.reset} Codex custom agents installed`);
   }
   if (hasClaude) {
-    console.log(`        ${C.green}✓${C.reset} Claude source scout agents installed`);
+    console.log(`        ${C.green}✓${C.reset} Claude custom agents installed`);
   }
   if (authReused) {
     console.log(

package/package.json

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

package/skill-templates/create-campaign.md

@@ -12,6 +12,7 @@ allowed-tools:
   - mcp__sellable__search_subskill_prompts
   - mcp__sellable__get_provider_prompt
   - mcp__sellable__get_source_scout_registry
+  - mcp__sellable__get_post_find_leads_scout_registry
   - mcp__sellable__get_message_prompt
   - mcp__sellable__get_active_workspace
   - mcp__sellable__list_senders
@@ -114,6 +115,13 @@ copy, is the runtime source of truth. If the host runs them sequentially, do not
 claim they ran in parallel. In chat, call the downstream copy stage `message generation`;
 `message-validation.md` is only an internal proof artifact.
 
+After find-leads returns a lead source and the user approves it, use the same
+registry pattern for the two post-lead branches. The create-campaign-v2 subskill
+calls `get_post_find_leads_scout_registry`, then launches the returned
+filter-leads scout and message-generation scout together when real subagents are
+available. Message generation must not wait for the filter unless the host
+cannot run the two branches concurrently.
+
 Use rendered Markdown for user review surfaces, not fenced code blocks. Keep
 lines short, use indexed section labels and bullets, and translate internal
 sourcing terms into plain language.
@@ -190,14 +198,22 @@ Treat host capabilities as concrete functions, not prose conventions:
   and continue chunks until `hasMore` is false.
 - `load_source_scout_registry`: call
   `mcp__sellable__get_source_scout_registry({})` before any scout dispatch.
+- `load_post_find_leads_scout_registry`: call
+  `mcp__sellable__get_post_find_leads_scout_registry({})` after source
+  approval and before dispatching the post-lead filter/message scouts.
 - `launch_source_scout`: Claude Code uses `Task` with `subagent_type` equal to
   the registry `name`; Codex uses named custom agents such as
   `source-scout-linkedin-engagement`, `source-scout-sales-nav`, and
   `source-scout-prospeo-contact` when subagents are available.
+- `launch_post_find_leads_scout`: Claude Code uses `Task` with `subagent_type`
+  equal to the returned post-lead registry `name`; Codex uses the returned
+  custom agents such as `post-find-leads-filter-scout` and
+  `post-find-leads-message-scout` when subagents are available.
 
 If a required interactive host function is missing, stop and explain the
 Sellable install/reload problem. Do not silently simulate structured choices,
-subprompt loading, or source-scout dispatch with local scripts.
+subprompt loading, source-scout dispatch, or post-lead scout dispatch with local
+scripts.
 
 Never narrate local draft housekeeping to the user. If you create directories,
 save drafts, write artifacts, or persist intermediate state, translate it into