@sellable/mcp 0.1.165 → 0.1.166

package/package.json

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

package/skills/create-campaign/SKILL.md

@@ -276,14 +276,16 @@ workspace routing needed for auto-login. `create_campaign.watchUrl`,
 acceptable only when they return that direct campaign-builder shape.
 
 Never call browser-opening tools, shell `open`, Computer Use, or in-app browser
-automation just because a watch link exists. Print the link and tell the user to
-Command-Enter/click it when they want to watch in the app. Use this shape:
+automation just because a watch link exists. Print the link in this shape:
 
 ```text
+Campaign shell is ready. You and I will keep building the campaign in this chat.
+You can watch it come together in real time here:
+
 Watch link: {watchUrl}
 
-Command-Enter or click that link to watch the campaign in Sellable. I’ll keep
-the brief, lead source, and message-review steps explicit here as I build.
+Send changes here. I’ll ask for your approval whenever I need your expertise or
+taste before moving forward.
 ```
 
 The watch link should auto-login through the token in the URL. If the user says

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

@@ -136,10 +136,9 @@ when a bounded choice needs an escape hatch.
 ## Watch Link And Narration
 
 The first campaign shell is created before lead import so the user can watch
-the work. When `create_campaign` returns `watchUrl`, print it directly and tell
-the user to Command-Enter or click it. Never call browser-opening tools,
-Computer Use, shell `open`, or in-app browser automation just because a watch
-link exists.
+the work. When `create_campaign` returns `watchUrl`, print it directly. Never
+call browser-opening tools, Computer Use, shell `open`, or in-app browser
+automation just because a watch link exists.
 
 Every watched step switch must call:
 

package/skills/create-campaign-v2/references/watch-link-handoff.md

@@ -34,21 +34,14 @@ Example skeleton:
 
 ```text
 I created the campaign shell with the brief already in it.
-I am creating the campaign through this chat. Open this link if you want to
-watch the work being done and audit what changes.
+You and I will keep building the campaign in this chat. You can watch it come
+together in real time here:
 
-You can still ask me to change anything here. I’ll pause at the next approval
-gate before sourcing.
+You can still ask me to change anything here. I’ll ask for your approval
+whenever I need your expertise or taste before moving forward.
 
 Watch link: [Open campaign]({watchUrl})
 
-Click that link to watch the campaign. The app is for inspection; this chat is
-where you direct the campaign. If it opens in an in-app browser and asks you to
-sign in, open the same link in your regular browser so you can watch real-time
-updates from your signed-in session.
-
-Command-Enter or click that link to watch it in Sellable.
-
 Now ask the brief approval question. Do not show the approve/revise question
 panel until the full brief content and this `Watch link:` line have appeared in
 normal chat text. A summary such as "the brief is visible there" is not enough
@@ -134,7 +127,7 @@ cached or reconstructed URL.
 - Never fabricate or reconstruct the URL locally.
 - The watch link must be a direct campaign-builder URL with token auto-login.
 - Do not call browser-opening tools, shell `open`, Computer Use, or in-app
-  browser automation; the user opens the link when they want to watch.
+  browser automation just because a watch link exists.
 - Missing `watchUrl` is an error, not a silent skip.
 - The first watch link must be shown only after the v1 brief is on the campaign.
 - A watch link is not approval to import, attach sequence, or start.