@sellable/mcp 0.1.952 → 0.1.953

package/dist/tools/campaigns.d.ts

@@ -141,6 +141,7 @@ export interface CreateCampaignInput {
     offerPositioning?: unknown;
     campaignBrief?: string;
     messageGenerationMode?: "template" | "ai-generated";
+    messageApproach?: "conversation" | "message_test";
     currentStep?: string | null;
     watchNarration?: unknown;
     leadSourceType?: string | null;
@@ -167,6 +168,7 @@ export interface UpdateCampaignInput {
     interactionMode?: InteractionMode;
     enableICPFilters?: boolean | null;
     useMessagingTemplate?: boolean | null;
+    messageApproach?: "conversation" | "message_test";
     autoApproveFollowups?: boolean;
     enableFollowUps?: boolean;
     senderIds?: string[];
@@ -251,6 +253,7 @@ export declare const campaignToolDefinitions: ({
             offerPositioning?: undefined;
             campaignBrief?: undefined;
             messageGenerationMode?: undefined;
+            messageApproach?: undefined;
             currentStep?: undefined;
             watchNarration?: undefined;
             leadSourceType?: undefined;
@@ -300,6 +303,7 @@ export declare const campaignToolDefinitions: ({
             offerPositioning?: undefined;
             campaignBrief?: undefined;
             messageGenerationMode?: undefined;
+            messageApproach?: undefined;
             currentStep?: undefined;
             watchNarration?: undefined;
             leadSourceType?: undefined;
@@ -351,6 +355,7 @@ export declare const campaignToolDefinitions: ({
             offerPositioning?: undefined;
             campaignBrief?: undefined;
             messageGenerationMode?: undefined;
+            messageApproach?: undefined;
             currentStep?: undefined;
             watchNarration?: undefined;
             leadSourceType?: undefined;
@@ -398,6 +403,7 @@ export declare const campaignToolDefinitions: ({
             offerPositioning?: undefined;
             campaignBrief?: undefined;
             messageGenerationMode?: undefined;
+            messageApproach?: undefined;
             currentStep?: undefined;
             watchNarration?: undefined;
             leadSourceType?: undefined;
@@ -445,6 +451,7 @@ export declare const campaignToolDefinitions: ({
             offerPositioning?: undefined;
             campaignBrief?: undefined;
             messageGenerationMode?: undefined;
+            messageApproach?: undefined;
             currentStep?: undefined;
             watchNarration?: undefined;
             leadSourceType?: undefined;
@@ -535,6 +542,7 @@ export declare const campaignToolDefinitions: ({
             offerPositioning?: undefined;
             campaignBrief?: undefined;
             messageGenerationMode?: undefined;
+            messageApproach?: undefined;
             currentStep?: undefined;
             watchNarration?: undefined;
             leadSourceType?: undefined;
@@ -593,6 +601,11 @@ export declare const campaignToolDefinitions: ({
                 enum: string[];
                 description: string;
             };
+            messageApproach: {
+                type: string;
+                enum: string[];
+                description: string;
+            };
             currentStep: {
                 type: string[];
                 description: string;
@@ -971,6 +984,11 @@ export declare const campaignToolDefinitions: ({
                 type: string[];
                 description: string;
             };
+            messageApproach: {
+                type: string;
+                enum: string[];
+                description: string;
+            };
             autoApproveFollowups: {
                 type: string;
                 description: string;
@@ -1038,6 +1056,7 @@ export declare const campaignToolDefinitions: ({
             offerPositioning?: undefined;
             campaignBrief?: undefined;
             messageGenerationMode?: undefined;
+            messageApproach?: undefined;
             currentStep?: undefined;
             watchNarration?: undefined;
             leadSourceType?: undefined;
@@ -1088,6 +1107,7 @@ export declare const campaignToolDefinitions: ({
             senderLinkedinUrl?: undefined;
             offerPositioning?: undefined;
             messageGenerationMode?: undefined;
+            messageApproach?: undefined;
             currentStep?: undefined;
             watchNarration?: undefined;
             leadSourceType?: undefined;

package/dist/tools/campaigns.js

@@ -447,6 +447,11 @@ export const campaignToolDefinitions = [
                     enum: ["template", "ai-generated"],
                     description: "Defaults to template for autonomous messaging steps. Use ai-generated only when the user explicitly approves freeform AI-generated messages instead of an approved {{token}} template.",
                 },
+                messageApproach: {
+                    type: "string",
+                    enum: ["conversation", "message_test"],
+                    description: 'How first messages are written. "conversation": each first message is written for that person by the backend writer and opens a conversation, with no pitch; the campaign must have NO approved message template and no {{token}} copy in the brief. "message_test": one approved message template goes to everyone, for testing copy. Omit to leave the campaign as it is.',
+                },
                 currentStep: {
                     type: ["string", "null"],
                     description: "Workflow step ID (headless or UI step ID such as filter-rules)",
@@ -569,6 +574,11 @@ export const campaignToolDefinitions = [
                     type: ["boolean", "null"],
                     description: "Whether to use the messaging template step",
                 },
+                messageApproach: {
+                    type: "string",
+                    enum: ["conversation", "message_test"],
+                    description: 'How first messages are written. "conversation": each first message is written for that person by the backend writer and opens a conversation, with no pitch; the campaign must have NO approved message template and no {{token}} copy in the brief. "message_test": one approved message template goes to everyone, for testing copy. Omit to leave the campaign as it is.',
+                },
                 autoApproveFollowups: {
                     type: "boolean",
                     description: "Whether drafted campaign follow-ups are automatically approved/sent. This does not draft, approve, or send an individual prospect message during the settings update.",
@@ -1046,7 +1056,10 @@ export async function createCampaign(input) {
     const isAutonomousMessageMint = currentStep === "auto-execute-leads" ||
         currentStep === "validate-sample" ||
         currentStep === "auto-execute-messaging";
-    const explicitlyAllowsAiGenerated = input.messageGenerationMode === "ai-generated";
+    // A conversation campaign has no template by design: each first message is
+    // written for the person by the backend writer.
+    const explicitlyAllowsAiGenerated = input.messageGenerationMode === "ai-generated" ||
+        input.messageApproach === "conversation";
     const hasTemplateToken = /\{\{\s*\S[^}]*\}\}/.test(briefContent);
     if (isAutonomousMessageMint &&
         !explicitlyAllowsAiGenerated &&

package/dist/tools/navigation.d.ts

@@ -12,6 +12,9 @@ export type CampaignOfferNavigation = {
     useMessagingTemplate?: boolean | null;
     messagingTemplateId?: string | null;
     messagingTemplate?: unknown | null;
+    messageGenerator?: {
+        mode?: string | null;
+    } | null;
     leadSourceType?: string | null;
     leadSourceProvider?: string | null;
     selectedLeadListId?: string | null;

package/dist/tools/navigation.js

@@ -140,6 +140,10 @@ function hasActiveRubrics(campaign) {
 function hasApprovedMessageTemplate(campaign) {
     if (campaign.messagingTemplateId || campaign.messagingTemplate)
         return true;
+    // A conversation campaign never has a template; its messages are written
+    // per person, so the message approach is already settled.
+    if (campaign.messageGenerator?.mode === "CONVERSATION")
+        return true;
     const briefContent = getBriefContent(campaign.campaignBrief);
     if (!briefContent.trim())
         return false;

package/dist/tools/registry.d.ts

@@ -2334,6 +2334,7 @@ export declare const allTools: ({
             offerPositioning?: undefined;
             campaignBrief?: undefined;
             messageGenerationMode?: undefined;
+            messageApproach?: undefined;
             currentStep?: undefined;
             watchNarration?: undefined;
             leadSourceType?: undefined;
@@ -2383,6 +2384,7 @@ export declare const allTools: ({
             offerPositioning?: undefined;
             campaignBrief?: undefined;
             messageGenerationMode?: undefined;
+            messageApproach?: undefined;
             currentStep?: undefined;
             watchNarration?: undefined;
             leadSourceType?: undefined;
@@ -2434,6 +2436,7 @@ export declare const allTools: ({
             offerPositioning?: undefined;
             campaignBrief?: undefined;
             messageGenerationMode?: undefined;
+            messageApproach?: undefined;
             currentStep?: undefined;
             watchNarration?: undefined;
             leadSourceType?: undefined;
@@ -2481,6 +2484,7 @@ export declare const allTools: ({
             offerPositioning?: undefined;
             campaignBrief?: undefined;
             messageGenerationMode?: undefined;
+            messageApproach?: undefined;
             currentStep?: undefined;
             watchNarration?: undefined;
             leadSourceType?: undefined;
@@ -2528,6 +2532,7 @@ export declare const allTools: ({
             offerPositioning?: undefined;
             campaignBrief?: undefined;
             messageGenerationMode?: undefined;
+            messageApproach?: undefined;
             currentStep?: undefined;
             watchNarration?: undefined;
             leadSourceType?: undefined;
@@ -2618,6 +2623,7 @@ export declare const allTools: ({
             offerPositioning?: undefined;
             campaignBrief?: undefined;
             messageGenerationMode?: undefined;
+            messageApproach?: undefined;
             currentStep?: undefined;
             watchNarration?: undefined;
             leadSourceType?: undefined;
@@ -2676,6 +2682,11 @@ export declare const allTools: ({
                 enum: string[];
                 description: string;
             };
+            messageApproach: {
+                type: string;
+                enum: string[];
+                description: string;
+            };
             currentStep: {
                 type: string[];
                 description: string;
@@ -3054,6 +3065,11 @@ export declare const allTools: ({
                 type: string[];
                 description: string;
             };
+            messageApproach: {
+                type: string;
+                enum: string[];
+                description: string;
+            };
             autoApproveFollowups: {
                 type: string;
                 description: string;
@@ -3121,6 +3137,7 @@ export declare const allTools: ({
             offerPositioning?: undefined;
             campaignBrief?: undefined;
             messageGenerationMode?: undefined;
+            messageApproach?: undefined;
             currentStep?: undefined;
             watchNarration?: undefined;
             leadSourceType?: undefined;
@@ -3171,6 +3188,7 @@ export declare const allTools: ({
             senderLinkedinUrl?: undefined;
             offerPositioning?: undefined;
             messageGenerationMode?: undefined;
+            messageApproach?: undefined;
             currentStep?: undefined;
             watchNarration?: undefined;
             leadSourceType?: undefined;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sellable/mcp",
-  "version": "0.1.952",
+  "version": "0.1.953",
   "type": "module",
   "description": "Sellable MCP server for Claude Code, Codex, and Hermes campaign workflows",
   "main": "dist/index.js",

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

@@ -80,6 +80,12 @@ approval and campaign setup validation.
 Use `research-sender`, call `complete_sender_research` before shell creation,
 and carry proof gaps into the brief.
 
+## Message Approach
+
+Before `create_campaign`, load `references/message-approach.md` and choose how
+first messages are written: Conversations (each written for the person, no
+template) or Message Lab (one approved template). Pass it as `messageApproach`.
+
 ## Brief Provenance
 
 When rendering the first brief, do not add bracketed inline source tags. Start
@@ -308,6 +314,7 @@ Route user copy feedback before `approve-message` back to Message Drafting; pare
 
 Load references only when needed:
 
+- `references/message-approach.md` before `create_campaign`.
 - `references/watch-link-handoff.md` for watch-link handoff.
 - `references/watch-guide-narration.md` for watch narration.
 - `references/lead-validation-preview.md` for legacy/debug preview shapes.

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

@@ -540,4 +540,6 @@ marketplace actors, wrong function, or no budget path, classify it as
 
 After filters are saved, wait for explicit filter approval before Filter Leads.
 Then wait for message template/token approval before enrichment, scoring, or
-Generate Message cells are queued.
+Generate Message cells are queued. A Conversations campaign
+(`references/message-approach.md`) has no template to approve: queue the
+sample once the filters are settled.

package/skills/create-campaign-v2/references/message-approach.md

@@ -0,0 +1,70 @@
+# Message Approach
+
+Every campaign writes its first message one of two ways. Decide which before
+`create_campaign`, pass it as `messageApproach`, and say which you picked in
+one plain line the customer can correct.
+
+- **Conversations** (`messageApproach: "conversation"`). Each first message is
+  written for that one person by Sellable's writer and opens a conversation.
+  It carries no pitch and no ask; the offer comes up once they reply. Choose
+  it when replies have an owner: reply drafting is on for the campaign (the
+  default), so each reply arrives as a draft to approve, or the workspace's
+  Reply Agent answers.
+- **Message Lab** (`messageApproach: "message_test"`). One approved message
+  goes to everyone, so the customer can test which copy wins. This is the
+  template flow described in the create-campaign-v2 prompt and flow file. Choose it when the
+  customer wants to approve exact wording, test copy against copy, or has
+  switched reply drafting off.
+
+When the customer has not said, use Conversations if replies have an owner and
+Message Lab otherwise. "Same message to everyone", "test my copy" or "I want
+to approve the wording" means Message Lab. "Write each one", "personal",
+"conversational" or "use the reply agent" means Conversations. Change an
+existing campaign with `update_campaign({ campaignId, messageApproach })`.
+
+**A Conversations campaign has no template.** The backend writes each message
+only when the campaign carries no approved template, so:
+
+- write no `## Approved Message Template` section, no `{{token}}` copy and no
+  first-message wording into the brief, and keep pitch wording out of `dos`;
+- put the offer and the proof under headings that say "for replies only";
+- when the first message goes out as a DM after the connection request is
+  accepted (the recommended sequence), add this line to the campaign `dos`
+  with the sender's first name: "This first message goes out as a LinkedIn DM
+  after they accept {sender}'s connection request: thank them for
+  connecting.";
+- skip Message Drafting, the message template review and the template
+  approval. After the filters are saved, queue enrichment for the sample;
+  fit scoring and Generate Message follow on their own;
+- review the generated messages themselves before showing or approving
+  them: the person and company match the profile, no pitch, and nothing
+  about the person that their profile does not show (a guessed city, a guessed
+  role). Leave a message that fails out of the sample, say so in one line,
+  and do not approve that row until it is rewritten
+  (`queue_campaign_cells` with `columnRole: "generateMessage"`, that row,
+  `forceRerun: true`). `get_campaign` reports the saved approach as
+  `campaignOffer.messageApproach`.
+
+**The writer sounds like the sender only when it knows the sender.** With
+exactly one sender attached to the campaign and that sender's context saved,
+it writes the full message, including a line about the sender. With no sender,
+several senders, or no saved context it writes the short form: a greeting,
+one plain line about the person's work, and a light line about their town. So in a Conversations campaign:
+
+1. Ask for the LinkedIn connection before the sample, not after it.
+2. Once `list_senders` shows the account, attach it
+   (`update_campaign({ campaignId, senderIds: [id] })`), read it with
+   `get_sender`, and save what the profile research found with
+   `set_sender_context` (pass `get_sender`'s `generationContext.updatedAt` as
+   `expectedUpdatedAt`, null on the first save). Use facts from the sender's
+   own profile only: what they built and did (`workStories`), plain personal
+   facts (`personalNotes`), a few lines in their own words from their posts
+   or About (`voiceExamples`), and what they may share or will not say
+   (`sourcesAndLimits`).
+3. Generate or regenerate the sample after that
+   (`queue_campaign_cells` with `columnRole: "generateMessage"`, the sample
+   rows, `forceRerun: true`).
+
+If the customer has not connected an account when the sample is ready, show
+the short-form sample and say the messages gain a line about them once the
+account is connected.

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

@@ -54,7 +54,8 @@ rerun `import_leads`.
   only after saved-filter approval; `validate-sample` is the logical loop name,
   not a visible route)
 - Approved message template/token rules exist in the campaign brief before any
-  enrichment or scoring cells are queued
+  enrichment or scoring cells are queued (Message Lab only; a Conversations
+  campaign has no template)
 - Confirmed campaign rows from Step 13, with the internal execution slice stored
   in `WorkflowTable.config.mcp.reviewBatch` (default 15)
 - Config from `auto-execute.yaml`: `sample.sampleSize`,

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

@@ -8,6 +8,13 @@ visibility: internal
 
 This is the tail detail extracted from the main create-campaign-v2 SKILL.md to keep the entry prompt slim. The agent loads this on-demand BEFORE entering the auto-execute or validate-sample steps. Follow this verbatim.
 
+**Conversations campaigns** (`messageApproach: "conversation"`, see
+`create-campaign-v2` `references/message-approach.md`) have no message
+template. Every rule below that requires an approved template, `{{...}}`
+tokens in the brief, Message Drafting, or template approval before queueing
+applies to Message Lab campaigns only. In a Conversations campaign the same
+cascade writes each message once a row passes the fit check.
+
 CampaignOffer state and the watch link are canonical. Disk artifacts are
 optional debug/UAT diagnostics; normal customer runs should not expose local
 draft files. Resume, gating, and handoff read campaign state first.
@@ -380,7 +387,8 @@ the output — not to generate messages manually.
 **What Step 15 does:**
 
 1. Before queueing or waiting on Generate Message cells, confirm the minted
-   campaign brief still contains `{{...}}` in `## Approved Message Template`.
+   campaign brief still contains `{{...}}` in `## Approved Message Template`
+   (Message Lab only; a Conversations campaign must have no template).
    If it does not, fail before the cascade runs. Do not repair after mint; the
    template must be present during mint so Step 15 never starts in freeform
    generation mode.

package/skills/first-campaign-onboarding/SKILL.md

@@ -48,7 +48,9 @@ reply to either the same way.)
 A reply in that thread is explicit permission to begin preparation, not
 permission to send. It needs no mention of this Agent.
 
-- **The reply contains a LinkedIn profile URL.** Send one short line first so
+- **The reply contains a LinkedIn profile URL or handle.** A single word such
+  as `csreyes92` or `@csreyes92` is a handle: read it as
+  `https://www.linkedin.com/in/{handle}/`. Send one short line first so
   the customer is not left looking at silence: "Got it. Researching you and
   your company now. I'll be back in a few minutes with a first campaign to
   review." Send it before the Live State Check and before loading any other
@@ -278,6 +280,15 @@ for the message template: those are yours to decide and report.
 - Do not paste the full brief into Slack. Save it on the campaign and post the
   five-line summary below.
 
+**How the first message is written.** The first campaign uses the
+Conversations approach from the workflow's `references/message-approach.md`:
+create it with `messageApproach: "conversation"`, write no message template,
+and let Sellable's writer write each first message for the person. Use Message
+Lab (`"message_test"`, one approved message to everyone) only when the
+customer asks to send the same message to everyone, to test copy, or to
+approve exact wording; then the template steps of the workflow apply and you
+approve the template yourself as before.
+
 **Approval 1: direction.** After research, write the brief, create the
 campaign with it (`create_campaign`), and post one message in this shape. The
 saved brief is the full brief; this message is how the customer approves it,
@@ -292,6 +303,7 @@ Here's the first campaign I'd run for {company}.
 *Offer*  {what you would get to once they reply, and the small ask, one line}
 *Proof*  {the proof you would lead with; if you found none, say so and what you would use instead}
 *Where I'll look*  {where you will find them first, in plain words}
+*Messages*  Written for each person to open a conversation; the offer comes once they reply. Say "same message to everyone" if you'd rather test one message.
 
 Full brief: {campaign link}
 
@@ -325,13 +337,17 @@ do-not-contact gate; do not ask again before the import.
 
 **Between 1 and 2.** Once the direction and the do-not-contact answer are in,
 reply first, before any tool call: "On it. I'll find the people, check who
-fits and write the message. Your sample will be here in about 15 to 20
-minutes." Then set `interactionMode: "autonomous"` on the campaign with
+fits and write the messages. Your sample will be here in about 15 to 20
+minutes. While I work: connect the LinkedIn account that will send,
+https://app.sellable.dev/linkedin-accounts It takes about two minutes, it is
+only used to send what you approve, and once it's connected I write the
+messages in your voice." Then set `interactionMode: "autonomous"` on the campaign with
 `update_campaign` and pass `confirmed: true` where a search or import tool
 asks for it: the direction approval is that confirmation. Do the work without
 asking: pick where to look, find and import the people within the flow's
-caps, use filters and write the rules, write the message, and prepare the
-15-person sample.
+caps, use filters and write the rules, and prepare the 15-person sample. In
+Conversations there is no template to write: queue the sample once the rules
+are saved and the messages are written for you.
 
 - **Keep the customer posted.** Whenever about five minutes have passed since
   your last message, post one short line in plain words on where you are
@@ -353,6 +369,13 @@ caps, use filters and write the rules, write the message, and prepare the
 - **Let the sample finish.** The flow stops at the first passing message; here
   wait until the 15-person sample has finished scoring and writing, because
   the customer is shown three people and a count.
+- **The sender, as soon as there is one.** Check `list_senders` when the
+  import finishes and again before you show the sample. When the customer's
+  account is there, attach it to the campaign, save what your research found
+  about them as sender context, and write or rewrite the sample after that,
+  as `references/message-approach.md` describes. A sample written
+  before the account was connected is the short form, with nothing about the
+  sender.
 - **Check before you show.** For each message you are about to show, compare
   the company it names with the person's own headline. Leave out any that
   disagree and say that you dropped them.
@@ -361,7 +384,7 @@ caps, use filters and write the rules, write the message, and prepare the
 real message each would receive:
 
 ```text
-Your sample is ready: {n} real people and the message each would get.
+Your sample is ready: {the number you show below} real people and the message each would get.
 
 {Name} · {title}, {company} · {why they are here, a few words}
 "{the message they would receive}"
@@ -370,10 +393,11 @@ Your sample is ready: {n} real people and the message each would get.
 
 {passed} of {checked} people I checked fit. {one line on why the rest did not}
 What I chose: {where the people came from and how many are on the list, and the fit rules in a few words}
-The first message has no pitch on purpose. {the offer} comes once they reply.
+Each message is written for that person and has no pitch on purpose. {the offer} comes once they reply.
+{only if no sending account is connected yet: "These are the short version. Connect your LinkedIn account and I'll rewrite them with a line about you: https://app.sellable.dev/linkedin-accounts"}
 Everyone and every message: {campaign link}
 
-Reply approve to use these people and this message, or tell me what to change.
+Reply approve to use these people and messages like these, or tell me what to change.
 Nothing has been sent.
 ```
 
@@ -383,8 +407,8 @@ the customer kept as approved in the table, not one or two. A person the
 customer dropped stays unapproved; never approve them later, in bulk or
 otherwise.
 
-**Approval 3: launch.** The only thing left is the sending account. Call
-`list_senders`.
+**Approval 3: launch.** The only thing that can still be missing is the
+sending account. Call `list_senders`.
 
 - **No usable sender.** Ask for that one thing: "One thing left: connect the
   LinkedIn account that will send. https://app.sellable.dev/linkedin-accounts