@sellable/mcp 0.1.9 → 0.1.11

package/README.md

@@ -83,14 +83,14 @@ The token is provided when you generate it. Use `list_workspaces` +
 For customer/package installs, use the public installer:
 
 ```bash
-npx -y @sellable/install@0.1.9 --host codex --token skt_live_your_token_here --workspace-id your_workspace_id
+npx -y @sellable/install@0.1.11 --host codex --token skt_live_your_token_here --workspace-id your_workspace_id
 ```
 
 If you already have `~/.sellable/config.json`, rerun/verify without rewriting
 auth:
 
 ```bash
-npx -y @sellable/install@0.1.9 --host codex
+npx -y @sellable/install@0.1.11 --host codex
 sellable --verify-only --host codex
 ```
 
@@ -146,6 +146,10 @@ panel" for structured questions, and keep implementation details out of normal
 customer-facing updates.
 Use `quick question panel` in customer-facing setup blockers.
 
+The Codex installer also writes compatibility cache aliases for recent plugin
+versions so stale Desktop skill links resolve to the current wrapper instead of
+showing file/version debugging to the user.
+
 ## Usage
 
 ### From Sellable UI

package/package.json

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

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

@@ -99,7 +99,8 @@ Validated draft directory:
 
   $sellable:create-campaign
 
-  After that, I’ll ask the 4 setup questions and start the campaign brief.
+  After that, I’ll confirm who we’re launching for, then ask the setup questions
+  and start the campaign brief.
   ```
 
   If they decline, tell them to switch to Plan/collaboration mode and rerun
@@ -111,16 +112,37 @@ Validated draft directory:
   question panel", "campaign brief", "lead sourcing", and "approval" instead of
   `request_user_input`, Default mode, MCP namespaces, plugin caches, prompt
   loading, runbooks, local skill files, or skill versions.
-- Before the first intake gate, use this customer-facing shape:
+- Do not treat the active Sellable workspace as the campaign subject. The
+  workspace only tells you where the campaign will be saved. Before buyer, CTA,
+  proof, or source questions, identify and confirm who the campaign is launching
+  for.
+- If the user supplied a LinkedIn profile, website, domain, company name, or
+  sender name in the invocation, do one lightweight lookup first:
+  - LinkedIn profile: call `fetch_linkedin_profile`.
+  - Website/domain/company: call `fetch_company` when possible, otherwise one
+    web lookup.
+  - Workspace sender id or known sender: call `get_sender` or `enrich_sender`.
+    Then summarize what you found in one or two lines and ask the user to confirm
+    the launch identity before continuing.
+- If the user did not provide the launch identity, make the first quick question
+  panel an identity gate. Ask who we are launching for, with options like:
+  1. `Use one of my connected Sellable senders`
+  2. `I’ll paste a LinkedIn profile`
+  3. `I’ll paste a company website/domain`
+  4. `Other / custom`
+     After that answer, do the lightweight lookup, confirm the company/sender
+     context, then ask the campaign setup questions. The setup questions should use
+     the confirmed company context so they do not feel generic. If identity is
+     still unavailable, use neutral/custom intake options instead of guessed
+     vertical-specific options.
+- Before the identity gate, use this customer-facing shape:
 
   ```text
   I’m ready to build the campaign in {workspace}.
 
-  First I’ll ask 4 quick setup questions:
-  1. who you want to target
-  2. what you want them to do
-  3. what proof or offer we should use
-  4. where we should source leads
+  First I need to confirm who we’re launching for. If you give me a LinkedIn
+  profile or company website, I’ll use that to understand the company, then I’ll
+  confirm it with you before we pick the target, offer, proof, and lead source.
 
   Then I’ll turn that into a campaign brief for you to approve before anything is created.
   ```
@@ -133,16 +155,17 @@ Validated draft directory:
   one lightweight identity lookup, then use the structured question gate. If the user
   supplied a company website/domain, call exactly one of `fetch_company`,
   `WebFetch`, or `WebSearch` to identify what the company actually does before
-  generating intake options. If the user supplied a LinkedIn profile URL, call
-  `fetch_linkedin_profile` before generating intake options. Do not infer the
-  product category from the company name alone. If no domain, website, or
-  LinkedIn profile is supplied, use neutral/custom intake options rather than
-  guessed vertical-specific options. Before the first structured question gate,
-  do not run sender research, `list_senders`, source discovery, Sales Nav, Prospeo,
+  generating setup options. If the user supplied a LinkedIn profile URL, call
+  `fetch_linkedin_profile` before generating setup options. Do not infer the
+  product category from the company name alone. If no domain, website, LinkedIn
+  profile, or sender identity is supplied, the first structured question gate
+  must ask for the launch identity before buyer/offer/source. Before that first
+  structured question gate, do not run source discovery, Sales Nav, Prospeo,
   Signals, Bash, Read, Write, Edit, Glob, Grep, full company research, or
   draft-directory inspection/creation. Do draft-directory setup only after the
-  founder answers. The first intake packet must ask buyer, offer/CTA, proof, and
-  lead source, and all four questions must include an `Other / custom` option.
+  founder answers. After launch identity is confirmed, the setup packet must ask
+  buyer, offer/CTA, proof, and lead source, and all four questions must include
+  an `Other / custom` option.
 - After the founder answers the first strategy/source packet, explain the next
   stage only: campaign brief creation and brief approval. Use this shape:
 

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

@@ -28,13 +28,14 @@ approval. Hide implementation details unless they are needed to unblock setup.
 The customer believes Sellable is helping them launch a campaign. Keep every
 turn anchored to that:
 
-1. Understand the campaign.
-2. Turn it into a campaign brief.
-3. Find likely responders.
-4. Filter for fit.
-5. Draft messages.
-6. Ask for approval.
-7. Create the campaign.
+1. Confirm who the campaign is launching for.
+2. Understand the company and offer.
+3. Turn that into a campaign brief.
+4. Find likely responders.
+5. Filter for fit.
+6. Draft messages.
+7. Ask for approval.
+8. Create the campaign.
 
 ## Progress Updates
 

package/skills/create-campaign-v2/core/flow.v2.json

@@ -97,8 +97,8 @@
       "onEnter": [
         {
           "action": "resolve_company_identity_before_strategy_packet",
-          "optional": true,
-          "when": "user_supplied_company_domain_website_or_linkedin_profile",
+          "optional": false,
+          "when": "before_founder_strategy_source_packet",
           "allowedTools": [
             "fetch_company",
             "fetch_linkedin_profile",
@@ -107,7 +107,7 @@
           ],
           "maxCalls": 1,
           "mustNotInferFromNameOnly": true,
-          "fallback": "use neutral/custom intake options when identity is unavailable"
+          "fallback": "ask identity gate first; use neutral/custom intake options only when identity remains unavailable"
         },
         {
           "action": "render_post_intake_progress_preamble",
@@ -161,6 +161,8 @@
         "get_subskill_prompt",
         "get_auth_status",
         "get_active_workspace",
+        "list_senders",
+        "get_sender",
         "enrich_sender",
         "complete_sender_research",
         "fetch_company",