@sellable/mcp 0.1.13 → 0.1.15

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.13 --host codex --token skt_live_your_token_here --workspace-id your_workspace_id
+npx -y @sellable/install@0.1.15 --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.13 --host codex
+npx -y @sellable/install@0.1.15 --host codex
 sellable --verify-only --host codex
 ```
 

package/package.json

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

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

@@ -129,7 +129,8 @@ Validated draft directory:
   once if available. This is a shortcut to deduce who the user might be from
   their Sellable API token and connected LinkedIn accounts. Do not present it as
   a sender picker yet. If there is one strong likely sender, use `enrich_sender`
-  to infer their current or most recent company, then ask:
+  to infer their current or most recent company, then ask a structured
+  confirmation question:
 
   ```text
   I’m ready to build this in {workspace}. I found {matched sender} connected here.
@@ -137,6 +138,34 @@ Validated draft directory:
   Is that you, and is this campaign for {company}?
   ```
 
+  The options must be:
+
+  1. `Yes, that's me and this is for {company}`
+  2. `That's me, but this is for a different company`
+  3. `No, I'll paste my LinkedIn URL so you can look me up`
+  4. `No, I'll paste the company website instead`
+  5. `Other / custom`
+
+  If the user chooses option 2, ask for the company website/domain and call
+  `fetch_company` when possible, otherwise one web lookup. If the user chooses
+  option 3, ask for their LinkedIn URL, call `fetch_linkedin_profile`, infer
+  their current or most recent company, then confirm company and sender again.
+  If the user chooses option 4, ask for the company website/domain, call
+  `fetch_company` when possible, otherwise one web lookup, then ask who the
+  LinkedIn messages should send from.
+
+  If `list_senders` returns zero connected senders, avoid the sender-confirmation
+  branch entirely. Ask for the user's LinkedIn URL or the company they want to
+  send on behalf of so you can research context:
+
+  ```text
+  I’m ready to build this in {workspace}.
+
+  First, paste your LinkedIn URL or the company website you want to send on
+  behalf of. I’ll use that to understand the company before we pick the target,
+  offer, proof, and lead source.
+  ```
+
   If there is no strong sender match, make the first quick question panel ask
   for the user's LinkedIn URL or company website. The point of this gate is not
   "pick a sender"; it is to learn who the user is, infer the current or most
@@ -175,7 +204,7 @@ Validated draft directory:
   ```
 
   Sender options should include connected sender names if available, `same as
-  me`, `I’ll paste a different sender profile`, and `Other / custom`.
+me`, `I’ll paste a different sender profile`, and `Other / custom`.
 
   After the user confirms the subject and sender, run one lightweight company
   lookup if it has not already run, then ask the campaign setup questions. The