@sellable/mcp 0.1.11 → 0.1.13

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

package/package.json

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

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

@@ -114,8 +114,9 @@ Validated draft directory:
   loading, runbooks, local skill files, or skill versions.
 - 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.
+  proof, or source questions, identify two things:
+  1. who/what company this campaign is for, and
+  2. who the LinkedIn messages should send from.
 - 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`.
@@ -123,26 +124,74 @@ Validated draft directory:
     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.
+    the campaign subject and sender before continuing.
+- If the user did not provide the launch identity, quietly call `list_senders`
+  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:
+
+  ```text
+  I’m ready to build this in {workspace}. I found {matched sender} connected here.
+
+  Is that you, and is this campaign for {company}?
+  ```
+
+  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
+  recent company, and then confirm who we are sending from. The customer-facing
+  shape should be:
+
+  ```text
+  I’m ready to build this in {workspace}.
+
+  First, what’s your LinkedIn URL? If you’d rather start from the company, paste
+  the company website instead.
+  ```
+
+  The LinkedIn/company identity gate should ask:
+
+  1. `What’s your LinkedIn URL?` Options: `I’ll paste my LinkedIn profile`,
+     `I’ll paste the company website instead`, `Other / custom`.
+
+  After that answer, do the lightweight lookup. For a LinkedIn profile, call
+  `fetch_linkedin_profile` and infer the user's current or most recent company
+  from the profile. For a company website, call `fetch_company` when possible,
+  otherwise one web lookup.
+
+  If `list_senders` did not already run, call it once after the lookup to see
+  whether the fetched user appears to match a connected sender. If there is a
+  likely match, ask:
+
+  ```text
+  Cool — are you {matched sender}, and is this campaign for {company}?
+  ```
+
+  If there is no likely sender match, ask:
+
+  ```text
+  Cool — I have this campaign as {company}. Who should the LinkedIn messages send from?
+  ```
+
+  Sender options should include connected sender names if available, `same as
+  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
+  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 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.
+  First I’ll check whether your Sellable token already tells me who you are. If
+  not, I’ll ask for your LinkedIn URL or company website, look it up, then
+  confirm the company and sender 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.
   ```
@@ -162,10 +211,12 @@ Validated draft directory:
   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. 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.
+  draft-directory inspection/creation. `list_senders` is allowed once before the
+  first identity gate as a quiet token/sender inference shortcut, and once means
+  once: do not call it again after a LinkedIn lookup if it already ran. Do
+  draft-directory setup only after the 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,14 +28,15 @@ 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. 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.
+1. Confirm who/what company the campaign is for.
+2. Confirm who the LinkedIn messages send from.
+3. Understand the company and offer.
+4. Turn that into a campaign brief.
+5. Find likely responders.
+6. Filter for fit.
+7. Draft messages.
+8. Ask for approval.
+9. Create the campaign.
 
 ## Progress Updates
 

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

@@ -100,12 +100,23 @@
           "optional": false,
           "when": "before_founder_strategy_source_packet",
           "allowedTools": [
+            "list_senders",
+            "get_sender",
+            "enrich_sender",
             "fetch_company",
             "fetch_linkedin_profile",
             "WebFetch",
             "WebSearch"
           ],
-          "maxCalls": 1,
+          "maxCalls": {
+            "list_senders": 1,
+            "identityLookup": 1,
+            "companyLookupAfterIdentityConfirm": 1
+          },
+          "quietlyCheckConnectedSendersFirst": true,
+          "preferUserLinkedInWhenSenderInferenceIsWeak": true,
+          "doNotPresentSenderPickerBeforeIdentityInference": true,
+          "confirmCompanyBeforeStrategyQuestions": true,
           "mustNotInferFromNameOnly": true,
           "fallback": "ask identity gate first; use neutral/custom intake options only when identity remains unavailable"
         },