@sellable/mcp 0.1.17 → 0.1.18

package/README.md

@@ -83,14 +83,14 @@ The token is provided when you generate it. Use `list_workspaces` +
 For customer/package installs, use the public installer:
 
 ```bash
-npx -y @sellable/install@0.1.17 --host codex --token skt_live_your_token_here --workspace-id your_workspace_id
+npx -y @sellable/install@0.1.18 --host codex --token skt_live_your_token_here --workspace-id your_workspace_id
 ```
 
 If you already have `~/.sellable/config.json`, rerun/verify without rewriting
 auth:
 
 ```bash
-npx -y @sellable/install@0.1.17 --host codex
+npx -y @sellable/install@0.1.18 --host codex
 sellable --verify-only --host codex
 ```
 

package/package.json

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

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

@@ -280,9 +280,45 @@ me`, `I’ll paste a different sender profile`, and `Other / custom`.
   Do not mention internal artifact names, local folders, shell commands, or
   persistence in this preamble.
 
-- After rendering the brief summary, ask for brief approval when there is a real
+- Before asking for brief approval, render the actual readable brief in the chat.
+  Do not ask the user to approve a one-paragraph direction, a risk note, or a
+  hidden artifact they cannot inspect. The user must be able to read what they
+  are approving without opening files. Include these sections:
+
+  ```text
+  Campaign brief
+
+  Who we are targeting:
+  ...
+
+  Why they should care:
+  ...
+
+  Offer / CTA:
+  ...
+
+  Proof to use:
+  ...
+
+  Lead source hypothesis:
+  ...
+
+  Message angle:
+  ...
+
+  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.
+  ```
+
+  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
   user-facing choice should be approve/revise language, not "looks good".
+  Approval options should refer to what the user just read, e.g. `Approve this
+  brief`, `Revise target`, `Revise offer/proof`, and `Other / custom`.
 - After the brief is approved or auto-confirmed, show the next progress line:
   `Cool. Now I'm going to find people who are both a good fit and likely to
 reply on LinkedIn. I'll compare source paths by expected volume, likely
@@ -307,6 +343,7 @@ should test for this campaign. Those can run in parallel and usually take
   because the brief becomes the source of truth for the leads and messages. I’ll
   show you the draft next so you can approve it or change it.
   ```
+
 - In hosted/rehearsal runs, `Bash` is only for safe local draft-directory
   housekeeping before approval: `mkdir`, `ls`, `find`, `test`, `pwd`, `echo`,
   `cat`, or copying `brief-v1.md` to `brief.md` inside the repo. Do not use

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

@@ -55,6 +55,10 @@ turn anchored to that:
 8. Ask for approval.
 9. Create the campaign.
 
+Approvals only feel safe when the user can see what they are approving. Before
+any approve/revise question, show the relevant decision in plain language. For a
+brief approval, render the brief itself, not just a direction summary.
+
 ## Progress Updates
 
 Every customer-facing update should answer one of these:
@@ -64,6 +68,17 @@ Every customer-facing update should answer one of these:
 - What will the user see next?
 - What is protected until approval?
 
+Before a brief approval, the user should see:
+
+- who we are targeting
+- why they should care
+- the offer / CTA
+- proof to use
+- lead source hypothesis
+- message angle
+- risks / assumptions
+- what happens after approval
+
 Good:
 
 ```text

package/skills/create-campaign-v2/core/flow.v2.json

@@ -213,10 +213,20 @@
         {
           "action": "render_brief_approval_checkpoint",
           "requiredVisibleContent": [
+            "Campaign brief",
+            "Who we are targeting",
+            "Why they should care",
+            "Offer / CTA",
+            "Proof to use",
+            "Lead source hypothesis",
+            "Message angle",
+            "Risks / assumptions",
+            "What happens after approval",
             "approve this brief",
             "revise the brief",
             "then I will find good-fit leads"
           ],
+          "minimumVisibleBriefDetail": "full_readable_brief_before_question",
           "avoidQuestionWhenOnlyUsefulAnswerIs": "looks good"
         },
         {