@sellable/mcp 0.1.205 → 0.1.207

package/skills/create-campaign/SKILL.md

@@ -203,7 +203,7 @@ 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
+    After scouting, ask for a second approval on Start Import. For
     LinkedIn engagement (`signal-discovery` internally), name how many
     recommended posts will be scraped and the target engager/source-candidate
     volume. N must be the smallest right-content post set that clears the source
@@ -253,20 +253,29 @@ scout those angles as independent branches when the host can actually do it:
 LinkedIn posts / people reacting or commenting (internal `signal-discovery`
 provider prompt), Sales Nav / title + company filters, and Prospeo Contact /
 domains, hiring filters, or broad verified-contact expansion when relevant. In
-Codex, explicitly spawn the named custom scouts
+Codex, source discovery is agent-first after the Find Buyers Plan approval. For
+the approved single source lane, explicitly spawn that returned named custom
+scout; for example, choosing LinkedIn posts should spawn
+`source-scout-linkedin-engagement` even when no comparison is needed. When
+multiple source angles are credible, 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
-comparison wording. In Claude Code, invoke the generated `source-scout-*`
-Task/Agent subagents for all credible lanes in one assistant message only when
-the current session lists those names. The installer writes them from the same
-canonical Sellable agent registry with explicit Sellable MCP tool allowlists.
+exposes those names; Codex does not infer subagent fan-out from generic wording.
+YOLO/autonomous mode counts as campaign-scoped permission to use Sellable source
+background agents. In Claude Code, invoke the generated `source-scout-*`
+Task/Agent subagent for the approved lane, or all credible lanes in one
+assistant message when comparison/fallback is needed, only when the current
+session lists those names. The installer writes them from the same canonical
+Sellable agent registry with explicit Sellable MCP tool allowlists.
 The create-campaign-v2 subskill calls `get_source_scout_registry` before
 dispatch so the current registry, not this copy, is the runtime source of truth.
-If the host runs them sequentially or the named agents are unavailable, do not
-claim they ran in parallel and do not surface install status to the customer. In
-chat, call the downstream copy stage `message generation`; message validation is
-only an internal approval proof.
+If the named source scout is unavailable, use a generic `gpt-5.5` high
+background agent when the host can spawn generic agents. Continue source
+discovery in the parent thread only when agent launch is impossible or the user
+explicitly says to continue inline. Do not claim a scout ran unless one did, and
+do not surface install status to the customer. In chat, call the downstream copy
+stage `message generation`; message validation is only an internal approval
+proof.
 
 For campaign-attached Signal Discovery sampling, promote/select the exact posts
 with `select_promising_posts` before `fetch_post_engagers` so the user can see
@@ -281,17 +290,17 @@ actually engaging and the source is viable.
 
     After confirmed source rows exist in the campaign table, use the same registry pattern for
 
-post-lead work, but do not load that registry or any deep filter/message prompt
+prospect setup 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
+vs skip filters immediately. Once the user answers, launch Message Drafting
 from the same campaign/table basis. If the user chooses filters, also launch the
-filter-leads scout, move to Filter Rules, save rubrics, then ask for filter
+Prospect Filters worker, move to Filter Rules, save rubrics, then ask for filter
 approval. After approval, move to Filter Leads and show `Filters saved + waiting
 for message approval` while the message recommendation is reviewed. If the user
 skips filters, move to Messages/message review. Enrichment/filtering and
 Generate Message cells wait for message 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
+prospect setup agents are absent, the main thread still orchestrates the same
 branches from compact MCP context.
 
 Use rendered Markdown for user review surfaces, not fenced code blocks. Keep
@@ -427,15 +436,15 @@ Treat host capabilities as concrete functions, not prose conventions:
   `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.
+  import and before dispatching Prospect Filters/Message Drafting.
 - `launch_source_scout`: Claude Code uses `Task` with `subagent_type` equal to
   the registry `name` only when the session lists those agents; 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` only when the session lists
-  those agents; Codex uses the returned custom agents such as
+  equal to the returned prospect-setup registry `name` only when the session
+  lists those agents; Codex uses the returned compatibility agents such as
   `post-find-leads-filter-scout` and `post-find-leads-message-scout` when
   subagents are available.
 
@@ -758,10 +767,23 @@ updates.
    copies of this file; packaged Claude Code and Codex runs must use the MCP
    asset loader so they share the same config.
 3. Follow that prompt and workflow config exactly.
-4. For message generation, use the `post-find-leads-message-scout` agent when
-   available. The worker and parent-thread fallback must load
+4. For message generation, keep the parent thread as a lean orchestrator and
+   use the `post-find-leads-message-scout` compatibility agent for Message
+   Drafting whenever the host exposes it
+   and the current host policy allows agent launch. The worker must load
    `mcp__sellable__get_subskill_prompt({ subskillName: "generate-messages" })`.
-   Do not use any alternate or examples-only message prompt. Message review requires Message Draft Builder output:
+   In Codex, YOLO/autonomous mode counts as campaign-scoped permission to use
+   Sellable background agents for pre-launch work. If the user has not enabled
+   YOLO and has not explicitly asked for background agents, subagents, parallel
+   agents, delegation, or a message/bg agent in this campaign, ask once for
+   permission before loading the long message prompt in the parent. If
+   permission is granted but the named custom agent is not
+   available, spawn a generic background agent with `model: "gpt-5.5"` and
+   `reasoning_effort: "xhigh"` using the same campaign/table basis. Do not
+   silently fall back to parent-thread message drafting; parent fallback is
+   allowed only when the user explicitly says to continue without a background
+   agent.
+   Do not use any alternate or examples-only message prompt. Message review requires Message Drafting output:
    do not draft from a checklist, local markdown artifact, or parent-thread
    intuition. Use campaign state, campaign brief content, selected source state, and
    initial campaign-table execution slice rows as the source of truth; do not read stale local

package/skills/create-campaign/context/learnings.md

@@ -4,7 +4,7 @@ This log captures what has worked in real campaigns.
 
 Entries should be short, specific, and based on observed outcomes.
 
-**Cross-skill learnings** that would help other skills (engage, create-post) should ALSO be written to `~/.sellable/insights/cross-skill.md` so the entire system learns.
+**Cross-skill learnings** that would help other skills (engage, create-post) should ALSO be written to `.sellable/insights/cross-skill.md` so the entire system learns.
 
 ## Log
 

package/skills/create-campaign/references/brief-template.md

@@ -41,8 +41,8 @@ Example: "In a 15-minute call, we will audit your top 10 accounts and show where
 - **Bridge to:** [How it connects to their pain]
 - **Avoid:** [Generic phrases to skip - "best-in-class", "industry-leading", etc.]
 - **Voice:** [Reference core memory / composed engage memory first. Use legacy writing memory only as fallback.]
-- **Outbound rules:** [Reference `~/.sellable/configs/writing/outbound.md` if loaded -- observation -> relevance -> ask]
-- **Proof boundaries:** [Reference `~/.sellable/configs/core/proof-ledger.md` and `~/.sellable/configs/core/wins-ledger.md` if loaded. Do not upgrade or invent claims.]
+- **Outbound rules:** [Reference `.sellable/configs/writing/outbound.md` if loaded -- observation -> relevance -> ask]
+- **Proof boundaries:** [Reference `.sellable/configs/core/proof-ledger.md` and `.sellable/configs/core/wins-ledger.md` if loaded. Do not upgrade or invent claims.]
 
 ## Do NOT Target
 

package/skills/create-campaign-brief/references/brief-template.md

@@ -15,7 +15,7 @@ assistant message directly from the `result.result` stream-json payload —
 it does not read a file off disk.
 
 If you find yourself emitting a TodoWrite step like "Write brief.md v1
-to disk" or "Save brief to ~/.sellable/..." — DELETE that step and return
+to disk" or "Save brief to .sellable/..." — DELETE that step and return
 the brief inline instead. The tools `Write`, `Edit`, and `Bash` are
 intentionally not in the Phase 83 harness allowlist; attempting them
 will cause a ToolSearch loop that deadlocks the turn.
@@ -37,7 +37,7 @@ offer is, why it should work, and what must be true before we launch. Do not
 prescribe message structure, opener order, or final copy here.]
 
 Draft path:
-`~/.sellable/create-campaign-brief/drafts/{workspace-slug}/{campaign-slug}/brief.md`
+`.sellable/create-campaign-brief/drafts/{workspace-slug}/{campaign-slug}/brief.md`
 
 ## Product
 

package/skills/create-campaign-brief/references/draft-lifecycle.md

@@ -2,7 +2,7 @@
 
 Phase 83 writes one Markdown file:
 
-`~/.sellable/create-campaign-brief/drafts/{workspace-slug}/{campaign-slug}/brief.md`
+`.sellable/create-campaign-brief/drafts/{workspace-slug}/{campaign-slug}/brief.md`
 
 ## Rules
 

package/skills/create-campaign-brief/references/examples/briefs/gelee.md

@@ -58,7 +58,7 @@ _Personalization: References their previous exit or current venture by name + th
 
 Hi {{first_name}}, let me know if i'm off, but {{seems_like_you}}.
 
-saw you in a few conversations around {{signal_topic}}, so hope this is relevant.
+saw you were active in some {{signal_topic}} conversations recently and figured this might be relevant.
 
 we work with about 30 exited founders right now (yc, techstars, sequoia backed) handling their entire linkedin with ai + human review.
 
@@ -131,7 +131,7 @@ is this worth a look or should i send a short overview?
 
 Hi sarah, let me know if i'm off, but seems like you started building something new in the pharma space after the Benchling exit.
 
-saw you in a few conversations around founder-led growth, so hope this is relevant.
+saw you were active in some founder-led growth conversations recently and figured this might be relevant.
 
 we work with about 30 exited founders right now (yc, techstars, sequoia backed) handling their entire linkedin with ai + human review.
 

package/skills/create-campaign-brief/references/examples/briefs/superpower.md

@@ -35,82 +35,70 @@ Signal-based outreach using peer-to-peer tone. Positioning Superpower as early d
 
 **VARIANT 1 — Subject: jeff/{{first name}} intro**
 
-hey {{first name}},
+hey {{first name}}, saw you were active around some {{topic}} stuff recently and figured this might actually be relevant
 
-saw you in a few conversations around {{topic}}, so hope this is relevant.
+any chance you're exploring early detection or preventive health programs at {{company}}?
 
-if preventive health is anywhere near the benefits plan at {{company}}, Superpower may be worth a look.
+we screen for 1,000+ conditions from a single blood draw and surface risks before they ever become claims.
 
-it screens for 1,000+ conditions from a single blood draw and surfaces risks before they become claims.
+basically your team gets to see what's coming instead of just reacting to it
 
-basically your team gets to see what's coming instead of only reacting to it.
-
-should i send over the short version?
+can I send over some more info?
 
 **VARIANT 2 — Subject: jeff/{{first name}} intro**
 
-hey {{first name}},
-
-saw you in a few conversations around {{topic}}, so hope this is relevant.
+hey {{first name}}. saw you were active in some {{topic}} conversations recently and wanted to run something by you
 
 most annual physicals test 15 biomarkers max.
 
-Superpower looks at 100+ biomarkers and screens for 1,000+ conditions from one draw.
+there's over 100 that actually matter and the gap between those two numbers is where the expensive claims tend to sit
 
-teams like Lyft and Notion are already exploring this at $199 a person.
+teams like Lyft and Notion are already exploring this. one draw, 1,000+ conditions, $199 a person.
 
-if preventive health is nowhere near your lane, ignore me.
+if your claims costs have been going up and you're not sure where it's coming from... that gap may be a good place to start looking
 
-should i send over the short version?
+can I send over some more info?
 
 ## Examples
 
 **Example 1 (Variant 1 — self-insured health plans):**
 Subject: susana/prab intro
 
-hey susana,
-
-saw you in a few conversations around self-insured health plans, so hope this is relevant.
+hey susana, saw you were active around self-insured health plan content recently and figured this might actually be relevant
 
-if preventive health is anywhere near the benefits plan at Quantum Health, Superpower may be worth a look.
+any chance you're exploring preventive health programs at Quantum Health?
 
-it screens for 1,000+ conditions from a single blood draw and surfaces risks before they become claims.
+we screen for 1,000+ conditions from a single blood draw and surface risks before they ever become claims.
 
-basically your team gets to see what's coming instead of only reacting to it.
+basically your team gets to see what's coming instead of just reacting to it
 
-should i send over the short version?
+can I send over some more info?
 
 **Example 2 (Variant 2 — employee wellness programs):**
 Subject: lisa/prab intro
 
-hey lisa,
-
-saw you in a few conversations around employee wellness programs, so hope this is relevant.
+hey lisa. saw you were active in some employee wellness programs conversations recently and wanted to run something by you
 
 most annual physicals test 15 biomarkers max.
 
-Superpower looks at 100+ biomarkers and screens for 1,000+ conditions from one draw.
-
-teams like Lyft and Notion are already exploring this at $199 a person.
+there's over 100 that actually matter and the gap is driving the surprise expensive claims every year
 
-if preventive health is nowhere near your lane, ignore me.
+teams like Lyft and Notion are already exploring this. one test, 1,000+ conditions, $199 a person
 
-should i send over the short version?
+can I send over some more info?
 
 **Example 3 (Variant 1 — employee wellness programs):**
 Subject: princess/prab intro
 
-hey princess,
-
-saw you in a few conversations around employee wellness programs, so hope this is relevant.
+hey princess, saw you were active around employee wellness programs content recently and figured this might actually be relevant
 
-if preventive health is anywhere near the benefits plan at Marriott, Superpower may be worth a look.
+any chance you're exploring preventive health programs at Marriott?
 
-it screens for 1,000+ conditions from a single blood draw and surfaces risks before they become claims.
+we screen for 1,000+ conditions from a single blood draw and surface risks before they ever become claims.
 
-basically your team gets to see what's coming instead of only reacting to it.
+basically your team gets to see what's coming instead of just reacting to it
 
-should i send over the short version?
+can I send over some more info?
 
 ## Social Proof
 
@@ -124,8 +112,7 @@ Teams like Lyft and Notion are exploring Superpower's early detection platform.
 - **ICP filtering:** All prospects filtered against ICP criteria before entering send queue
 - **Positioning:** Early detection tool for claims prevention, not a wellness benefit
 - **Tone:** All lowercase, casual, peer-to-peer - building relationship before asking
-- **Two approved variants:** Testing a low-certainty signal bridge vs. proof-led
-  benefits mechanism
+- **Two approved variants:** Testing different hooks (exploratory vs. problem-aware)
 
 ### Rubric Markdown
 
@@ -225,8 +212,8 @@ Teams like Lyft and Notion are already using early detection screening. One bloo
 
 **Subject: Prab/{{first_name}} intro**
 
-Hey {{first_name}},
+Hey {{first_name}}, not sure if you've looked into this but felt it may be relevant to your work.
 
-hope this is relevant if preventive health is anywhere near the benefits plan at {{company}}.
+have you ever looked into early detection or preventive health programs for {{company}}?
 
-Superpower screens for 1,000+ conditions from a single blood draw and surfaces risks before they become claims.
+we screen for 1,000+ conditions from a single blood draw and surface risks before they ever become claims.

package/skills/create-campaign-brief/references/phase75-active-runtime-message-pack.md

@@ -14,8 +14,7 @@ Included as primary gold examples:
 - `Galley`
 - `Clover`
 - `Persona`
-- `Superpower` — domain-language reference only; use the cleaned low-certainty
-  opener, not retired engagement-source phrasing
+- `Superpower`
 
 Not included in runtime inspiration:
 
@@ -34,9 +33,6 @@ Not included in runtime inspiration:
 
 - Feed only endorsed examples into generation.
 - Keep bad lines only if they are explicitly labeled `BAD` and paired with a `BETTER` version.
-- Treat sellable.dev, Hey Digital, Persona, Galley, and Clover as the primary
-  line-level quality anchors. Superpower is useful for benefits/healthcare
-  mechanism language, but it must not outrank those examples on opener style.
 - Default to one approved message in the generated brief unless the ICP is genuinely broad.
 - A/B CTA is optional. Use it only when the second option is truly strong.
 - If there is a great low-friction proof asset or case study, that is often the best Option B.
@@ -217,21 +213,22 @@ Why included:
 
 - simple language in a hard domain
 - useful plain-language healthcare constraint example
-- why it works: it uses a low-certainty signal bridge, explains the mechanism
-  in plain language, and keeps the ask tiny instead of forcing a call
+- why it works: it asks about the buyer's existing benefits priority, explains
+  the mechanism in plain language, and keeps the ask tiny instead of forcing a
+  call
 
 ```md
 Hey {{first_name}},
 
-saw you in a few conversations around {{topic}}, so hope this is relevant.
+not sure if you've looked into this but felt it may be relevant to your work.
 
-if preventive health is anywhere near the benefits plan at {{company}}, Superpower may be worth a look.
+have you ever looked into early detection or preventive health programs for {{company}}?
 
-it screens for 1,000+ conditions from a single blood draw and surfaces risks before they become claims.
+we screen for 1,000+ conditions from a single blood draw and surface risks before they ever become claims.
 
-basically your team gets to see what's coming instead of only reacting to it.
+basically your team gets to see what's coming instead of just reacting to it
 
-should i send over the short version?
+can I send over some more info?
 ```
 
 Locked production variant from the same Superpower campaign: