@sellable/mcp 0.1.273 → 0.1.275

package/dist/tools/prompts.d.ts

@@ -135,7 +135,7 @@ export interface PostFindLeadsScoutRegistryResponse {
 }
 export declare const DEFAULT_SUBSKILL_PROMPT_CHUNK_CHARS = 48000;
 export declare const MAX_SUBSKILL_PROMPT_CHUNK_CHARS = 48000;
-export declare const ALLOWED_SUBSKILL_PROMPT_NAMES: readonly ["building-gtm-tables", "content", "create-campaign", "create-campaign-brief", "create-campaign-v2", "create-campaign-v2-tail", "create-campaign-v2-validation", "create-post", "create-rubric", "engage", "enrich-prospects", "find-leads", "foundation", "generate-messages", "interview", "load-voice", "research", "research-prospect", "research-sender", "workflow-sequences"];
+export declare const ALLOWED_SUBSKILL_PROMPT_NAMES: readonly ["building-gtm-tables", "content", "create-ab-test", "create-campaign", "create-campaign-brief", "create-campaign-v2", "create-campaign-v2-tail", "create-campaign-v2-validation", "create-post", "create-rubric", "engage", "enrich-prospects", "find-leads", "foundation", "generate-messages", "interview", "load-voice", "research", "research-prospect", "research-sender", "workflow-sequences"];
 export declare const promptToolDefinitions: ({
     name: string;
     description: string;
@@ -179,7 +179,7 @@ export declare const promptToolDefinitions: ({
         properties: {
             subskillName: {
                 type: string;
-                enum: readonly ["building-gtm-tables", "content", "create-campaign", "create-campaign-brief", "create-campaign-v2", "create-campaign-v2-tail", "create-campaign-v2-validation", "create-post", "create-rubric", "engage", "enrich-prospects", "find-leads", "foundation", "generate-messages", "interview", "load-voice", "research", "research-prospect", "research-sender", "workflow-sequences"];
+                enum: readonly ["building-gtm-tables", "content", "create-ab-test", "create-campaign", "create-campaign-brief", "create-campaign-v2", "create-campaign-v2-tail", "create-campaign-v2-validation", "create-post", "create-rubric", "engage", "enrich-prospects", "find-leads", "foundation", "generate-messages", "interview", "load-voice", "research", "research-prospect", "research-sender", "workflow-sequences"];
                 description: string;
             };
             offset: {
@@ -214,7 +214,7 @@ export declare const promptToolDefinitions: ({
         properties: {
             subskillName: {
                 type: string;
-                enum: readonly ["building-gtm-tables", "content", "create-campaign", "create-campaign-brief", "create-campaign-v2", "create-campaign-v2-tail", "create-campaign-v2-validation", "create-post", "create-rubric", "engage", "enrich-prospects", "find-leads", "foundation", "generate-messages", "interview", "load-voice", "research", "research-prospect", "research-sender", "workflow-sequences"];
+                enum: readonly ["building-gtm-tables", "content", "create-ab-test", "create-campaign", "create-campaign-brief", "create-campaign-v2", "create-campaign-v2-tail", "create-campaign-v2-validation", "create-post", "create-rubric", "engage", "enrich-prospects", "find-leads", "foundation", "generate-messages", "interview", "load-voice", "research", "research-prospect", "research-sender", "workflow-sequences"];
                 description: string;
             };
             assetPath: {

package/dist/tools/prompts.js

@@ -19,6 +19,7 @@ const DEPRECATED_SUBSKILL_PROMPT_REPLACEMENTS = {
 export const ALLOWED_SUBSKILL_PROMPT_NAMES = [
     "building-gtm-tables",
     "content",
+    "create-ab-test",
     "create-campaign",
     "create-campaign-brief",
     "create-campaign-v2",

package/dist/tools/registry.d.ts

@@ -225,7 +225,7 @@ export declare const allTools: ({
         properties: {
             subskillName: {
                 type: string;
-                enum: readonly ["building-gtm-tables", "content", "create-campaign", "create-campaign-brief", "create-campaign-v2", "create-campaign-v2-tail", "create-campaign-v2-validation", "create-post", "create-rubric", "engage", "enrich-prospects", "find-leads", "foundation", "generate-messages", "interview", "load-voice", "research", "research-prospect", "research-sender", "workflow-sequences"];
+                enum: readonly ["building-gtm-tables", "content", "create-ab-test", "create-campaign", "create-campaign-brief", "create-campaign-v2", "create-campaign-v2-tail", "create-campaign-v2-validation", "create-post", "create-rubric", "engage", "enrich-prospects", "find-leads", "foundation", "generate-messages", "interview", "load-voice", "research", "research-prospect", "research-sender", "workflow-sequences"];
                 description: string;
             };
             offset: {
@@ -260,7 +260,7 @@ export declare const allTools: ({
         properties: {
             subskillName: {
                 type: string;
-                enum: readonly ["building-gtm-tables", "content", "create-campaign", "create-campaign-brief", "create-campaign-v2", "create-campaign-v2-tail", "create-campaign-v2-validation", "create-post", "create-rubric", "engage", "enrich-prospects", "find-leads", "foundation", "generate-messages", "interview", "load-voice", "research", "research-prospect", "research-sender", "workflow-sequences"];
+                enum: readonly ["building-gtm-tables", "content", "create-ab-test", "create-campaign", "create-campaign-brief", "create-campaign-v2", "create-campaign-v2-tail", "create-campaign-v2-validation", "create-post", "create-rubric", "engage", "enrich-prospects", "find-leads", "foundation", "generate-messages", "interview", "load-voice", "research", "research-prospect", "research-sender", "workflow-sequences"];
                 description: string;
             };
             assetPath: {
@@ -1140,6 +1140,62 @@ export declare const allTools: ({
         required: string[];
         additionalProperties?: undefined;
     };
+} | {
+    name: string;
+    description: string;
+    inputSchema: {
+        type: string;
+        properties: {
+            sourceCampaignId: {
+                type: string;
+                description: string;
+            };
+            variantName: {
+                type: string;
+                description: string;
+            };
+            variantBriefDelta: {
+                type: string;
+                description: string;
+            };
+            variantALabel: {
+                type: string;
+                description: string;
+            };
+            variantABriefDelta: {
+                type: string;
+                description: string;
+            };
+            splitStrategy: {
+                type: string;
+                enum: string[];
+                description: string;
+            };
+            targetCounts: {
+                type: string;
+                properties: {
+                    a: {
+                        type: string;
+                    };
+                    b: {
+                        type: string;
+                    };
+                };
+                additionalProperties: boolean;
+                description: string;
+            };
+            dryRun: {
+                type: string;
+                description: string;
+            };
+            idempotencyKey: {
+                type: string;
+                description: string;
+            };
+        };
+        required: string[];
+        additionalProperties: boolean;
+    };
 } | {
     name: string;
     description: string;
@@ -1956,6 +2012,53 @@ export declare const allTools: ({
         };
         required: never[];
     };
+} | {
+    name: string;
+    description: string;
+    inputSchema: {
+        type: string;
+        properties: {
+            searchToken: {
+                type: string;
+                description: string;
+            };
+            selectedJobIds: {
+                type: string;
+                items: {
+                    type: string;
+                };
+                description: string;
+            };
+            name: {
+                type: string;
+            };
+            outputDir: {
+                type: string;
+                description: string;
+            };
+            fileBaseName: {
+                type: string;
+                description: string;
+            };
+            search?: undefined;
+            searches?: undefined;
+            location?: undefined;
+            geoId?: undefined;
+            postedLimit?: undefined;
+            sortBy?: undefined;
+            workplaceType?: undefined;
+            employmentType?: undefined;
+            experienceLevel?: undefined;
+            easyApply?: undefined;
+            under10Applicants?: undefined;
+            salary?: undefined;
+            pages?: undefined;
+            maxRows?: undefined;
+            artifactFormat?: undefined;
+        };
+        required: string[];
+        additionalProperties: boolean;
+    };
 } | {
     name: string;
     description: string;

package/dist/tools/registry.js

@@ -2,6 +2,7 @@ import { authToolDefinitions } from "./auth.js";
 import { blueprintCommitToolDefinitions } from "./blueprint-commit.js";
 import { bootstrapToolDefinitions } from "./bootstrap.js";
 import { campaignToolDefinitions } from "./campaigns.js";
+import { campaignAbTestToolDefinitions } from "./campaign-ab-test.js";
 import { campaignProcessingToolDefinitions } from "./campaign-processing.js";
 import { cellToolDefinitions } from "./cells.js";
 import { startCliLoginToolDef, waitForCliLoginToolDef } from "./cli-login.js";
@@ -14,6 +15,7 @@ import { engageMemoryToolDefinitions } from "./engage-memory.js";
 import { engageStateToolDefinitions } from "./engage-state.js";
 import { enrichmentToolDefinitions } from "./enrichment.js";
 import { frameworkToolDefinitions } from "./framework.js";
+import { harvestJobToolDefinitions } from "./harvest-jobs.js";
 import { leadToolDefinitions } from "./leads.js";
 import { linkedinToolDefinitions } from "./linkedin.js";
 import { navigationToolDefinitions } from "./navigation.js";
@@ -30,6 +32,7 @@ import { verifyRowToolDefinitions } from "./verify-row.js";
 import { workspaceToolDefinitions } from "./workspaces.js";
 export const allTools = [
     ...campaignToolDefinitions,
+    ...campaignAbTestToolDefinitions,
     ...campaignProcessingToolDefinitions,
     ...authToolDefinitions,
     startCliLoginToolDef,
@@ -43,6 +46,7 @@ export const allTools = [
     ...contentPostToolDefinitions,
     ...navigationToolDefinitions,
     ...leadToolDefinitions,
+    ...harvestJobToolDefinitions,
     ...enrichmentToolDefinitions,
     ...processingToolDefinitions,
     ...rubricToolDefinitions,

package/package.json

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

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

@@ -0,0 +1,77 @@
+---
+name: create-ab-test
+description: Create a Sellable campaign A/B test from a clean source lead list.
+visibility: public
+allowed-tools:
+  - mcp__sellable__get_auth_status
+  - mcp__sellable__get_active_workspace
+  - mcp__sellable__get_campaign
+  - mcp__sellable__get_campaign_context
+  - mcp__sellable__get_campaign_navigation_state
+  - mcp__sellable__get_campaign_messages_preview
+  - mcp__sellable__prepare_campaign_ab_test
+  - mcp__sellable__load_csv_linkedin_leads
+  - mcp__sellable__wait_for_lead_list_ready
+  - mcp__sellable__get_table_rows
+  - mcp__sellable__get_rows_minimal
+---
+
+# Sellable Create A/B Test
+
+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.
+
+## Opening Contract
+
+Start by identifying the source campaign, the one variable being tested, and
+the clean source lead origin. Then prepare the split and stop for review. The
+goal is two review-copy campaigns with clean split source lists, not a launched
+campaign.
+
+## Required Flow
+
+1. Confirm the source campaign ID or resolve it with `get_campaign`.
+2. Confirm the A/B variable in plain language. Keep variant B as the explicit
+   change and leave variant A as the control unless the user names an A change.
+3. Verify the campaign has a clean source lead list. A clean source list is a
+   lead-list table, not the generated campaign workflow table.
+4. Call `prepare_campaign_ab_test` with `dryRun: true` first.
+5. Review split counts, duplicate/skipped counts, campaign names, and variant
+   brief deltas with the user.
+6. Only after review, call `prepare_campaign_ab_test` without `dryRun` using the
+   same `idempotencyKey` if one was returned or supplied.
+7. Return the A and B campaign IDs, split lead-list IDs, counts, and the
+   explicit note that both campaigns are `not_started`.
+
+## Anti-Patterns
+
+- Do not call `export_table_csv` from an enriched/generated campaign workflow
+  table as the lead source for A/B splitting.
+- Do not reimport workflow output columns such as `ICP Score`, `Passes Rubric`,
+  `Generate Message`, `Message`, `Approved`, scheduling, status, result, or
+  error columns.
+- Do not use broad workflow-table selectors to split decorated campaign rows.
+- Do not call `start_campaign`, approve launch, attach senders for launch, or
+  trigger live sends in this workflow.
+
+## Clean Source Fallback
+
+If the source campaign has no clean source lead list, or the source list is
+polluted with workflow/output columns, ask for the original CSV or clean source
+list. Use `load_csv_linkedin_leads`; it strips Sellable workflow columns if a
+contaminated CSV is supplied, then creates a clean lead list. After the clean
+source is confirmed, retry `prepare_campaign_ab_test`.
+
+## Output Contract
+
+Report:
+
+- source campaign ID
+- source lead-list ID
+- split strategy and counts
+- duplicate/skipped lead counts
+- A review campaign ID and split lead-list ID
+- B review campaign ID and split lead-list ID
+- variant difference
+- `launchState: not_started` for both campaigns

package/skills/create-campaign/SKILL.md

@@ -29,6 +29,8 @@ allowed-tools:
   - mcp__sellable__search_prospeo
   - mcp__sellable__search_prospeo_companies
   - mcp__sellable__confirm_prospeo_company_accounts
+  - mcp__sellable__search_harvest_jobs
+  - mcp__sellable__confirm_harvest_job_companies
   - mcp__sellable__search_signals
   - mcp__sellable__fetch_post_engagers
   - mcp__sellable__enrich_with_prospeo
@@ -107,6 +109,22 @@ page before importing, call `list_dnc_entries`. Confirm the active workspace
 name and ID in the response before any write. This is Sellable's workspace DNC
 list used by DNC Check.
 
+## A/B Campaign Requests
+
+If the user explicitly asks to create an A/B test, split an existing campaign
+into variants, duplicate a campaign for copy testing, or compare two campaign
+message approaches from the same source list, route them to
+`create-ab-test` instead of improvising inside this create-campaign workflow.
+
+Workflow/campaign table exports are decorated outputs for operator review and
+debugging. They are not source lead lists for A/B splitting or campaign
+duplication. Do not use `export_table_csv` from an enriched/generated campaign
+table and then reimport it as leads. If the user only has a contaminated CSV,
+`load_csv_linkedin_leads` strips Sellable workflow columns such as `ICP Score`,
+`Passes Rubric`, `Generate Message`, `Message`, and `Approved`, but the
+preferred A/B path is the dedicated `create-ab-test` workflow using
+`prepare_campaign_ab_test`.
+
 ## Opening Turn Contract
 
 On the first visible response after this skill is invoked, do not narrate
@@ -227,6 +245,14 @@ are likely. Sales Nav is useful for recent LinkedIn activity, role/title
 precision, and referral paths, but it does not provide hiring-by-role filters;
 say that distinction plainly in the source-plan gate.
 
+When the brief asks for current LinkedIn job-post intent, such as companies
+hiring Power BI developers this month, use Harvest jobs as the account source:
+`search_harvest_jobs -> confirm_harvest_job_companies -> search_prospeo`.
+First write and review the Harvest job artifact. Then confirm selected Harvest
+job IDs into a `domainFilterId`; Prospeo remains the people-search provider.
+Do not paste LinkedIn company URLs as domains. Do not fetch full job details for
+every search row by default; selected batches only.
+
 For company lookalikes, best-customer lookalikes, "companies like X",
 lookalike accounts, companies that use AI, companies with API/SSO/Chrome
 extension, news/award/integration/key-customer filters, or account discovery

package/skills/create-campaign/core/providers/prospeo.json

@@ -7,6 +7,8 @@
   "requiredTools": [
     "update_campaign",
     "get_provider_prompt",
+    "search_harvest_jobs",
+    "confirm_harvest_job_companies",
     "search_prospeo_companies",
     "confirm_prospeo_company_accounts",
     "search_prospeo",
@@ -24,13 +26,14 @@
     "useWhen": [
       "You want Prospeo filters or domain-based search",
       "You need company lookalike account discovery before finding people",
+      "You need current LinkedIn job-post evidence before finding hiring stakeholders",
       "You want companies like X, target-domain, best-customer/top-customer, or job-search employer lookalikes, or accounts using AI/API/SSO/Chrome extensions",
       "You need companies hiring for specific roles using job-posting filters",
       "You need high deliverability from Prospeo"
     ],
     "avoidWhen": ["You need LinkedIn activity filters"],
-    "reason": "Strong for hiring-led search, company/account lookalikes, Prospeo-specific filters, verified contacts, and domain lists.",
-    "prose": "Since you're targeting **{icp}**, I'd recommend **Prospeo**.\n\nHere's why:\n- Prospeo can discover lookalike accounts first, then turn approved accounts into a domainFilterId for people search\n- Prospeo can filter for companies hiring specific roles with job-posting filters\n- We can pair those company signals with buyer/referrer titles and verified-contact coverage\n\nFor lookalike accounts, I will show an account sample first; those account rows are not people leads yet. After approval, I will use the companySearchToken to confirm the accounts, then search people at the returned domainFilterId. For outbound lookalikes, I will use target/account/customer domains or verified past-customer accounts, not the sender's company. For job-search/application lookalikes, I can use current or past employers as existing-company seeds.\n\nShould I search Prospeo for {icp}?"
+    "reason": "Strong for hiring-led search, current LinkedIn job-post account sourcing, company/account lookalikes, Prospeo-specific filters, verified contacts, and domain lists.",
+    "prose": "Since you're targeting **{icp}**, I'd recommend **Prospeo**.\n\nHere's why:\n- Prospeo can discover lookalike accounts first, then turn approved accounts into a domainFilterId for people search\n- Harvest job search can source companies from current LinkedIn job posts, then confirm selected jobs into a domainFilterId for Prospeo people search\n- Prospeo can filter for companies hiring specific roles with job-posting filters\n- We can pair those company signals with buyer/referrer titles and verified-contact coverage\n\nFor current LinkedIn job-post evidence, I will use search_harvest_jobs -> confirm_harvest_job_companies -> search_prospeo. I will not paste LinkedIn company URLs as domains, and I will only fetch job details for selected batches. For lookalike accounts, I will show an account sample first; those account rows are not people leads yet. After approval, I will use the companySearchToken to confirm the accounts, then search people at the returned domainFilterId. For outbound lookalikes, I will use target/account/customer domains or verified past-customer accounts, not the sender's company. For job-search/application lookalikes, I can use current or past employers as existing-company seeds.\n\nShould I search Prospeo for {icp}?"
   },
   "askOption": {
     "label": "Prospeo",

package/skills/generate-messages/SKILL.md

@@ -761,6 +761,15 @@ help...` or `built for [buyer] to...`. Do not overuse generic solved-state
   bridges like `there's a way to...`; they read informercial when they imply
   the buyer's problem is now solved before the product or artifact has earned
   that claim.
+- run a contraction naturalness pass on the buyer-facing copy before selecting
+  the winner. Use common contractions when they make the message sound like a
+  human LinkedIn note: `it is` -> `it's`, `does not` -> `doesn't`, `do not` ->
+  `don't`, `cannot` -> `can't`, `we are` -> `we're`, `I am` -> `I'm`, and
+  `you are` -> `you're`. Keep the uncontracted form only when emphasis,
+  grammar, token boundaries, legal/technical clarity, or a deliberate formal
+  voice requires it. Do not create awkward noun contractions like
+  `outbound's becoming`. If selected copy contains stiff helper-verb phrasing
+  such as `It is knowing...`, rewrite it before approval.
 - do not let the first substantive line become a generic problem-solved
   promise. Openers shaped like `there's a way to stop/fix/solve [problem]`
   are BLOCKED when they sound like an ad, imply the problem is already
@@ -2633,6 +2642,7 @@ hiring for`
 - Best PS / no-PS decision: Candidate [A|B|C] — reason
 - Element edits made by finalizer: ...
 - Parallel action formatting: bullets used | paragraphs kept | not applicable — reason
+- Contraction naturalness: PASS | BLOCKED — reason
 - Style consistency check: PASS | BLOCKED — reason
 - Assembly note: clean combination or one candidate swept
 

package/skills/providers/prospeo.md

@@ -9,10 +9,31 @@ Prospeo supports search + import in the campaign builder flow.
 ## Provider Decision Tree
 
 - Known account list or CSV: use `load_csv_domains` or `save_domain_filters`, then `search_prospeo`.
+- Current LinkedIn job-post intent: use `search_harvest_jobs`, review the job artifact, then use `confirm_harvest_job_companies` with selected Harvest job IDs to create a `domainFilterId`; only then call `search_prospeo` for hiring stakeholders at those companies. Harvest jobs are the account source, not a people-search replacement.
 - Company/account lookalikes: use `search_prospeo_companies`, review the account sample, then use `confirm_prospeo_company_accounts` with the returned `companySearchToken` to create a `domainFilterId`; only then call `search_prospeo` for people at those accounts. Account rows are not people leads yet.
 - Person search with known filters: use `search_prospeo` directly.
 - LinkedIn activity, content-source, or post-engagement intent: stay on Signal Discovery or Sales Nav, not Prospeo.
 
+Current LinkedIn job-post account sourcing must follow:
+
+```text
+search_harvest_jobs -> confirm_harvest_job_companies -> search_prospeo
+```
+
+Use `search_harvest_jobs` when the user's account-source intent is current
+LinkedIn job posts, for example "companies hiring Power BI developers in the US
+this month." The search tool writes review artifacts and returns a token or
+`mcp-harvest-job-search-token:*` reference. After reviewing selected jobs, call
+`confirm_harvest_job_companies` with selected Harvest job IDs only. It resolves
+real company website domains from selected job details and bounded
+`/linkedin/company` fallback, then returns a `domainFilterId` for
+`search_prospeo`.
+
+Do not paste LinkedIn company URLs as domains. Do not detail-fetch every job row
+by default; fetch details only for selected batches during confirmation. Use
+Prospeo directly when the user wants broader volume, company attributes,
+lookalikes, or people search without needing current LinkedIn job evidence.
+
 Company/account lookalikes must follow:
 
 ```text

package/skills/research/config.json

@@ -1,9 +0,0 @@
-{
-  "parallelMode": "wide",
-  "agentCount": 6,
-  "maxToolCallsPerAgent": 2,
-  "senderMaxAgents": 2,
-  "senderMaxToolCallsPerAgent": 3,
-  "progressMode": true,
-  "debugMode": true
-}