@sellable/mcp 0.1.204 → 0.1.206

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:

package/skills/create-campaign-v2/SKILL.md

@@ -38,7 +38,7 @@ Legacy commit-gate/atomic-mint is only in create-campaign-v2-validation.
 3. Research the client/company and current offer enough to draft a concrete brief.
 4. Create the watchable campaign shell with `create_campaign` and the v1 brief.
 5. Surface the direct watch link once before brief approval.
-6. Choose and approve the lead source.
+6. Approve the Find Buyers Plan, then approve Start Import.
 7. Materialize the approved source list and confirm 15 campaign-table rows for
    filter/message setup; do not present that as source sampling.
 8. Ask whether to use filters or skip them.
@@ -143,7 +143,7 @@ Use the host-native structured question gate (`request_user_input` or
 AskUserQuestion) only for bounded choices:
 
 - target, offer, credibility, and prospect-source setup choices after research
-- source approval or source revision
+- Find Buyers Plan, Start Import, or source revision
 - use filters vs skip filters
 - approve message vs revise message
 - sender/sequence/launch choices at Settings
@@ -230,7 +230,7 @@ move to Prospeo. Prospeo is the terminal fallback;
 if it also falls below 10%, tighten the ICP/source direction instead of
 inventing another provider.
 
-After scouting, show a second approval gate for the concrete source action.
+After scouting, show a second approval gate for Start Import.
 For LinkedIn engagement (`signal-discovery` internally), use plain language:
 selected posts, people we can check, likely prospects, what the first
 review will inspect, cleanup risk, and fallback. Label the approval like
@@ -241,7 +241,7 @@ Prospeo, name the specific search/import path and source lead count. Do not call
 `import_leads` or `confirm_lead_list` until this gate is approved.
 
 For Sales Nav and Prospeo, do not ask to import only the internal 15-row
-campaign-table execution slice at the source-action gate. First-page samples are
+campaign-table execution slice at the Start Import gate. First-page samples are
 source math: sampled fit, projected good-fit prospects, and whether the path
 clears the target. Once it clears, ask approval for a source list with
 `targetLeadCount` around 1,000 contacts by default. After that,
@@ -249,8 +249,8 @@ clears the target. Once it clears, ask approval for a source list with
 confirmed source rows into the campaign table and returns the initial
 campaign-table execution slice row ids for filter and message setup.
 
-After the user approves this concrete source-action gate, do not show the
-Source Recommendation again or ask another source approval question.
+After the user approves this Start Import gate, do not show the
+Source Recommendation again or ask another Start Import question.
 Acknowledge once, then call `import_leads` immediately with the approved source
 math. For Sales Nav/Prospeo, pass `targetLeadCount` as the approved source-list
 export count, not the campaign execution-slice size. For Signal Discovery, pass
@@ -261,7 +261,7 @@ After `import_leads`, poll `wait_for_lead_list_ready` until ready, failed, or
 cancelled. Rows appearing is not enough for `confirm_lead_list`; use
 `allowPartialSourceList: true` only when the user explicitly asks to continue early.
 
-For LinkedIn engagement, the source-action approval uses `## Source
+For LinkedIn engagement, the Start Import approval uses `## Source
 Recommendation`, plain language, selected posts, people to check, likely
 prospects, cleanup risk, fallback, and the first 15-lead review.
 
@@ -279,21 +279,21 @@ Supplied profile CSVs, company/domain CSVs, pasted domains, and existing
 Sellable lead lists are supported, but keep provider mechanics out of the first
 customer-facing source-choice labels.
 
-## Post-Lead Workstreams
+## Prospect Setup Workstreams
 
 After `confirm_lead_list` copies a non-empty confirmed source into the campaign
 and records the compact review batch, ask the filter-choice question
 immediately. Do not call
 `get_post_find_leads_scout_registry`, load filter/message subskill prompts, or
-spawn post-lead workers before that question. The only customer-facing work
+spawn Prospect Filters / Message Drafting before that question. The only customer-facing work
 before the question should be a short campaign setup summary and the choice:
 add filters, skip filters, or revise source. Do not include another watch link
 in this summary; the existing app view updates through campaign state.
 
-If the user chooses filters, load the post-lead registry/reference needed for
-filtering and start the Lead Fit Builder. Also start the Message Draft Builder
-from the same campaign/table basis once filter-choice is known. If filters are
-skipped, move the watched app to Messages and run Message Draft Builder there.
+If the user chooses filters, load the prospect-setup registry/reference needed
+for filtering and start Prospect Filters. Also start Message Drafting from the
+same campaign/table basis once filter-choice is known. If filters are skipped,
+move the watched app to Messages and run Message Drafting there.
 Debug markdown/json artifacts are optional only.
 
 When the user chooses filters, immediately call
@@ -303,23 +303,29 @@ visible so the user can approve saved criteria. Only after approval should
 `update_campaign` move to `apply-icp-rubric` / Filter Leads and show
 `Filters saved + waiting for message approval` until the template is approved. Do not
 queue enrichment/filtering/Generate Message cells until message approval. Tell
-the user the Message Draft Builder is preparing the template in the background.
+the user Message Drafting is preparing the template in the background.
 
-Lead Fit Builder persists production rubrics with `save_rubrics` when filters
+Prospect Filters persists production rubrics with `save_rubrics` when filters
 are enabled. It must not require `brief.md`, `lead-review.md`, or
 `lead-sample.json`.
 
-Run `post-find-leads-message-scout` as the background Message Draft Builder
-whenever the host exposes it. It must load:
+Run compatibility agent `post-find-leads-message-scout` as Message Drafting
+when allowed. Keep the long prompt and refs there.
+
+Codex: YOLO counts as campaign bg-agent permission. If no permission, ask once
+after filter choice. Use generic `gpt-5.5` / `xhigh` if needed. Never draft in
+parent silently.
+
+Load:
 
 ```text
 get_subskill_prompt({ subskillName: "generate-messages" })
 ```
 
-Do not use any alternate or examples-only message prompt. If the host cannot
-launch the agent, the parent fallback must run the same full prompt from live
-campaign state. Do not render message
-review until `messageDraftRecommendation` proves current campaign/table basis.
+Do not use any alternate or examples-only message prompt. Do not render message
+review until `messageDraftRecommendation` proves current campaign/table basis
+and shows whether it came from a background branch or an explicitly approved
+inline fallback.
 
 ## Hard Gates
 

package/skills/create-campaign-v2/SOUL.md

@@ -256,8 +256,7 @@ Customer-facing source-plan copy must avoid "lane", "provider",
 "pilot volume", "workflow pain", and "ICP". Use "buyers" for the target market,
 "people to check" for raw reactions/comments, "prospects" after fit looks
 usable, and "leads" for campaign rows. Second, after the source evidence exists, show
-counts, samples, fit math, cleanup risk, and ask for source approval before
-import.
+counts, samples, fit math, cleanup risk, and ask for Start Import approval.
 
 For LinkedIn engagement, the second gate is not "approve source" in the abstract.
 It is a concrete scrape approval: show a compact `## Source Recommendation`
@@ -301,14 +300,15 @@ scout loads only its matching provider prompt. If source work is sequential,
 keep the output numeric but do not claim the source scout was parallel or
 surface install status to the customer.
 
-For post-lead work, call `get_post_find_leads_scout_registry` after
+For prospect setup work, call `get_post_find_leads_scout_registry` after
 the user chooses filters, not before the filter-choice question. After
 `confirm_lead_list` copies source rows and records the first review/process
 sample, ask add-filters vs skip-filters
-immediately. Once the user answers, start `post-find-leads-message-scout` /
-message generation from the same campaign/table basis. If the user chooses
-filters, also start `post-find-leads-filter-scout`, move the browser to Filter
-Rules, save rubrics, then ask for filter approval. After approval, keep the
+immediately. Once the user answers, start Message Drafting via
+`post-find-leads-message-scout` from the same campaign/table basis. If the user
+chooses filters, also start Prospect Filters via
+`post-find-leads-filter-scout`, move the browser to Filter Rules, save rubrics,
+then ask for filter approval. After approval, keep the
 browser on Filter Leads and show `Filters saved + waiting for message approval`
 while the message recommendation is reviewed. If the user skips filters, move
 the browser to Messages/message review. The join gate is saved-filter approval or
@@ -316,8 +316,11 @@ a resolved skip-filter choice, plus a message recommendation grounded in the sam
 campaign/table basis. Enrichment, filtering, and Generate Message cells wait for
 template approval on the Use Template path.
 
-Only promise parallel post-lead work when parallel work actually started. If the
-host cannot or should not launch background branches, say the real sequence:
+Only promise parallel prospect setup work when parallel work actually started. If the
+host cannot or should not launch background branches, do not silently move the
+long message prompt into the parent thread. In Codex, ask once for permission to
+use background Message Drafting. If the user declines or asks to continue
+without background agents, say the real sequence:
 
 ```text
 I’ll tighten the filter first, then run message generation from the same sample.