@sellable/install 0.1.198 → 0.1.200

package/bin/sellable-install.mjs

@@ -31,7 +31,7 @@ function getInstallVersion() {
   }
 }
 
-const CODEX_PLUGIN_VERSION = "0.1.41";
+const CODEX_PLUGIN_VERSION = "0.1.42";
 const CODEX_PLUGIN_COMPAT_VERSIONS = [
   "0.1.8",
   "0.1.9",
@@ -65,6 +65,8 @@ const CODEX_PLUGIN_COMPAT_VERSIONS = [
   "0.1.37",
   "0.1.38",
   "0.1.39",
+  "0.1.40",
+  "0.1.41",
 ];
 const INSTALL_PACKAGE_SPEC =
   process.env.SELLABLE_INSTALL_PACKAGE_SPEC || "@sellable/install@latest";
@@ -620,9 +622,9 @@ const CREATE_CAMPAIGN_ALLOWED_TOOLS = [
   "mcp__sellable__select_campaign_cells",
   "mcp__sellable__queue_campaign_cells",
   "mcp__sellable__wait_for_campaign_processing",
-  "mcp__sellable__start_prepare_campaign_messages",
-  "mcp__sellable__get_prepare_campaign_messages_status",
-  "mcp__sellable__cancel_prepare_campaign_messages",
+  "mcp__sellable__start_campaign_message_preparation",
+  "mcp__sellable__get_campaign_message_preparation_status",
+  "mcp__sellable__cancel_campaign_message_preparation",
   "mcp__sellable__revise_message_template_and_rerun",
   "mcp__sellable__update_campaign_brief",
   "mcp__sellable__update_campaign",
@@ -651,6 +653,13 @@ function allowedToolsYaml(tools) {
   return tools.map((tool) => `  - ${tool}`).join("\n");
 }
 
+function yamlString(value) {
+  return JSON.stringify(String(value));
+}
+
+const FOUNDATION_SKILL_DESCRIPTION =
+  "Build or update durable founder/company memory: voice, values, proof, stories, positioning, and writing rules.";
+
 function codexSkillOpenAiYaml(displayName, description) {
   return `interface:
   display_name: "${displayName.replaceAll('"', '\\"')}"
@@ -1238,7 +1247,7 @@ Use \`prepare_campaign_ab_test\` to create clean A/B split lead lists and review
 function genericSellableSkillMd({ name, title, description }) {
   return `---
 name: ${name}
-description: ${description}
+description: ${yamlString(description)}
 allowed-tools:
   - mcp__sellable__get_auth_status
   - mcp__sellable__get_subskill_prompt
@@ -1277,7 +1286,7 @@ If subskill lookup fails, use \`mcp__sellable__search_subskill_prompts({ query:
 function foundationSkillMd() {
   return `---
 name: foundation
-description: Build or update durable founder/company memory: voice, values, proof, stories, positioning, and writing rules.
+description: ${yamlString(FOUNDATION_SKILL_DESCRIPTION)}
 allowed-tools:
   - mcp__sellable__get_subskill_prompt
   - mcp__sellable__get_subskill_asset

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sellable/install",
-  "version": "0.1.198",
+  "version": "0.1.200",
   "type": "module",
   "description": "One-command installer for Sellable MCP in Claude Code and Codex",
   "bin": {

package/skill-templates/create-ab-test.md

@@ -4,26 +4,71 @@ description: Create a Sellable campaign A/B test by duplicating a full Campaign
 visibility: public
 allowed-tools:
   - mcp__sellable__get_auth_status
+  - mcp__sellable__start_cli_login
+  - mcp__sellable__wait_for_cli_login
   - mcp__sellable__bootstrap_create_campaign
   - mcp__sellable__get_subskill_prompt
   - mcp__sellable__get_subskill_asset
+  - mcp__sellable__search_subskill_prompts
+  - mcp__sellable__get_provider_prompt
+  - mcp__sellable__get_source_scout_registry
+  - mcp__sellable__get_post_find_leads_scout_registry
   - mcp__sellable__get_active_workspace
+  - mcp__sellable__list_workspaces
+  - mcp__sellable__set_active_workspace
+  - mcp__sellable__list_senders
+  - mcp__sellable__get_sender
   - mcp__sellable__fetch_linkedin_profile
+  - mcp__sellable__fetch_linkedin_posts
+  - mcp__sellable__get_linkedin_profile
+  - mcp__sellable__fetch_company
+  - mcp__sellable__fetch_company_posts
   - mcp__sellable__complete_sender_research
+  - mcp__sellable__lookup_sales_nav_filter
+  - mcp__sellable__search_sales_nav
+  - 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
+  - mcp__sellable__bulk_enrich_with_prospeo
+  - mcp__sellable__save_domain_filters
+  - mcp__sellable__add_rubric_item
+  - mcp__sellable__upsert_rubric
+  - mcp__sellable__set_headline_icp_criteria
+  - mcp__sellable__check_rubric
   - mcp__sellable__create_campaign
   - mcp__sellable__update_campaign_brief
   - mcp__sellable__update_campaign
   - mcp__sellable__save_rubrics
   - mcp__sellable__get_campaign
   - mcp__sellable__get_campaign_context
+  - mcp__sellable__get_campaign_framework
   - mcp__sellable__get_campaign_navigation_state
   - mcp__sellable__get_campaign_messages_preview
+  - mcp__sellable__get_campaign_table_schema
+  - mcp__sellable__select_campaign_cells
+  - mcp__sellable__queue_campaign_cells
+  - mcp__sellable__wait_for_campaign_processing
+  - mcp__sellable__revise_message_template_and_rerun
+  - mcp__sellable__confirm_lead_list
+  - mcp__sellable__import_leads
   - mcp__sellable__duplicate_campaign
   - mcp__sellable__prepare_campaign_ab_test
+  - mcp__sellable__list_dnc_entries
+  - mcp__sellable__load_csv_dnc_entries
   - mcp__sellable__load_csv_linkedin_leads
+  - mcp__sellable__load_csv_domains
   - mcp__sellable__wait_for_lead_list_ready
+  - mcp__sellable__wait_for_campaign_table_ready
+  - mcp__sellable__get_rows
   - mcp__sellable__get_table_rows
   - mcp__sellable__get_rows_minimal
+  - mcp__sellable__attach_sequence
+  - mcp__sellable__attach_recommended_sequence
 ---
 
 # Sellable Create A/B Test
@@ -36,11 +81,13 @@ campaign-message approaches from the same source list.
 
 Start by identifying the campaign idea and the one variable being tested.
 Campaign A must be a real, fully prepared Sellable campaign before this A/B
-helper runs. If the user only supplied an idea, first run the normal
-`$sellable:create-campaign` flow for Campaign A: research the sender/company,
-create the campaign shell, build and approve the campaign brief, source or
-attach leads when appropriate, save any approved ICP filters, and get the
-message/template state into the campaign brief. Do not call
+helper runs. If the user only supplied an idea, this skill must first execute
+the normal `$sellable:create-campaign` workflow for Campaign A in the same run:
+bootstrap create-campaign, load `create-campaign-v2` and
+`core/flow.v2.json`, research the sender/company, create the campaign shell,
+build and approve the campaign brief, source or attach leads when appropriate,
+save any approved ICP filters, and get the message/template state into the
+campaign brief. Do not call
 `prepare_campaign_ab_test` with only `campaignName`/`campaignBrief`.
 
 Once Campaign A exists, the A/B step duplicates Campaign A through Sellable's
@@ -54,8 +101,11 @@ split lead list.
 1. Decide the source mode:
    - Existing Campaign A: confirm the source campaign ID or resolve it with
      `get_campaign`.
-   - Idea-only request: run the full `$sellable:create-campaign` workflow first,
-     then use the created campaign ID as `sourceCampaignId`.
+   - Idea-only request: run the full create-campaign workflow inline first,
+     through `bootstrap_create_campaign`, `get_subskill_prompt({
+     subskillName: "create-campaign-v2" })`, and `get_subskill_asset({
+     subskillName: "create-campaign-v2", assetPath: "core/flow.v2.json" })`.
+     Use the created campaign ID as `sourceCampaignId`.
 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. Inspect Campaign A with `get_campaign` and `get_campaign_context`. Confirm

package/skill-templates/create-campaign.md

@@ -46,9 +46,9 @@ allowed-tools:
   - mcp__sellable__select_campaign_cells
   - mcp__sellable__queue_campaign_cells
   - mcp__sellable__wait_for_campaign_processing
-  - mcp__sellable__start_prepare_campaign_messages
-  - mcp__sellable__get_prepare_campaign_messages_status
-  - mcp__sellable__cancel_prepare_campaign_messages
+  - mcp__sellable__start_campaign_message_preparation
+  - mcp__sellable__get_campaign_message_preparation_status
+  - mcp__sellable__cancel_campaign_message_preparation
   - mcp__sellable__revise_message_template_and_rerun
   - mcp__sellable__update_campaign_brief
   - mcp__sellable__update_campaign
@@ -92,18 +92,28 @@ When filters are chosen, save rubrics, get filter approval, then wait for
 message-template approval before enrichment/filtering or Generate Message cells.
 After filter approval, Filter Leads should show `Filters saved + waiting for
 message approval` until the template is approved.
-After message approval, use `start_prepare_campaign_messages` for target-ready
-message preparation such as "prepare 100 messages, checking up to 300 rows".
-Treat `campaignId` as `CampaignOffer.id`, keep the default
-`approvalMode:"mark_ready"` unless the user explicitly asks to flip Approved
-cells, and poll `get_prepare_campaign_messages_status` for checked rows,
-prepared/approved count, target, row budget remaining, and stop reason. Low
-level selector/queue tools are diagnostics and recovery only for this lane. If
-the user asks to stop preparation, the target is wrong, or status shows the
-wrong campaign/table, call `cancel_prepare_campaign_messages`; otherwise do not
-cancel a healthy prepare run.
-Never call `start_campaign` from Prepare Messages; final launch remains a
-separate explicit user greenlight.
+The default path stays the existing first campaign-table execution slice:
+review the normal `reviewBatchLimit:15`, approve reviewed draft rows, then move
+to Settings/sequence/final greenlight. Only call
+`start_campaign_message_preparation` when the user explicitly asks for more
+prepared messages or a send count. If the user says "prepare/generate X
+messages", set `targetPreparedMessages:X`, let the backend derive
+`maxRowsToCheck:min(2500,max(300,X*5))`, and keep
+`approvalMode:"mark_ready"`. The backend samples up to 100 rows first, then
+adapts later batches up to 250 rows while recalculating yield. Poll
+`get_campaign_message_preparation_status` for preparation-job status: checked
+rows, prepared/approved count, target, row budget remaining, and stop reason. If
+the user says "approve X messages", use `approvalMode:"approve"` but still do
+not launch. If the user says "schedule X sends", use `approvalMode:"approve"`
+to approve exactly the bounded X-message cohort during preparation, then
+continue through sender, sequence, and final launch greenlight; the launch path
+must verify that bounded cohort and must not broad approve-all.
+Treat `campaignId` as `CampaignOffer.id`. Low level selector/queue tools are
+diagnostics and recovery only for this lane. If the user asks to stop
+preparation, the target is wrong, or status shows the wrong campaign/table, call
+`cancel_campaign_message_preparation`; otherwise do not cancel a healthy prepare
+run. Never call `start_campaign` from message preparation; final launch remains
+a separate explicit user greenlight.
 Use Template is the default message path; AI Generated is only an explicit
 opt-out.