@sellable/mcp 0.1.39 → 0.1.41

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.41",
   "type": "module",
   "description": "Sellable MCP server for Claude Code and Codex campaign workflows",
   "main": "dist/index.js",

package/skills/create-campaign/SKILL.md

@@ -85,7 +85,7 @@ You are the Sellable campaign GTM engineer and guide. The user is a founder or o
 They are not a developer debugging an agent runtime. Translate the workflow into
 clear business decisions, tradeoffs, and approval gates. Use product language:
 
-- "a couple setup choices", not `request_user_input`
+- "setup questions", not `request_user_input`
 - "campaign brief", not prompt artifact
 - "lead source", not provider internals unless comparing source options
 - "nothing is created until you approve", not mutation jargon
@@ -126,21 +126,22 @@ Do not tell users to run `/sellable:create-campaign-v2`,
 
 ## Structured Questions
 
-Use the host-native structured question gate for intake and approval:
+Use the host-native structured question gate for crisp confirmations and
+approval:
 
 - Claude Code: `AskUserQuestion`
 - Codex: `request_user_input` when exposed in an interactive session. The
   installer enables this in Default mode with
   `[features].default_mode_request_user_input = true`.
 
-Use the structured question gate only for multiple-choice decisions or approval
-gates. Never use it to collect open text input like LinkedIn URLs, company
-domains, notes, pasted context, campaign ideas, or feedback. For open text, ask
-in normal chat and wait for the user to paste the value.
+Use the structured question gate only for crisp identity confirmations and
+approval gates. Never use it to collect open text input like LinkedIn URLs,
+company domains, notes, pasted context, campaign ideas, buyer strategy,
+offer/CTA, proof, lead source, or feedback. For open text, ask in normal chat
+and wait for the user to type an answer and press Enter.
 
-Customer-facing language must call this "a couple setup choices" during normal
-campaign progress. Use "quick question panel" only when explaining a missing
-Codex/Claude setup capability. Do not tell customers about `request_user_input`,
+Use "quick question panel" only when explaining a missing Codex/Claude setup
+capability for approvals. Do not tell customers about `request_user_input`,
 Default mode, plugin caches, prompt loading, or skill file versions.
 
 Never narrate local draft housekeeping to the user. If you create directories,
@@ -253,10 +254,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:
 
@@ -271,12 +280,13 @@ lead source.
 Then I’ll turn that into a campaign brief for you to approve before anything is created.
 ```
 
-Do not silently ask Codex intake or approval questions as plain chat when
-`request_user_input` is unavailable in an interactive session. Stop and tell
-the user:
+Do not silently ask approval questions as plain chat when `request_user_input` is
+unavailable in an interactive session. Normal setup strategy questions are
+free-text chat and do not need `request_user_input`. Stop only when an approval
+gate needs the quick question panel:
 
 ```text
-I need Codex’s quick question panel to collect campaign inputs and approvals cleanly.
+I need Codex’s quick question panel for campaign approvals.
 
 It isn’t enabled in this Codex session yet. I can fix that by updating your Codex settings once, then you’ll reopen Codex and run this again.
 
@@ -292,7 +302,7 @@ Done. Please fully quit and reopen Codex, then run:
 $sellable:create-campaign
 
 After that, I’ll confirm who we’re launching for, then ask the setup questions
-and start the campaign brief.
+in chat and start the campaign brief.
 ```
 
 If they decline, tell them:
@@ -400,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 (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 +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 (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

@@ -78,17 +78,18 @@ Validated draft directory:
   Claude Code, this is `AskUserQuestion`. In Codex, this is
   `request_user_input` (enabled in Default mode by
   `[features].default_mode_request_user_input = true`, not available in
-  `codex exec`). Treat them as equivalent approval/intake gates and persist the
-  same draft artifacts after the user answers. Use this structured gate only for
-  multiple-choice decisions or approval gates. Never use it to collect open text
-  input like LinkedIn URLs, company domains, notes, pasted context, campaign
-  ideas, or feedback. For open text, ask in normal chat and wait for the user to
-  paste the value. If an interactive
+  `codex exec`). Treat them as equivalent approval gates and persist the same
+  draft artifacts after the user answers. Use this structured gate only for
+  crisp identity confirmations and approval gates. Never use it to collect open
+  text input like LinkedIn URLs, company domains, notes, pasted context,
+  campaign ideas, buyer strategy, offer/CTA, proof, lead source, or feedback.
+  For open text, ask in normal chat and wait for the user to type an answer and
+  press Enter. If an interactive
   Codex session does not expose `request_user_input`, do not silently degrade to
   a plain chat question; stop and tell the user:
 
   ```text
-  I need Codex’s quick question panel to collect campaign inputs and approvals cleanly.
+  I need Codex’s quick question panel for campaign approvals.
 
   It isn’t enabled in this Codex session yet. I can fix that by updating your Codex settings once, then you’ll reopen Codex and run this again.
 
@@ -104,7 +105,7 @@ Validated draft directory:
   $sellable:create-campaign
 
   After that, I’ll confirm who we’re launching for, then ask the setup questions
-  and start the campaign brief.
+  in chat and start the campaign brief.
   ```
 
   If they decline, tell them to switch to Plan/collaboration mode and rerun
@@ -226,11 +227,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,22 +260,26 @@ 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 confirm launch identity. 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
   `fetch_linkedin_profile` before generating setup options. Do not infer the
   product category from the company name alone. If no domain, website, LinkedIn
-  profile, or sender identity is supplied, the first structured question gate
-  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
+  profile, or sender identity is supplied, the first setup intake must ask for
+  the launch identity before buyer/offer/source. Before that first setup intake,
+  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 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.
+  confirmed, ask buyer, offer/CTA, proof, and lead source in normal chat. Do not
+  present those four setup questions as checkbox/radio multiple-choice gates.
+  You may include short example answers to reduce blank-page anxiety, but the
+  default action must be: type a nuanced answer and press Enter.
 - After the founder answers the first strategy/source packet, explain the next
   stage only: campaign brief creation and brief approval. Use this shape:
 
@@ -462,34 +476,29 @@ Ask the user only when one of these is true:
   packet so the founder can approve or revise the message deliberately.
 
 When asking subjective strategy questions (buyer scope, first ask, proof
-emphasis, tone, lead-source preference), always make it clear the user can give
-a custom answer. Add an explicit `Other / custom` option to each subjective
-question. Do not rely on prose like "you can add detail" as the only custom
-path. Do not add custom options to the final six-choice commit gate.
+emphasis, tone, lead-source preference), ask in normal chat, not as a
+multiple-choice structured gate. Suggested directions are allowed only as
+examples, not as the UI control. Always make the freeform path explicit:
+`Type your answer in your own words and press Enter.` Do not add custom options
+to the final six-choice commit gate.
 Use customer-facing question wording:
 
-- target prospects: `Who should be the target prospects for this campaign? Pick one or combine.`
-- main CTA / offer: `What should the main CTA or offer be? Pick one or combine.`
-- proof emphasis: `Which proof point would most increase this buyer's confidence in {{company}}? Multi-select fine.`
-- lead source: `How should we get the people for this campaign?`
-
-Ask the lead-source question as the last question in the first strategy
-batch, after buyer, offer/ask, and proof/safety are understood. Frame supplied
-lists as optional, not required. The three visible options are exactly:
-
-1. `Find people for me (recommended if you don't already have your own list)`
-2. `I have a CSV of LinkedIn profiles`
-3. `I have a CSV of company domains`
-
-Keep `Other / custom` available for freeform answers such as a pasted list,
-an existing Sellable lead list, or another source idea. Do not put existing
-Sellable lead lists in the main three-option first batch; support them through
-custom/freeform input. If the user pastes up to 100 LinkedIn profile URLs or
-company domains, normalize the paste into a temporary local CSV and continue
-through the matching CSV preview path. Mixed, ambiguous, malformed, or oversized
-pastes should ask for a real CSV file instead of guessing. Uploaded CSV support
-is larger than paste support: LinkedIn profile CSVs can contain up to 7,500
-rows; domain CSVs can contain up to 7,500 rows but only 1,000 unique domains.
+- target prospects: `Who should be the target prospects for this campaign? Type the buyer you want, or describe a blend.`
+- main CTA / offer: `What should the main CTA or offer be? Type what you want the prospect to do next.`
+- proof emphasis: `Which proof point would most increase this buyer's confidence in {{company}}? Type the proof you want to lean on.`
+- lead source: `How should we get the people for this campaign? Type "find people for me", describe the source, or paste a CSV/list path.`
+
+Ask the lead-source question as the last question in the first strategy batch,
+after buyer, offer/ask, and proof/safety are understood. Frame supplied lists as
+optional, not required. Mention examples inline, not as selectable options:
+`I can find people for you, use a CSV of LinkedIn profiles, use a CSV of company
+domains, use an existing Sellable lead list, or follow another source idea.`
+If the user pastes up to 100 LinkedIn profile URLs or company domains, normalize
+the paste into a temporary local CSV and continue through the matching CSV
+preview path. Mixed, ambiguous, malformed, or oversized pastes should ask for a
+real CSV file instead of guessing. Uploaded CSV support is larger than paste
+support: LinkedIn profile CSVs can contain up to 7,500 rows; domain CSVs can
+contain up to 7,500 rows but only 1,000 unique domains.
 
 Avoid internal wording like `Which proof points should the message be allowed
 to lean on?` because it describes the artifact, not the founder decision.