@sellable/install 0.1.48 → 0.1.50

package/package.json

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

package/skill-templates/create-campaign.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
@@ -134,11 +133,17 @@ approval:
   installer enables this in Default mode with
   `[features].default_mode_request_user_input = true`.
 
-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.
+Use the structured question gate for crisp identity confirmations, compact setup
+intake, and approval gates. Never use it to collect raw open text like LinkedIn
+URLs, company domains, pasted notes, long campaign ideas, or detailed feedback.
+For buyer strategy, offer/CTA, proof, and lead source, use the structured gate
+when it is exposed, but treat the visible choices as shortcuts, not a rigid
+multiple-choice survey. Every setup question must allow a custom typed answer.
+In Codex, `request_user_input` adds a freeform Other path; in Claude, include an
+`Other / custom` option. Keep setup intake to two panels because Codex supports
+at most three questions per panel: target/offer/proof first, lead source second.
+Do not use checkbox/radio multi-select language like "pick one",
+"multi-select", or "choose all that apply" for these setup questions.
 
 Use "quick question panel" only when explaining a missing Codex/Claude setup
 capability for approvals. Do not tell customers about `request_user_input`,
@@ -181,7 +186,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 +219,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 +233,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 +243,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,20 +279,18 @@ 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
-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:
+unavailable in an interactive session. Setup strategy questions should use the
+quick question panel when available, but may fall back to normal chat if the host
+does not expose structured setup input. Stop only when an approval gate needs the
+quick question panel:
 
 ```text
 I need Codex’s quick question panel for campaign approvals.