@sellable/mcp 0.1.41 → 0.1.43

package/dist/tools/auth.js

@@ -138,8 +138,8 @@ export async function getAuthStatus() {
             "5) Call `mcp__sellable__wait_for_cli_login({ sessionId })` using the sessionId returned by start_cli_login. " +
             "6) If the result is `error.type === 'tool_timeout_guard'`, IMMEDIATELY re-call wait_for_cli_login with the SAME sessionId — do not narrate, do not call start_cli_login again. Loop until you get a different result. " +
             "7) On `ok: true`, the user is signed in and `~/.sellable/config.json` has been written. Branch on `isReturningUser`: " +
-            "if true, say `You're in — {activeWorkspaceName} workspace, ready to roll.\\n\\nNow — paste the LinkedIn profile URL of the person you'll be sending campaigns from. Usually that's you, or whoever's voice the messages should sound like.\\n\\ne.g. https://www.linkedin.com/in/your-handle`; " +
-            "if false, say `You're set up — your {activeWorkspaceName} workspace is ready.\\n\\nNow — paste the LinkedIn profile URL of the person you'll be sending campaigns from. Usually that's you, or whoever's voice the messages should sound like.\\n\\ne.g. https://www.linkedin.com/in/your-handle`";
+            "if true, say `You're in — {activeWorkspaceName} workspace, ready to roll.\\n\\nNow — paste the LinkedIn profile URL of the person you'll be sending this campaign from. Usually that's you. If someone else will send this campaign, paste their profile instead.\\n\\ne.g. https://www.linkedin.com/in/your-handle`; " +
+            "if false, say `You're set up — your {activeWorkspaceName} workspace is ready.\\n\\nNow — paste the LinkedIn profile URL of the person you'll be sending this campaign from. Usually that's you. If someone else will send this campaign, paste their profile instead.\\n\\ne.g. https://www.linkedin.com/in/your-handle`";
         if (error instanceof SellableApiError && error.isAuthError) {
             return {
                 ...base,

package/package.json

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

package/skills/create-campaign/SKILL.md

@@ -70,9 +70,8 @@ instruction loading, file lookup, plugin cache versions, missing linked files,
 or tool discovery. Start in product language:
 
 ```text
-I’ll help you launch this as a Sellable campaign. First I’ll confirm who we’re
-sending from and which company this is for, then I’ll turn that into a campaign
-brief before anything is created.
+I’ll help you launch this as a Sellable campaign. First I’ll confirm the sender
+and company, then draft the campaign brief for your approval.
 ```
 
 If a linked/local skill file is stale or missing, silently use the installed
@@ -181,7 +180,9 @@ senders. If there is any likely connected sender, use
 recent company, then ask a structured confirmation question:
 
 ```text
-I’m ready to build this in {workspace}. I found {matched sender} connected here.
+Workspace: {workspace}
+
+I found {matched sender} connected here.
 
 Is that you, and is this campaign for {company}?
 ```
@@ -212,11 +213,11 @@ with the structured question tool. Ask in normal chat 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}.
+Workspace: {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.
+First, paste your LinkedIn URL or the company website. I’ll use it to confirm
+the sender and company, then we’ll choose the target, offer, proof, and lead
+source.
 ```
 
 If there is no strong sender match, do not show a structured choice that says
@@ -226,7 +227,7 @@ 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}.
+Workspace: {workspace}
 
 First, what’s your LinkedIn URL? If you’d rather start from the company, paste
 the company website instead.
@@ -236,6 +237,8 @@ After the user pastes a URL/domain, do the lightweight lookup. For a LinkedIn pr
 `mcp__sellable__fetch_linkedin_profile` and infer the user's current or most
 recent company from the profile. For a company website, call
 `mcp__sellable__fetch_company` when possible, otherwise one web lookup.
+Before the lookup, use concise progress copy:
+`Got it — I’ll look it up and confirm the sender + company.`
 
 If `mcp__sellable__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
@@ -270,14 +273,11 @@ second context read so the four setup questions feel specific.
 Before the identity gate, use this customer-facing shape:
 
 ```text
-I’m ready to build the campaign in {workspace}.
-
-First I’ll check whether you already have a connected LinkedIn account here. If
-I can’t confirm it, I’ll ask for your LinkedIn URL or company website and use
-that to understand the company before we choose the target, offer, proof, and
-lead source.
+Workspace: {workspace}
 
-Then I’ll turn that into a campaign brief for you to approve before anything is created.
+First I’ll check for a connected LinkedIn sender. If I can’t confirm one, I’ll
+ask for your LinkedIn URL or company website before we choose the target, offer,
+proof, and lead source.
 ```
 
 Do not silently ask approval questions as plain chat when `request_user_input` is
@@ -410,7 +410,7 @@ updates.
        ```text
        You're in — {activeWorkspaceName} workspace, ready to roll.
 
-       Now — paste the LinkedIn profile URL of the person you'll be sending campaigns from. Usually that's you, or whoever's voice the messages should sound like.
+       Now — paste the LinkedIn profile URL of the person you'll be sending this campaign from. Usually that's you. If someone else will send this campaign, paste their profile instead.
 
        e.g. https://www.linkedin.com/in/your-handle
        ```
@@ -421,7 +421,7 @@ updates.
        ```text
        You're set up — your {activeWorkspaceName} workspace is ready.
 
-       Now — paste the LinkedIn profile URL of the person you'll be sending campaigns from. Usually that's you, or whoever's voice the messages should sound like.
+       Now — paste the LinkedIn profile URL of the person you'll be sending this campaign from. Usually that's you. If someone else will send this campaign, paste their profile instead.
 
        e.g. https://www.linkedin.com/in/your-handle
        ```

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

@@ -154,7 +154,9 @@ Validated draft directory:
   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.
+  Workspace: {workspace}
+
+  I found {matched sender} connected here.
 
   Is that you, and is this campaign for {company}?
   ```
@@ -185,11 +187,11 @@ Validated draft directory:
   company they want to send on behalf of so you can research context:
 
   ```text
-  I’m ready to build this in {workspace}.
+  Workspace: {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.
+  First, paste your LinkedIn URL or the company website. I’ll use it to confirm
+  the sender and company, then we’ll choose the target, offer, proof, and lead
+  source.
   ```
 
   If there is no strong sender match, do not show a structured choice that says
@@ -199,7 +201,7 @@ Validated draft directory:
   customer-facing shape should be:
 
   ```text
-  I’m ready to build this in {workspace}.
+  Workspace: {workspace}
 
   First, what’s your LinkedIn URL? If you’d rather start from the company, paste
   the company website instead.
@@ -209,6 +211,8 @@ Validated draft directory:
   `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.
+  Before the lookup, use concise progress copy:
+  `Got it — I’ll look it up and confirm the sender + company.`
 
   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
@@ -245,14 +249,11 @@ me`, `I’ll paste a different sender profile`, and `Other / custom`.
 - Before the identity gate, use this customer-facing shape:
 
   ```text
-  I’m ready to build the campaign in {workspace}.
+  Workspace: {workspace}
 
-  First I’ll check whether you already have a connected LinkedIn account here.
-  If I can’t confirm it, I’ll ask for your LinkedIn URL or company website and
-  use that to understand the company before we choose the target, offer, proof,
-  and lead source.
-
-  Then I’ll turn that into a campaign brief for you to approve before anything is created.
+  First I’ll check for a connected LinkedIn sender. If I can’t confirm one, I’ll
+  ask for your LinkedIn URL or company website before we choose the target,
+  offer, proof, and lead source.
   ```
 
 - Fast Intake Mode is mandatory for hosted/rehearsal net-new runs. Ask the