@sellable/mcp 0.1.43 → 0.1.45

package/package.json

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

package/skills/create-campaign/SKILL.md

@@ -133,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`,
@@ -281,9 +287,10 @@ 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.

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

@@ -79,12 +79,19 @@ Validated draft directory:
   `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 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
+  draft artifacts after the user answers. Use this structured 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.
+  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:
 
@@ -277,10 +284,12 @@ me`, `I’ll paste a different sender profile`, and `Other / custom`.
   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, 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.
+  confirmed, ask buyer, offer/CTA, proof, and lead source through the structured
+  question gate when available. Split the setup intake into two panels:
+  target/offer/proof first, then lead source. Do not present these as
+  checkbox/radio multi-select gates. Use 2-3 context-specific suggested answers
+  per question as fast-start shortcuts, and rely on the freeform custom path for
+  nuanced answers.
 - After the founder answers the first strategy/source packet, explain the next
   stage only: campaign brief creation and brief approval. Use this shape:
 
@@ -336,10 +345,19 @@ me`, `I’ll paste a different sender profile`, and `Other / custom`.
   Risks / assumptions:
   ...
 
-  What happens after approval:
-  I’ll find good-fit LinkedIn leads, show you the source decision and sample, then
-  draft the first message for review before anything goes live.
-  ```
+	  What happens after approval:
+	  I’ll find good-fit LinkedIn leads, show you the source decision and sample, then
+	  draft the first message for review before anything goes live.
+	  ```
+
+  The `Offer / CTA` section must name the useful thing the buyer gets by
+  replying. Do not use vague peer-call framing like `compare notes`, `swap
+  notes`, `worth chatting`, `pick your brain`, or a bare `15 minute call` unless
+  the user explicitly asks for that. A low-friction CTA is only good when the
+  object is concrete: a checklist, workflow teardown, benchmark, sample, short
+  loom, diagnostic, bottleneck map, relevant proof asset, or a working session
+  with a clear output. If the first draft produces a vague CTA, revise it before
+  showing the brief.
 
   After rendering that brief, ask for brief approval when there is a real
   strategic choice or the user has not already made the direction obvious. The
@@ -477,21 +495,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), 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.
+emphasis, tone, lead-source preference), use the structured quick question panel
+when available. Do not make it feel like a rigid multiple-choice survey:
+suggested directions are shortcuts, and the user must be able to type a custom
+answer in their own words. Ask target, offer, and proof in the first panel; ask
+lead source in a second panel. 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? 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.`
+- target prospects: `Who should this campaign target?`
+- main CTA / offer: `What useful thing should {{sender_or_company}} offer them?`
+- proof emphasis: `What proof should we lean on?`
+- lead source: `How should we get the people for this campaign?`
+
+Offer shortcuts must be concrete deliverables or outcomes, not meeting wrappers.
+Good examples: `send a short checklist`, `map 2-3 workflow bottlenecks`, `show a
+relevant customer example`, `teardown their public workflow`, `walk through a
+sample output`, or `diagnose where the current process slows down`. Bad
+examples: `compare notes`, `quick intro call`, `worth chatting`, `pick your
+brain`, `learn more`, or `see if it makes sense`.
 
 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:
+optional, not required. Suggested lead-source shortcuts should include:
 `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

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

@@ -103,6 +103,11 @@ Before a brief approval, the user should see:
 - risks / assumptions
 - what happens after approval
 
+The offer / CTA should be useful before it is convenient. Avoid vague
+peer-call asks like "compare notes" unless the user explicitly chose that. The
+buyer should know what they get if they reply: a checklist, teardown, diagnostic,
+sample, benchmark, relevant example, or working session with a concrete output.
+
 For lead-source decisions, confidence comes from concrete counts. Do not say
 "strong sample", "73% match", or "meaningful concentration" without showing the
 sample size and what was counted. Prefer: