@sellable/mcp 0.1.245 → 0.1.247

package/dist/tools/campaigns.js

@@ -49,16 +49,31 @@ function getCampaignBuilderWatchModeFromUrl(watchUrl) {
 export function getCampaignBuilderWatchModeDriverLabel(mode = getCampaignBuilderWatchModeParam()) {
     return mode === "codex" ? "Codex" : "Claude Code";
 }
+function buildWatchHandoffHeadlineBox(headline) {
+    const width = 52;
+    const visibleHeadline = headline.length > width ? headline.slice(0, width) : headline;
+    const padding = Math.max(width - visibleHeadline.length, 0);
+    const left = Math.floor(padding / 2);
+    const right = padding - left;
+    const border = `+${"-".repeat(width + 2)}+`;
+    return [
+        "```",
+        border,
+        `| ${" ".repeat(left)}${visibleHeadline}${" ".repeat(right)} |`,
+        border,
+        "```",
+    ].join("\n");
+}
 export function buildCampaignWatchHandoffMarkdown(watchUrl, mode = getCampaignBuilderWatchModeFromUrl(watchUrl) ??
     getCampaignBuilderWatchModeParam()) {
     const driverLabel = getCampaignBuilderWatchModeDriverLabel(mode);
     const headline = `WATCH ${driverLabel.toUpperCase()} BUILD THE CAMPAIGN LIVE`;
     return [
-        `> **${headline}**`,
-        ">",
-        `> [Open live campaign builder](${watchUrl})`,
-        ">",
-        "> Keep this chat open. I'll ask approval questions here before making decisions that need your judgment.",
+        buildWatchHandoffHeadlineBox(headline),
+        "",
+        `[Open live campaign builder](${watchUrl})`,
+        "",
+        "Keep this chat open. I'll ask approval questions here before making decisions that need your judgment.",
     ].join("\n");
 }
 function buildCampaignBuilderWatchPath(campaignId) {

package/package.json

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

package/skills/create-campaign/SKILL.md

@@ -409,19 +409,23 @@ automation just because a watch link exists. If `create_campaign` returns
 approval question. It will use the URL mode to say Codex or Claude Code:
 
 ````markdown
-> **WATCH CODEX BUILD THE CAMPAIGN LIVE**
->
-> [Open live campaign builder]({watchUrl})
->
-> Keep this chat open. I'll ask approval questions here before making decisions
-> that need your judgment.
+```
++------------------------------------------------------+
+|         WATCH CODEX BUILD THE CAMPAIGN LIVE          |
++------------------------------------------------------+
+```
+
+[Open live campaign builder]({watchUrl})
+
+Keep this chat open. I'll ask approval questions here before making decisions
+that need your judgment.
 ````
 
-The rendered callout is intentional: rendered chat clients highlight the
-headline, link, and note without treating it as a code block, and plain terminals
-still expose the tokenized URL inside the Markdown target. Do not wrap this CTA
-in a fenced code block, replace it with a shell command, or add a
-browser-opening instruction.
+The ASCII banner is intentional because it is unmissable in both Codex and plain
+terminals. Only the banner should be fenced/preformatted; keep the Markdown link
+and chat note outside the fence so rendered chat clients still expose a normal
+click target. Do not add a code-fence language label, replace the link with a
+shell command, or add a browser-opening instruction.
 
 The watch link should auto-login through the token in the URL. If the user says
 the link lands on auth, 404, permission, blank, or a visible error state, recover

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

@@ -341,12 +341,16 @@ approve/revise recommendation, not fallback samples, concerns, or a QA receipt.
 Be explicit about what has and has not happened:
 
 ````markdown
-> **WATCH CODEX BUILD THE CAMPAIGN LIVE**
->
-> [Open live campaign builder]({watchUrl})
->
-> Keep this chat open. I'll ask approval questions here before making decisions
-> that need your judgment.
+```
++------------------------------------------------------+
+|         WATCH CODEX BUILD THE CAMPAIGN LIVE          |
++------------------------------------------------------+
+```
+
+[Open live campaign builder]({watchUrl})
+
+Keep this chat open. I'll ask approval questions here before making decisions
+that need your judgment.
 ````
 
 Print that watch-link handoff only once before the brief approval question, and

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

@@ -39,12 +39,16 @@ useful brief instead of an empty campaign.
 Example skeleton:
 
 ````markdown
-> **WATCH CODEX BUILD THE CAMPAIGN LIVE**
->
-> [Open live campaign builder]({watchUrl})
->
-> Keep this chat open. I'll ask approval questions here before making decisions
-> that need your judgment.
+```
++------------------------------------------------------+
+|         WATCH CODEX BUILD THE CAMPAIGN LIVE          |
++------------------------------------------------------+
+```
+
+[Open live campaign builder]({watchUrl})
+
+Keep this chat open. I'll ask approval questions here before making decisions
+that need your judgment.
 
 Now ask the brief approval question. Do not show the approve/revise question
 panel until the full brief content and this exact watch-link handoff have

package/skills/create-post/SKILL.md

@@ -6,6 +6,36 @@ visibility: internal
 
 # Create Post
 
+<command_model>
+`create-post` is the user-facing content command for LinkedIn post work.
+
+It owns the content workflow:
+
+- log rough post source material, voice memos, transcripts, and freestyle notes
+- mine transcript-derived content memory for recurring ideas and hidden angles
+- workshop a promising idea until the premise has enough story/proof/tension
+- run external LinkedIn research
+- draft, validate, save, and publish-track posts
+
+It does not own foundational identity setup. Use `$sellable:interview` for the
+foundation layer: core values, founder identity, company truth, durable stories,
+proof ledgers, answer bank, context modes, anti-AI rules, and transcript indexes.
+
+Implementation detail: `mcp__sellable__get_engage_memory` is the
+backward-compatible loader for unified Sellable memory. It is not a separate
+user-facing command. `create-post` must call it and use both:
+
+- interview-created foundation memory: `core/about-me.md`,
+  `core/my-company.md`, `core/story-bank.md`, `core/proof-ledger.md`,
+  `core/answer-bank.md`, `core/context-modes.md`
+- content memory: `core/content-memory/**` clusters, cards, questions, and seeds
+
+If foundation memory is missing or too thin, ask the user to run
+`$sellable:interview` or answer the missing foundation questions before
+drafting. If content-memory is missing, continue from the raw source and propose
+the smallest content-memory write-back.
+</command_model>
+
 <role>
 You are the Sellable LinkedIn post writer for a specific user.
 

package/skills/interview/SKILL.md

@@ -6,6 +6,30 @@ visibility: public
 
 # Core Identity Interview
 
+<command_model>
+`interview` is the foundation-memory command.
+
+It owns:
+
+- core values and founder identity
+- company truth and positioning
+- durable stories and reusable answers
+- proof/wins ledgers and proof-safety rules
+- context modes and anti-AI writing rules
+- transcript/topic references and raw interview archives
+- approved reference packs
+
+It does not own the LinkedIn post production workflow. When a user wants to log
+post source notes, mine transcripts for post ideas, workshop a post seed, or
+draft a LinkedIn post, route that to `$sellable:create-post`.
+
+The bridge is unified memory: `interview` writes the foundation under
+`~/.sellable/configs/core/**`; `create-post` loads it through
+`mcp__sellable__get_engage_memory` before researching or drafting. This means
+posts should always have access to interview-created values, voice, stories,
+proof, and context modes when they exist.
+</command_model>
+
 <role>
 You are the Sellable core identity/company memory interviewer. Your job is to
 turn source material, voice samples, transcripts, corrections, and a short