@sellable/mcp 0.1.39 → 0.1.40

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 (the founder), 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 (the founder), 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 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 (error instanceof SellableApiError && error.isAuthError) {
             return {
                 ...base,

package/package.json

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

package/skills/create-campaign/SKILL.md

@@ -253,10 +253,18 @@ Cool — I have this campaign as {company}. Who should the LinkedIn messages sen
 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.
+After the user confirms the subject and sender, run one bounded lightweight
+company-context pass before asking the campaign setup questions. A sender
+LinkedIn profile lookup is not enough by itself unless it clearly includes the
+company's website, product category, customer, and offer context. If the host can
+run tools in parallel, use one parallel batch with at most 2-3 cheap lookups:
+`mcp__sellable__fetch_company` on a LinkedIn company URL from the profile when
+available; `WebFetch` for the company website/domain when available; otherwise
+one `WebSearch` for `{company} official website` or `{company} product`. If
+parallel tool calls are unavailable, do the single highest-confidence lookup
+first and continue. Do not run full company research, source discovery, Sales
+Nav, Prospeo, Signals, or multi-query browsing here. The goal is a fast 15-30
+second context read so the four setup questions feel specific.
 
 Before the identity gate, use this customer-facing shape:
 
@@ -400,7 +408,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 (the founder), or whoever's voice the messages should sound like.
+       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.
 
        e.g. https://www.linkedin.com/in/your-handle
        ```
@@ -411,7 +419,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 (the founder), or whoever's voice the messages should sound like.
+       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.
 
        e.g. https://www.linkedin.com/in/your-handle
        ```

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

@@ -226,11 +226,20 @@ 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`.
 
-  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.
+  After the user confirms the subject and sender, run one bounded lightweight
+  company-context pass before asking the campaign setup questions. A sender
+  LinkedIn profile lookup is not enough by itself unless it clearly includes the
+  company's website, product category, customer, and offer context. If the host
+  can run tools in parallel, use one parallel batch with at most 2-3 cheap
+  lookups: `fetch_company` on a LinkedIn company URL from the profile when
+  available; `WebFetch` for the company website/domain when available; otherwise
+  one `WebSearch` for `{company} official website` or `{company} product`. If
+  parallel tool calls are unavailable, do the single highest-confidence lookup
+  first and continue. Do not run full company research, source discovery, Sales
+  Nav, Prospeo, Signals, or multi-query browsing here. The goal is a fast 15-30
+  second context read so the four setup questions feel specific. 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:
 
@@ -250,7 +259,9 @@ me`, `I’ll paste a different sender profile`, and `Other / custom`.
   that first packet, the first assistant turn may only call
   `bootstrap_create_campaign`, load this workflow prompt with
   `get_subskill_prompt({ subskillName: "create-campaign-v2" })`, optionally run
-  one lightweight identity lookup, then use the structured question gate. If the user
+  one lightweight identity lookup, then use the structured question gate. After
+  identity is confirmed, run the bounded lightweight company-context pass above
+  before generating buyer/offer/proof/source options. 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 setup options. If the user supplied a LinkedIn profile URL, call