@sellable/install 0.1.45 → 0.1.47

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sellable/install",
-  "version": "0.1.45",
+  "version": "0.1.47",
   "type": "module",
   "description": "One-command installer for Sellable MCP in Claude Code and Codex",
   "bin": {

package/skill-templates/create-campaign.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
        ```