@sellable/mcp 0.1.157 → 0.1.159

package/skills/create-campaign-v2/references/approval-gate-framing.md

@@ -143,7 +143,12 @@ will use, what the first message says, and what happens if the user approves.
 Keep implementation details available, but move them below the customer-facing
 summary.
 
-1. **brief** — `brief.md` thesis, product, ICP, offer
+1. **brief** — `brief.md` thesis, product, ICP, offer. Label major strategic
+   choices with compact provenance tags when known: `[from you]`,
+   `[from LinkedIn]`, `[from website]`, `[from case study]`, or
+   `[Sellable recommendation]`. Include this correction affordance before
+   approval: "This is based on what I found. If your site or LinkedIn is stale,
+   tell me what to update before I build the lead list." Ask "Do you agree with this researched campaign direction?"
 2. **lead sample** — first 5-10 rows from `lead-sample.json` rendered as
    `Name / Title / Company` lines, plus the `lead-review.md` pass-rate
    and supplied-source framing when `lead-source-intake.json` exists:
@@ -169,6 +174,12 @@ review in the pre-mint approval packet. Those are configured and reviewed after
 the campaign is created in the autonomous tail. The pre-mint packet approves
 only the brief, lead source, lead filter/rubric, and first message direction.
 
+In the first strategic brief before leads exist, do not show quoted outreach
+copy or speculative first-message examples. If a message-shape hint is useful,
+keep it as non-final bullets and label it: "This is not the message yet; I will
+write real examples after we find and filter leads." Real rendered message proof
+belongs in message review after leads and sample rows exist.
+
 Do not include or summarize post-accept DMs, connection-accepted follow-ups,
 day-2 / day-7 follow-ups, second touches, reply branches, or any other
 sequence-shaped copy in `message-review.md` or `approval-packet.md`. If

package/skills/create-campaign-v2/references/filter-leads.md

@@ -12,6 +12,32 @@ production rubrics, and protect the user from replies they would not want to
 take. It should not re-run sourcing, create a second source plan, or build a
 large scoring framework.
 
+## Source Scouting Framing
+
+Use "source scouting" for the pre-import source decision. Do not say "testing
+sources" in first-time-facing copy. Explain the decision the user is approving:
+which source is being tried, why it was recommended from the research, the
+precision/scale tradeoff, what evidence quality it should prove, and what safe
+bounded pilot volume looks like.
+
+Source-scouting approval authorizes scouting/search only. It does not approve
+lead import, filtering, messaging, sequence, sender selection, or sending.
+Keep detailed LinkedIn account-safety reassurance for the sender/settings step.
+
+## Filter Approval Framing
+
+Before asking the user to approve saved filters, explain the value in plain
+language:
+
+- These rules prevent wasted sends before I score/import the list.
+- They protect limited outbound capacity by blocking bad-fit rows early.
+- Recommended because of the researched ICP, source sample, and repeated
+  false-positive patterns.
+- Show one pass example and one block example when available.
+
+Make the approval object explicit: the user is approving filter rules, not
+message drafts, not sender connection, and not campaign launch.
+
 ## Inputs
 
 Use only live campaign inputs supplied by the parent thread or scoped MCP tools:

package/skills/create-campaign-v2/references/final-handoff-contract.md

@@ -35,6 +35,9 @@ order (all before waiting for the user):
 4. Explain sender setup and Slack in normal customer language: Sellable needs a
    connected LinkedIn sender for launch, and Slack reply review matters because
    replies and approvals need a channel the team will monitor.
+   Before asking the user to connect or select a sender, include this sender
+   safety contract: lead research and filtering already happened outside the
+   user's LinkedIn account; the connected sender is not used for source scouting, scraping, or filtering; this account is only used for approved sending after final launch; final launch approval still happens at the Start step.
 5. If no connected sender exists, surface the campaign Settings link
    `/campaign-builder/{campaignId}/settings?mode=claude`, tell the user to
    connect a sender there, and STOP. Do not attach sequence and do not start.
@@ -58,6 +61,12 @@ currentStep: "sequence" })` to attach the sender via the v3 senders route and
     "what to do next" sentence.
 11. Ask the final launch greenlight with the structured question function:
     Start campaign, Review campaign first, or Pause here.
+    Before the Start choice, summarize launch confidence separately from quality
+    confidence: quality confidence means sample messages, prospect angle,
+    company/person match, token/person variables, and reputation-burn risk were
+    checked; launch confidence means sender, sequence, and final Start are ready.
+     Explain what happens after Start: approved messages begin sending according to the sequence, replies and meetings follow the connected settings, the user can monitor and pause, and no hidden extra approval disappears after
+    clicking Start.
 12. STOP unless the user explicitly chooses Start campaign. Do not call
     `start_campaign` from Step 16 itself.
 
@@ -68,7 +77,12 @@ The final handoff must answer five customer questions in plain language:
   sequence after a sender is attached)
 - whether the next UI step is Settings, Sequence, or Send
 - why the selected LinkedIn sender and Slack reply review matter before launch
+- that the connected LinkedIn account is not used for lead research, source
+  scouting, scraping, or filtering
+- that this account is only used for approved sending after final launch
 - what clicking Start does (approves/starts the campaign send path)
+- the difference between quality confidence and launch confidence
+- what happens after Start: approved messages begin sending according to the sequence, replies and meetings follow connected settings, the campaign can be monitored and paused, and no hidden approval disappears
 - how to revise (reply with what to change, or use the campaign UI)
 - current launch status and what the final Start action does
 
@@ -188,6 +202,7 @@ true:
 - Sender is missing or disabled.
 - `attach_recommended_sequence` never succeeded (no sequence bound to the
   campaign).
+- No approved generated message exists in the campaign table.
 
 A refusal is NOT an escalation in the ladder sense — it's a pre-check
 failure. Surface the specific reason so the user can fix it and say

package/skills/create-campaign-v2/references/sample-validation-loop.md

@@ -13,6 +13,32 @@ judge this campaign?" Message generation starts earlier: the first row that
 passes filters is enough to begin observing or queueing Generate Message for
 that passing row.
 
+## Sample Count Summary
+
+When showing sample or message-review status, include concrete count math:
+
+- `{checked} leads checked`
+- `{passed} passed and have draft messages`
+- `{blocked} blocked before sending`
+- `full list remains paused until approval`
+
+Use dynamic counts from campaign/table state when available. If counts are not
+available yet, use the generic pattern: "I am checking the bounded sample now;
+passed rows get draft messages, blocked rows stop before sending, and the full
+list remains paused until approval."
+
+When the UI/chat action would otherwise read like "Approve 11", make it precise:
+approve these 11 draft rows for the next review step. This does not approve the
+full campaign launch and does not approve the user's LinkedIn account for
+sending yet; approval here does not approve the full campaign launch.
+
+## Message QA Receipt
+
+Before asking for sample/message approval, include this compact receipt:
+"Before you approve, I checked: tokens resolved, company/person match, proof claim, prospect angle, language/tone when known, and obvious bad fits."
+
+Also include the reputation guardrail: weak personalization can burn the sender's reputation, so this approval is only for the reviewed sample/message direction. The full list remains paused until approval, and final launch happens later. Use the plain heuristic: "Would I take this call?"
+
 If the answer is yes, proceed to Step 15 messaging for the initial campaign rows. If
 the answer is no, diagnose whether the brief is wrong or the list is wrong,
 and either revise brief autonomously OR escalate to the user — never

package/skills/create-campaign-v2/references/watch-link-handoff.md

@@ -34,15 +34,18 @@ Example skeleton:
 
 ```text
 I created the campaign shell with the brief already in it.
-You can watch the lead source, filters, and messages fill in from here.
+I am creating the campaign through this chat. Open this link if you want to
+watch the work being done and audit what changes.
 
-I’ll pause at the next approval gate before sourcing.
+You can still ask me to change anything here. I’ll pause at the next approval
+gate before sourcing.
 
 Watch link: [Open campaign]({watchUrl})
 
-Click that link to watch the campaign. If it opens in an in-app browser and asks
-you to sign in, open the same link in your regular browser so you can watch
-real-time updates from your signed-in session.
+Click that link to watch the campaign. The app is for inspection; this chat is
+where you direct the campaign. If it opens in an in-app browser and asks you to
+sign in, open the same link in your regular browser so you can watch real-time
+updates from your signed-in session.
 
 Command-Enter or click that link to watch it in Sellable.
 
@@ -65,6 +68,8 @@ clear:
 
 - the campaign shell exists now
 - the brief is already visible in the campaign
+- chat is where the user directs changes
+- the app link is for watching and auditing live work
 - import, sequence, and start are still blocked
 
 ## Browser Choice

package/skills/providers/signal-discovery.md

@@ -425,9 +425,11 @@ recommendation, estimate source capacity from real sample math:
 
 Then select the smallest right-content post set that plausibly hits the source
 target. Do not scrape every promoted sample post by default; promoted sampling
-state and final scrape plan are separate. If the math says the warm post lane
-only supports a smaller first batch, say that and name the Sales Nav or Prospeo
-scale fallback rather than padding the selection with noisy posts. If the
+state and final scrape plan are separate. If one 1,200+ engager post clears a
+~1,000-engager target, recommend scraping that one post rather than the 3-post
+sample set. If the math says the warm post lane only supports a smaller first
+batch, say that and name the Sales Nav or Prospeo scale fallback rather than
+padding the selection with noisy posts. If the
 sampled/projected headline-fit rate is below 10%, do not call
 `import_leads`; move to Sales Nav recent activity.