@sellable/mcp 0.1.12 → 0.1.14

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

package/package.json

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

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

@@ -125,53 +125,90 @@ Validated draft directory:
   - 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 campaign subject and sender before continuing.
-- If the user did not provide the launch identity, make the first quick question
-  panel an identity gate. The point of this gate is not "pick a sender"; it is
-  to learn who the user is / what company we are launching for, and who we
-  should send from. Before that gate, call `list_senders` once if it is
-  available, only so you can offer connected senders as shortcuts. The
-  customer-facing shape should be:
+- 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 a structured
+  confirmation question:
 
   ```text
-  I found these connected senders in {workspace}: {sender names}.
+  I’m ready to build this in {workspace}. I found {matched sender} connected here.
 
-  First I need to know who this campaign is for and who we’re sending from. If
-  one of these connected senders is you, pick them; otherwise paste your LinkedIn
-  URL or company website.
+  Is that you, and is this campaign for {company}?
   ```
 
-  The identity gate should ask:
+  The options must be:
 
-  1. `Who is this campaign for?` Options: connected sender names if available,
-     `I’ll paste a LinkedIn profile`, `I’ll paste a company website/domain`,
-     `Other / custom`.
-  2. `Who should the LinkedIn messages send from?` Options:
-     `same person/company`, connected sender names if available,
-     `I’ll paste a different sender profile`, `Other / custom`.
+  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`
 
-  After that answer, do the lightweight lookup. For a connected sender, call
-  `enrich_sender` and identify their current or most recent company. For a
-  LinkedIn profile, call `fetch_linkedin_profile` and infer the current or most
-  recent company from the profile. Then ask:
+  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 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 — I have this as {campaign subject/company}, sending from {sender}. Is that right?
+  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 (`fetch_company` when possible, otherwise one web lookup), 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.
+  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 this campaign is for and who we’re sending from.
-  If you already have a connected sender, I can use that to infer the company;
-  otherwise paste a LinkedIn profile or company website and I’ll look it up.
+  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.
   ```
@@ -192,7 +229,8 @@ Validated draft directory:
   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. `list_senders` is allowed once before the
-  first identity gate so the user can pick from connected senders. Do
+  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.

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

@@ -113,7 +113,9 @@
             "identityLookup": 1,
             "companyLookupAfterIdentityConfirm": 1
           },
-          "preferConnectedSendersFirst": true,
+          "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"