@sellable/mcp 0.1.954 → 0.1.956

package/dist/tools/campaigns.d.ts

@@ -73,6 +73,7 @@ export interface CampaignDetail {
 export interface CampaignAutomationSettings {
     autoApproveFollowups: boolean | null;
     enableFollowUps: boolean | null;
+    autoApproveReplies: boolean | null;
 }
 export interface CampaignMessagesPreviewInput {
     campaignId: string;
@@ -171,6 +172,7 @@ export interface UpdateCampaignInput {
     messageApproach?: "conversation" | "message_test";
     autoApproveFollowups?: boolean;
     enableFollowUps?: boolean;
+    autoApproveReplies?: boolean;
     senderIds?: string[];
     rubric?: unknown[];
 }
@@ -270,6 +272,7 @@ export declare const campaignToolDefinitions: ({
             useMessagingTemplate?: undefined;
             autoApproveFollowups?: undefined;
             enableFollowUps?: undefined;
+            autoApproveReplies?: undefined;
             rubric?: undefined;
             flowVersion?: undefined;
         };
@@ -320,6 +323,7 @@ export declare const campaignToolDefinitions: ({
             useMessagingTemplate?: undefined;
             autoApproveFollowups?: undefined;
             enableFollowUps?: undefined;
+            autoApproveReplies?: undefined;
             rubric?: undefined;
             flowVersion?: undefined;
         };
@@ -372,6 +376,7 @@ export declare const campaignToolDefinitions: ({
             useMessagingTemplate?: undefined;
             autoApproveFollowups?: undefined;
             enableFollowUps?: undefined;
+            autoApproveReplies?: undefined;
             rubric?: undefined;
             flowVersion?: undefined;
         };
@@ -420,6 +425,7 @@ export declare const campaignToolDefinitions: ({
             useMessagingTemplate?: undefined;
             autoApproveFollowups?: undefined;
             enableFollowUps?: undefined;
+            autoApproveReplies?: undefined;
             rubric?: undefined;
             flowVersion?: undefined;
         };
@@ -468,6 +474,7 @@ export declare const campaignToolDefinitions: ({
             useMessagingTemplate?: undefined;
             autoApproveFollowups?: undefined;
             enableFollowUps?: undefined;
+            autoApproveReplies?: undefined;
             rubric?: undefined;
             flowVersion?: undefined;
         };
@@ -559,6 +566,7 @@ export declare const campaignToolDefinitions: ({
             useMessagingTemplate?: undefined;
             autoApproveFollowups?: undefined;
             enableFollowUps?: undefined;
+            autoApproveReplies?: undefined;
             rubric?: undefined;
             flowVersion?: undefined;
         };
@@ -769,6 +777,7 @@ export declare const campaignToolDefinitions: ({
             useMessagingTemplate?: undefined;
             autoApproveFollowups?: undefined;
             enableFollowUps?: undefined;
+            autoApproveReplies?: undefined;
             rubric?: undefined;
             flowVersion?: undefined;
         };
@@ -997,6 +1006,10 @@ export declare const campaignToolDefinitions: ({
                 type: string;
                 description: string;
             };
+            autoApproveReplies: {
+                type: string;
+                description: string;
+            };
             senderIds: {
                 type: string;
                 items: {
@@ -1073,6 +1086,7 @@ export declare const campaignToolDefinitions: ({
             useMessagingTemplate?: undefined;
             autoApproveFollowups?: undefined;
             enableFollowUps?: undefined;
+            autoApproveReplies?: undefined;
             rubric?: undefined;
             flowVersion?: undefined;
         };
@@ -1124,6 +1138,7 @@ export declare const campaignToolDefinitions: ({
             useMessagingTemplate?: undefined;
             autoApproveFollowups?: undefined;
             enableFollowUps?: undefined;
+            autoApproveReplies?: undefined;
             rubric?: undefined;
             flowVersion?: undefined;
         };

package/dist/tools/campaigns.js

@@ -587,6 +587,10 @@ export const campaignToolDefinitions = [
                     type: "boolean",
                     description: "Whether the campaign follow-up sweeper may draft follow-ups. Keep true when enabling autoApproveFollowups unless the user explicitly requests drafting suppression.",
                 },
+                autoApproveReplies: {
+                    type: "boolean",
+                    description: "Whether drafted replies to prospects who answered are sent without the customer reviewing them. Set it only when the customer asks for automatic replies, and tell them replies will go out without their review. Default is off: every reply waits for the customer in the inbox.",
+                },
                 senderIds: {
                     type: "array",
                     items: { type: "string" },
@@ -712,6 +716,9 @@ function readCampaignAutomationSettings(source) {
         enableFollowUps: typeof source.enableFollowUps === "boolean"
             ? source.enableFollowUps
             : null,
+        autoApproveReplies: typeof source.autoApproveReplies === "boolean"
+            ? source.autoApproveReplies
+            : null,
     };
 }
 function normalizeCellValue(cell) {
@@ -1127,7 +1134,8 @@ export async function updateCampaign(campaignId, input) {
     const { campaignId: _ignore, workspaceId, interactionMode, flowVersion: _flowVersion, senderIds, currentStep, ...updates } = input;
     const hasSenderIds = Object.prototype.hasOwnProperty.call(input, "senderIds");
     const hasAutomationSettings = Object.prototype.hasOwnProperty.call(input, "autoApproveFollowups") ||
-        Object.prototype.hasOwnProperty.call(input, "enableFollowUps");
+        Object.prototype.hasOwnProperty.call(input, "enableFollowUps") ||
+        Object.prototype.hasOwnProperty.call(input, "autoApproveReplies");
     const requestOptions = workspaceId ? { workspaceId } : undefined;
     if (!hasSenderIds && currentStep !== undefined) {
         updates.currentStep = currentStep;

package/dist/tools/customer-program.d.ts

@@ -1,6 +1,6 @@
 export declare const customerProgramToolDefinitions: readonly [{
     readonly name: "customer_program";
-    readonly description: "Observe the home workspace campaign relationship stage, read prior complete daily or weekly campaign results, and retain campaign context. Scheduled stage_delivery grants native posting only when delivery.deliverNow is true; false means stay silent and reconcile. Save only newly learned campaign context or customer work/report preferences; campaign creation and editing stay in the create-campaign workflow. When the customer says where they are or wants updates at their own morning, call set_preferences with preferences.timezone (IANA, e.g. Europe/London); messages then go out at 08:00 and 09:00 their time on their working days. The customer gets one message a day.";
+    readonly description: "Observe the home workspace campaign relationship stage, read prior complete daily or weekly campaign results, and retain campaign context. Scheduled stage_delivery grants native posting only when delivery.deliverNow is true; false means stay silent and reconcile. Save only newly learned campaign context or customer work/report preferences; campaign creation and editing stay in the create-campaign workflow. When the customer says where they are or wants updates at their own morning, call set_preferences with preferences.timezone (IANA, e.g. Europe/London); messages then go out at 08:00 and 09:00 their time on their working days. The customer gets one message a day. Some changes are made only in the Sellable web app at https://app.sellable.dev; when asked for one, give the exact link and say what to click: card, invoices and the plan (owner only): /settings?tab=billing; Slack channels, and restarting, stopping or removing the agent: /sellable-agent/connection; adding or reconnecting LinkedIn, daily limits and sending hours: /linkedin-accounts; reply settings for one campaign: /campaign-builder/{campaignId}/settings. Do everything else yourself with your tools.";
     readonly inputSchema: {
         readonly type: "object";
         readonly properties: {

package/dist/tools/customer-program.js

@@ -2,7 +2,7 @@ import { getApi, SellableApiError } from "../api.js";
 export const customerProgramToolDefinitions = [
     {
         name: "customer_program",
-        description: "Observe the home workspace campaign relationship stage, read prior complete daily or weekly campaign results, and retain campaign context. Scheduled stage_delivery grants native posting only when delivery.deliverNow is true; false means stay silent and reconcile. Save only newly learned campaign context or customer work/report preferences; campaign creation and editing stay in the create-campaign workflow. When the customer says where they are or wants updates at their own morning, call set_preferences with preferences.timezone (IANA, e.g. Europe/London); messages then go out at 08:00 and 09:00 their time on their working days. The customer gets one message a day.",
+        description: "Observe the home workspace campaign relationship stage, read prior complete daily or weekly campaign results, and retain campaign context. Scheduled stage_delivery grants native posting only when delivery.deliverNow is true; false means stay silent and reconcile. Save only newly learned campaign context or customer work/report preferences; campaign creation and editing stay in the create-campaign workflow. When the customer says where they are or wants updates at their own morning, call set_preferences with preferences.timezone (IANA, e.g. Europe/London); messages then go out at 08:00 and 09:00 their time on their working days. The customer gets one message a day. Some changes are made only in the Sellable web app at https://app.sellable.dev; when asked for one, give the exact link and say what to click: card, invoices and the plan (owner only): /settings?tab=billing; Slack channels, and restarting, stopping or removing the agent: /sellable-agent/connection; adding or reconnecting LinkedIn, daily limits and sending hours: /linkedin-accounts; reply settings for one campaign: /campaign-builder/{campaignId}/settings. Do everything else yourself with your tools.",
         inputSchema: {
             type: "object",
             properties: {

package/dist/tools/registry.d.ts

@@ -2351,6 +2351,7 @@ export declare const allTools: ({
             useMessagingTemplate?: undefined;
             autoApproveFollowups?: undefined;
             enableFollowUps?: undefined;
+            autoApproveReplies?: undefined;
             rubric?: undefined;
             flowVersion?: undefined;
         };
@@ -2401,6 +2402,7 @@ export declare const allTools: ({
             useMessagingTemplate?: undefined;
             autoApproveFollowups?: undefined;
             enableFollowUps?: undefined;
+            autoApproveReplies?: undefined;
             rubric?: undefined;
             flowVersion?: undefined;
         };
@@ -2453,6 +2455,7 @@ export declare const allTools: ({
             useMessagingTemplate?: undefined;
             autoApproveFollowups?: undefined;
             enableFollowUps?: undefined;
+            autoApproveReplies?: undefined;
             rubric?: undefined;
             flowVersion?: undefined;
         };
@@ -2501,6 +2504,7 @@ export declare const allTools: ({
             useMessagingTemplate?: undefined;
             autoApproveFollowups?: undefined;
             enableFollowUps?: undefined;
+            autoApproveReplies?: undefined;
             rubric?: undefined;
             flowVersion?: undefined;
         };
@@ -2549,6 +2553,7 @@ export declare const allTools: ({
             useMessagingTemplate?: undefined;
             autoApproveFollowups?: undefined;
             enableFollowUps?: undefined;
+            autoApproveReplies?: undefined;
             rubric?: undefined;
             flowVersion?: undefined;
         };
@@ -2640,6 +2645,7 @@ export declare const allTools: ({
             useMessagingTemplate?: undefined;
             autoApproveFollowups?: undefined;
             enableFollowUps?: undefined;
+            autoApproveReplies?: undefined;
             rubric?: undefined;
             flowVersion?: undefined;
         };
@@ -2850,6 +2856,7 @@ export declare const allTools: ({
             useMessagingTemplate?: undefined;
             autoApproveFollowups?: undefined;
             enableFollowUps?: undefined;
+            autoApproveReplies?: undefined;
             rubric?: undefined;
             flowVersion?: undefined;
         };
@@ -3078,6 +3085,10 @@ export declare const allTools: ({
                 type: string;
                 description: string;
             };
+            autoApproveReplies: {
+                type: string;
+                description: string;
+            };
             senderIds: {
                 type: string;
                 items: {
@@ -3154,6 +3165,7 @@ export declare const allTools: ({
             useMessagingTemplate?: undefined;
             autoApproveFollowups?: undefined;
             enableFollowUps?: undefined;
+            autoApproveReplies?: undefined;
             rubric?: undefined;
             flowVersion?: undefined;
         };
@@ -3205,6 +3217,7 @@ export declare const allTools: ({
             useMessagingTemplate?: undefined;
             autoApproveFollowups?: undefined;
             enableFollowUps?: undefined;
+            autoApproveReplies?: undefined;
             rubric?: undefined;
             flowVersion?: undefined;
         };
@@ -8709,7 +8722,7 @@ export declare const allTools: ({
     };
 } | {
     readonly name: "customer_program";
-    readonly description: "Observe the home workspace campaign relationship stage, read prior complete daily or weekly campaign results, and retain campaign context. Scheduled stage_delivery grants native posting only when delivery.deliverNow is true; false means stay silent and reconcile. Save only newly learned campaign context or customer work/report preferences; campaign creation and editing stay in the create-campaign workflow. When the customer says where they are or wants updates at their own morning, call set_preferences with preferences.timezone (IANA, e.g. Europe/London); messages then go out at 08:00 and 09:00 their time on their working days. The customer gets one message a day.";
+    readonly description: "Observe the home workspace campaign relationship stage, read prior complete daily or weekly campaign results, and retain campaign context. Scheduled stage_delivery grants native posting only when delivery.deliverNow is true; false means stay silent and reconcile. Save only newly learned campaign context or customer work/report preferences; campaign creation and editing stay in the create-campaign workflow. When the customer says where they are or wants updates at their own morning, call set_preferences with preferences.timezone (IANA, e.g. Europe/London); messages then go out at 08:00 and 09:00 their time on their working days. The customer gets one message a day. Some changes are made only in the Sellable web app at https://app.sellable.dev; when asked for one, give the exact link and say what to click: card, invoices and the plan (owner only): /settings?tab=billing; Slack channels, and restarting, stopping or removing the agent: /sellable-agent/connection; adding or reconnecting LinkedIn, daily limits and sending hours: /linkedin-accounts; reply settings for one campaign: /campaign-builder/{campaignId}/settings. Do everything else yourself with your tools.";
     readonly inputSchema: {
         readonly type: "object";
         readonly properties: {

package/package.json

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

package/skills/campaign-daily-results/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: campaign-daily-results
-description: Post the one daily message: yesterday's numbers, who accepted and who replied by name, what Sellable did, and the one next step that gets more sent.
+description: "Post the one daily message with yesterday's numbers, who accepted and who replied by name, what Sellable did, and the one next step that gets more sent."
 visibility: public
 allowed-tools:
   - mcp__sellable__get_auth_status
@@ -13,6 +13,27 @@ Give the customer one concise snapshot of the prior complete day from their
 existing campaigns. This is a read-only results workflow. It does not create,
 edit, launch or refill campaigns, and it does not send or draft replies.
 
+## Writing to the customer
+
+Everything you write to the customer (Slack messages, questions, progress
+notes, summaries, the campaign brief) follows ASD-STE100 Simplified Technical
+English at about 80%:
+
+- One idea per sentence. One instruction per sentence.
+- An instruction has at most 20 words; any other sentence at most 25.
+- Active voice: say who does the action ("I added 60 people").
+- Simple tenses only: present, simple past, and "will".
+- Common words with one meaning. Use the same word for the same thing every time.
+- No idioms, slang or phrasal verbs where one verb works: "start", not "kick off".
+- An instruction starts with its verb: "Reply to Priya.", "Connect your LinkedIn."
+- Keep small words such as "the", "a" and "to". Use a list for more than two items.
+
+Relaxed for Slack: product words (invite, InMail, campaign, sender), contractions,
+and quoted prospect text exactly as written. This rule is for text to the
+customer only. Messages written for prospects (openers, replies, follow-ups,
+comments, posts) follow the campaign's and the sender's own voice rules, never
+this one.
+
 ## Read the snapshot
 
 1. Call `get_auth_status`, then call `customer_program` with

package/skills/campaign-daily-review/SKILL.md

@@ -19,6 +19,27 @@ is one continuous workflow: understand current workspace state, choose one
 useful next step, use the existing campaign owner, observe the result, and save
 the exact wait or outcome.
 
+## Writing to the customer
+
+Everything you write to the customer (Slack messages, questions, progress
+notes, summaries, the campaign brief) follows ASD-STE100 Simplified Technical
+English at about 80%:
+
+- One idea per sentence. One instruction per sentence.
+- An instruction has at most 20 words; any other sentence at most 25.
+- Active voice: say who does the action ("I added 60 people").
+- Simple tenses only: present, simple past, and "will".
+- Common words with one meaning. Use the same word for the same thing every time.
+- No idioms, slang or phrasal verbs where one verb works: "start", not "kick off".
+- An instruction starts with its verb: "Reply to Priya.", "Connect your LinkedIn."
+- Keep small words such as "the", "a" and "to". Use a list for more than two items.
+
+Relaxed for Slack: product words (invite, InMail, campaign, sender), contractions,
+and quoted prospect text exactly as written. This rule is for text to the
+customer only. Messages written for prospects (openers, replies, follow-ups,
+comments, posts) follow the campaign's and the sender's own voice rules, never
+this one.
+
 ## Run the review
 
 1. Call `get_auth_status`, then obtain a fenced `customer_program` review claim

package/skills/campaign-weekly-review/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: campaign-weekly-review
-description: Post Monday's one message: last week's numbers against the week before, who accepted and who replied by name, and the one next step that gets more sent.
+description: "Post Monday's one message with last week's numbers against the week before, who accepted and who replied by name, and the one next step that gets more sent."
 visibility: public
 allowed-tools:
   - mcp__sellable__get_auth_status
@@ -18,6 +18,27 @@ Give the customer one useful review of the prior complete local Monday through
 Sunday, compared with the equal complete week before it. Use existing campaign
 truth and keep the recommendation inside the same continuous campaign program.
 
+## Writing to the customer
+
+Everything you write to the customer (Slack messages, questions, progress
+notes, summaries, the campaign brief) follows ASD-STE100 Simplified Technical
+English at about 80%:
+
+- One idea per sentence. One instruction per sentence.
+- An instruction has at most 20 words; any other sentence at most 25.
+- Active voice: say who does the action ("I added 60 people").
+- Simple tenses only: present, simple past, and "will".
+- Common words with one meaning. Use the same word for the same thing every time.
+- No idioms, slang or phrasal verbs where one verb works: "start", not "kick off".
+- An instruction starts with its verb: "Reply to Priya.", "Connect your LinkedIn."
+- Keep small words such as "the", "a" and "to". Use a list for more than two items.
+
+Relaxed for Slack: product words (invite, InMail, campaign, sender), contractions,
+and quoted prospect text exactly as written. This rule is for text to the
+customer only. Messages written for prospects (openers, replies, follow-ups,
+comments, posts) follow the campaign's and the sender's own voice rules, never
+this one.
+
 ## Read the review
 
 1. Call `get_auth_status`, then call `customer_program` with

package/skills/create-ab-test/SKILL.md

@@ -77,6 +77,27 @@ Use this workflow when the user asks to create an A/B campaign test, split a
 campaign into variants, duplicate a campaign for copy testing, or compare two
 campaign-message approaches from the same source list.
 
+## Writing to the customer
+
+Everything you write to the customer (Slack messages, questions, progress
+notes, summaries, the campaign brief) follows ASD-STE100 Simplified Technical
+English at about 80%:
+
+- One idea per sentence. One instruction per sentence.
+- An instruction has at most 20 words; any other sentence at most 25.
+- Active voice: say who does the action ("I added 60 people").
+- Simple tenses only: present, simple past, and "will".
+- Common words with one meaning. Use the same word for the same thing every time.
+- No idioms, slang or phrasal verbs where one verb works: "start", not "kick off".
+- An instruction starts with its verb: "Reply to Priya.", "Connect your LinkedIn."
+- Keep small words such as "the", "a" and "to". Use a list for more than two items.
+
+Relaxed for Slack: product words (invite, InMail, campaign, sender), contractions,
+and quoted prospect text exactly as written. This rule is for text to the
+customer only. Messages written for prospects (openers, replies, follow-ups,
+comments, posts) follow the campaign's and the sender's own voice rules, never
+this one.
+
 ## Opening Contract
 
 Start by identifying the campaign idea and the one variable being tested.

package/skills/create-campaign/SKILL.md

@@ -91,6 +91,8 @@ It bootstraps auth and host capabilities, then loads the internal
 the internal campaign workflow prompt and `core/flow.v2.json` through MCP. Keep
 this wrapper thin; the packaged workflow is the operational source of truth.
 
+**Writing to the customer:** ASD-STE100 at about 80% (short active sentences, one idea each, instructions start with the verb). Never for prospect messages.
+
 ## Direct Manual-Copy Campaign Routing
 
 Route a bounded one-off request to the direct campaign tools when the user

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

@@ -19,6 +19,27 @@ This is Phase 83 of the brief-first create-campaign path. The runnable command
 is `create-campaign-brief`. Do not introduce or ask for a public
 `create-campaign-v2` command in this phase.
 
+## Writing to the customer
+
+Everything you write to the customer (Slack messages, questions, progress
+notes, summaries, the campaign brief) follows ASD-STE100 Simplified Technical
+English at about 80%:
+
+- One idea per sentence. One instruction per sentence.
+- An instruction has at most 20 words; any other sentence at most 25.
+- Active voice: say who does the action ("I added 60 people").
+- Simple tenses only: present, simple past, and "will".
+- Common words with one meaning. Use the same word for the same thing every time.
+- No idioms, slang or phrasal verbs where one verb works: "start", not "kick off".
+- An instruction starts with its verb: "Reply to Priya.", "Connect your LinkedIn."
+- Keep small words such as "the", "a" and "to". Use a list for more than two items.
+
+Relaxed for Slack: product words (invite, InMail, campaign, sender), contractions,
+and quoted prospect text exactly as written. This rule is for text to the
+customer only. Messages written for prospects (openers, replies, follow-ups,
+comments, posts) follow the campaign's and the sender's own voice rules, never
+this one.
+
 ## Required Inputs
 
 Start from:

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

@@ -28,6 +28,8 @@ There is no normal approval-packet, commit-gate, or atomic-mint path in the
 active flow. Legacy packet/mint artifacts stay in
 `create-campaign-v2-validation` and rehearsal material only.
 
+**Writing to the customer.** Every line you write to the customer follows ASD-STE100 Simplified Technical English at about 80%: one idea per sentence, instructions of at most 20 words and other sentences of at most 25, active voice, simple tenses, one word for one thing, no idioms, and an instruction starts with its verb. Product words, contractions and quoted prospect text are fine. Never apply it to messages written for prospects.
+
 ## Normal Flow
 
 1. Bootstrap and show the active Sellable workspace.

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

@@ -21,6 +21,27 @@ draft files. Resume, gating, and handoff read campaign state first.
 selectedLeadListId remains the source list; workflowTableId is the campaign
 table.
 
+## Writing to the customer
+
+Everything you write to the customer (Slack messages, questions, progress
+notes, summaries, the campaign brief) follows ASD-STE100 Simplified Technical
+English at about 80%:
+
+- One idea per sentence. One instruction per sentence.
+- An instruction has at most 20 words; any other sentence at most 25.
+- Active voice: say who does the action ("I added 60 people").
+- Simple tenses only: present, simple past, and "will".
+- Common words with one meaning. Use the same word for the same thing every time.
+- No idioms, slang or phrasal verbs where one verb works: "start", not "kick off".
+- An instruction starts with its verb: "Reply to Priya.", "Connect your LinkedIn."
+- Keep small words such as "the", "a" and "to". Use a list for more than two items.
+
+Relaxed for Slack: product words (invite, InMail, campaign, sender), contractions,
+and quoted prospect text exactly as written. This rule is for text to the
+customer only. Messages written for prospects (openers, replies, follow-ups,
+comments, posts) follow the campaign's and the sender's own voice rules, never
+this one.
+
 ## MANDATORY TOOL ORDER (read this BEFORE any tail step)
 
 Every tail run MUST call these tools in this exact order. The tail is

package/skills/create-evergreen-campaigns/SKILL.md

@@ -14,6 +14,27 @@ producing duplicates. This skill never launches campaigns; customer-visible
 completion stops at paused send review.
 </role>
 
+## Writing to the customer
+
+Everything you write to the customer (Slack messages, questions, progress
+notes, summaries, the campaign brief) follows ASD-STE100 Simplified Technical
+English at about 80%:
+
+- One idea per sentence. One instruction per sentence.
+- An instruction has at most 20 words; any other sentence at most 25.
+- Active voice: say who does the action ("I added 60 people").
+- Simple tenses only: present, simple past, and "will".
+- Common words with one meaning. Use the same word for the same thing every time.
+- No idioms, slang or phrasal verbs where one verb works: "start", not "kick off".
+- An instruction starts with its verb: "Reply to Priya.", "Connect your LinkedIn."
+- Keep small words such as "the", "a" and "to". Use a list for more than two items.
+
+Relaxed for Slack: product words (invite, InMail, campaign, sender), contractions,
+and quoted prospect text exactly as written. This rule is for text to the
+customer only. Messages written for prospects (openers, replies, follow-ups,
+comments, posts) follow the campaign's and the sender's own voice rules, never
+this one.
+
 ## Invocation Mode Gate
 
 Before any setup plan, classify the invocation mode.

package/skills/create-rubric/SKILL.md

@@ -37,6 +37,27 @@ Create and save a comprehensive lead scoring rubric that:
 
 <tools>
 
+## Writing to the customer
+
+Everything you write to the customer (Slack messages, questions, progress
+notes, summaries, the campaign brief) follows ASD-STE100 Simplified Technical
+English at about 80%:
+
+- One idea per sentence. One instruction per sentence.
+- An instruction has at most 20 words; any other sentence at most 25.
+- Active voice: say who does the action ("I added 60 people").
+- Simple tenses only: present, simple past, and "will".
+- Common words with one meaning. Use the same word for the same thing every time.
+- No idioms, slang or phrasal verbs where one verb works: "start", not "kick off".
+- An instruction starts with its verb: "Reply to Priya.", "Connect your LinkedIn."
+- Keep small words such as "the", "a" and "to". Use a list for more than two items.
+
+Relaxed for Slack: product words (invite, InMail, campaign, sender), contractions,
+and quoted prospect text exactly as written. This rule is for text to the
+customer only. Messages written for prospects (openers, replies, follow-ups,
+comments, posts) follow the campaign's and the sender's own voice rules, never
+this one.
+
 ## Campaign Context
 
 - `mcp__sellable__get_campaign` - Get campaign brief and positioning

package/skills/find-leads/SKILL.md

@@ -37,6 +37,27 @@ Use this public command when the user asks to find or source prospects, build a
 watch the list fill in real time, review leads, or export the list.
 It works without an existing campaign.
 
+## Writing to the customer
+
+Everything you write to the customer (Slack messages, questions, progress
+notes, summaries, the campaign brief) follows ASD-STE100 Simplified Technical
+English at about 80%:
+
+- One idea per sentence. One instruction per sentence.
+- An instruction has at most 20 words; any other sentence at most 25.
+- Active voice: say who does the action ("I added 60 people").
+- Simple tenses only: present, simple past, and "will".
+- Common words with one meaning. Use the same word for the same thing every time.
+- No idioms, slang or phrasal verbs where one verb works: "start", not "kick off".
+- An instruction starts with its verb: "Reply to Priya.", "Connect your LinkedIn."
+- Keep small words such as "the", "a" and "to". Use a list for more than two items.
+
+Relaxed for Slack: product words (invite, InMail, campaign, sender), contractions,
+and quoted prospect text exactly as written. This rule is for text to the
+customer only. Messages written for prospects (openers, replies, follow-ups,
+comments, posts) follow the campaign's and the sender's own voice rules, never
+this one.
+
 ## Load the canonical workflow
 
 1. Call `mcp__sellable__get_auth_status({})` and complete login/workspace setup

package/skills/find-leads-v2/SKILL.md

@@ -10,6 +10,27 @@ This is the canonical campaignless workflow. The durable identity invariant is
 `runId = leadListId`. Resume from product state with `get_find_leads_run`; never
 reconstruct progress from chat memory.
 
+## Writing to the customer
+
+Everything you write to the customer (Slack messages, questions, progress
+notes, summaries, the campaign brief) follows ASD-STE100 Simplified Technical
+English at about 80%:
+
+- One idea per sentence. One instruction per sentence.
+- An instruction has at most 20 words; any other sentence at most 25.
+- Active voice: say who does the action ("I added 60 people").
+- Simple tenses only: present, simple past, and "will".
+- Common words with one meaning. Use the same word for the same thing every time.
+- No idioms, slang or phrasal verbs where one verb works: "start", not "kick off".
+- An instruction starts with its verb: "Reply to Priya.", "Connect your LinkedIn."
+- Keep small words such as "the", "a" and "to". Use a list for more than two items.
+
+Relaxed for Slack: product words (invite, InMail, campaign, sender), contractions,
+and quoted prospect text exactly as written. This rule is for text to the
+customer only. Messages written for prospects (openers, replies, follow-ups,
+comments, posts) follow the campaign's and the sender's own voice rules, never
+this one.
+
 ## Prerequisites and recovery
 
 - Call `get_auth_status`. If login is required, use `start_cli_login` and

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

@@ -14,6 +14,27 @@ use Sellable Admin, inspect sibling workspaces, query production directly, or
 write to Slack yourself. In a scheduled Hermes run, return the final reminder
 as the run reply; the Hermes gateway owns delivery.
 
+## Writing to the customer
+
+Everything you write to the customer (Slack messages, questions, progress
+notes, summaries, the campaign brief) follows ASD-STE100 Simplified Technical
+English at about 80%:
+
+- One idea per sentence. One instruction per sentence.
+- An instruction has at most 20 words; any other sentence at most 25.
+- Active voice: say who does the action ("I added 60 people").
+- Simple tenses only: present, simple past, and "will".
+- Common words with one meaning. Use the same word for the same thing every time.
+- No idioms, slang or phrasal verbs where one verb works: "start", not "kick off".
+- An instruction starts with its verb: "Reply to Priya.", "Connect your LinkedIn."
+- Keep small words such as "the", "a" and "to". Use a list for more than two items.
+
+Relaxed for Slack: product words (invite, InMail, campaign, sender), contractions,
+and quoted prospect text exactly as written. This rule is for text to the
+customer only. Messages written for prospects (openers, replies, follow-ups,
+comments, posts) follow the campaign's and the sender's own voice rules, never
+this one.
+
 ## Outcomes
 
 Work toward these milestones in order, asking for only the smallest useful next

package/skills/foundation/SKILL.md

@@ -48,3 +48,24 @@ Do not create campaigns here. Use `$sellable:create-campaign`.
 Do not move identity, proof, stories, answer-bank entries, transcript archives,
 or anti-AI rules into `~/.sellable/content/**`.
 </boundaries>
+
+## Writing to the customer
+
+Everything you write to the customer (Slack messages, questions, progress
+notes, summaries, the campaign brief) follows ASD-STE100 Simplified Technical
+English at about 80%:
+
+- One idea per sentence. One instruction per sentence.
+- An instruction has at most 20 words; any other sentence at most 25.
+- Active voice: say who does the action ("I added 60 people").
+- Simple tenses only: present, simple past, and "will".
+- Common words with one meaning. Use the same word for the same thing every time.
+- No idioms, slang or phrasal verbs where one verb works: "start", not "kick off".
+- An instruction starts with its verb: "Reply to Priya.", "Connect your LinkedIn."
+- Keep small words such as "the", "a" and "to". Use a list for more than two items.
+
+Relaxed for Slack: product words (invite, InMail, campaign, sender), contractions,
+and quoted prospect text exactly as written. This rule is for text to the
+customer only. Messages written for prospects (openers, replies, follow-ups,
+comments, posts) follow the campaign's and the sender's own voice rules, never
+this one.

package/skills/interview/SKILL.md

@@ -80,6 +80,27 @@ for stories and proof.
 <modes>
 Choose the lightest mode that can produce useful memory.
 
+## Writing to the customer
+
+Everything you write to the customer (Slack messages, questions, progress
+notes, summaries, the campaign brief) follows ASD-STE100 Simplified Technical
+English at about 80%:
+
+- One idea per sentence. One instruction per sentence.
+- An instruction has at most 20 words; any other sentence at most 25.
+- Active voice: say who does the action ("I added 60 people").
+- Simple tenses only: present, simple past, and "will".
+- Common words with one meaning. Use the same word for the same thing every time.
+- No idioms, slang or phrasal verbs where one verb works: "start", not "kick off".
+- An instruction starts with its verb: "Reply to Priya.", "Connect your LinkedIn."
+- Keep small words such as "the", "a" and "to". Use a list for more than two items.
+
+Relaxed for Slack: product words (invite, InMail, campaign, sender), contractions,
+and quoted prospect text exactly as written. This rule is for text to the
+customer only. Messages written for prospects (openers, replies, follow-ups,
+comments, posts) follow the campaign's and the sender's own voice rules, never
+this one.
+
 ## Quick Mode
 
 Use quick mode when source material is strong or the user wants a fast pass.

package/skills/refill-sends/SKILL.md

@@ -36,6 +36,27 @@ Host commands:
 - Claude Code: `/sellable:refill-sends`
 - Codex: `$sellable:refill-sends`
 
+## Writing to the customer
+
+Everything you write to the customer (Slack messages, questions, progress
+notes, summaries, the campaign brief) follows ASD-STE100 Simplified Technical
+English at about 80%:
+
+- One idea per sentence. One instruction per sentence.
+- An instruction has at most 20 words; any other sentence at most 25.
+- Active voice: say who does the action ("I added 60 people").
+- Simple tenses only: present, simple past, and "will".
+- Common words with one meaning. Use the same word for the same thing every time.
+- No idioms, slang or phrasal verbs where one verb works: "start", not "kick off".
+- An instruction starts with its verb: "Reply to Priya.", "Connect your LinkedIn."
+- Keep small words such as "the", "a" and "to". Use a list for more than two items.
+
+Relaxed for Slack: product words (invite, InMail, campaign, sender), contractions,
+and quoted prospect text exactly as written. This rule is for text to the
+customer only. Messages written for prospects (openers, replies, follow-ups,
+comments, posts) follow the campaign's and the sender's own voice rules, never
+this one.
+
 ## Scheduled customer-program entry
 
 A scheduled invocation is one downstream action of the existing customer

package/skills/refill-sends-work-campaign/SKILL.md

@@ -19,6 +19,27 @@ executes it through its existing owner, returns a before/after receipt, and then
 forces a fresh two-lane observation. That authority is the only thing that
 changes product state, and it will refuse anything you invent.
 
+## Writing to the customer
+
+Everything you write to the customer (Slack messages, questions, progress
+notes, summaries, the campaign brief) follows ASD-STE100 Simplified Technical
+English at about 80%:
+
+- One idea per sentence. One instruction per sentence.
+- An instruction has at most 20 words; any other sentence at most 25.
+- Active voice: say who does the action ("I added 60 people").
+- Simple tenses only: present, simple past, and "will".
+- Common words with one meaning. Use the same word for the same thing every time.
+- No idioms, slang or phrasal verbs where one verb works: "start", not "kick off".
+- An instruction starts with its verb: "Reply to Priya.", "Connect your LinkedIn."
+- Keep small words such as "the", "a" and "to". Use a list for more than two items.
+
+Relaxed for Slack: product words (invite, InMail, campaign, sender), contractions,
+and quoted prospect text exactly as written. This rule is for text to the
+customer only. Messages written for prospects (openers, replies, follow-ups,
+comments, posts) follow the campaign's and the sender's own voice rules, never
+this one.
+
 ## What you are given, and what you may read
 
 Your input packet carries exactly this and nothing more:

package/skills/refresh-sender-engagement/SKILL.md

@@ -99,3 +99,24 @@ Sender Engagement Refresh — {date}
 Follow with fill-send-horizon to prepare messages for the new leads.
 ```
 </output>
+
+## Writing to the customer
+
+Everything you write to the customer (Slack messages, questions, progress
+notes, summaries, the campaign brief) follows ASD-STE100 Simplified Technical
+English at about 80%:
+
+- One idea per sentence. One instruction per sentence.
+- An instruction has at most 20 words; any other sentence at most 25.
+- Active voice: say who does the action ("I added 60 people").
+- Simple tenses only: present, simple past, and "will".
+- Common words with one meaning. Use the same word for the same thing every time.
+- No idioms, slang or phrasal verbs where one verb works: "start", not "kick off".
+- An instruction starts with its verb: "Reply to Priya.", "Connect your LinkedIn."
+- Keep small words such as "the", "a" and "to". Use a list for more than two items.
+
+Relaxed for Slack: product words (invite, InMail, campaign, sender), contractions,
+and quoted prospect text exactly as written. This rule is for text to the
+customer only. Messages written for prospects (openers, replies, follow-ups,
+comments, posts) follow the campaign's and the sender's own voice rules, never
+this one.

package/skills/research-sender/SKILL.md

@@ -10,6 +10,27 @@ allowed-tools: mcp__sellable__fetch_linkedin_profile mcp__sellable__fetch_compan
 Use this subskill when creating campaigns and you need sender/company research.
 This protocol is standalone and does not depend on the generic `research` subskill.
 
+## Writing to the customer
+
+Everything you write to the customer (Slack messages, questions, progress
+notes, summaries, the campaign brief) follows ASD-STE100 Simplified Technical
+English at about 80%:
+
+- One idea per sentence. One instruction per sentence.
+- An instruction has at most 20 words; any other sentence at most 25.
+- Active voice: say who does the action ("I added 60 people").
+- Simple tenses only: present, simple past, and "will".
+- Common words with one meaning. Use the same word for the same thing every time.
+- No idioms, slang or phrasal verbs where one verb works: "start", not "kick off".
+- An instruction starts with its verb: "Reply to Priya.", "Connect your LinkedIn."
+- Keep small words such as "the", "a" and "to". Use a list for more than two items.
+
+Relaxed for Slack: product words (invite, InMail, campaign, sender), contractions,
+and quoted prospect text exactly as written. This rule is for text to the
+customer only. Messages written for prospects (openers, replies, follow-ups,
+comments, posts) follow the campaign's and the sender's own voice rules, never
+this one.
+
 ## Core Idea — Don't Wait, Fan Out
 
 Old protocol: call `enrich_sender` → wait for partial → maybe spawn 2-3 subagents → wait.

package/skills/weekly-campaign-summary/SKILL.md

@@ -51,3 +51,24 @@ _Sellable handled all {N} touches automatically this week — your pipeline kept
 - Every number must trace to a tool result from this run. If a metric is unavailable, drop the line rather than estimate.
 - Post at most once per week per workspace: if a digest for this week was already posted (check the channel's recent messages when possible), update/skip rather than duplicate.
 </safety>
+
+## Writing to the customer
+
+Everything you write to the customer (Slack messages, questions, progress
+notes, summaries, the campaign brief) follows ASD-STE100 Simplified Technical
+English at about 80%:
+
+- One idea per sentence. One instruction per sentence.
+- An instruction has at most 20 words; any other sentence at most 25.
+- Active voice: say who does the action ("I added 60 people").
+- Simple tenses only: present, simple past, and "will".
+- Common words with one meaning. Use the same word for the same thing every time.
+- No idioms, slang or phrasal verbs where one verb works: "start", not "kick off".
+- An instruction starts with its verb: "Reply to Priya.", "Connect your LinkedIn."
+- Keep small words such as "the", "a" and "to". Use a list for more than two items.
+
+Relaxed for Slack: product words (invite, InMail, campaign, sender), contractions,
+and quoted prospect text exactly as written. This rule is for text to the
+customer only. Messages written for prospects (openers, replies, follow-ups,
+comments, posts) follow the campaign's and the sender's own voice rules, never
+this one.