@sellable/install 0.1.91 → 0.1.93

package/README.md

@@ -6,6 +6,16 @@ Installs Sellable MCP for Claude Code and Codex.
 npx -y @sellable/install@latest --host all
 ```
 
+After install, `sellable create` is a terminal helper that prints the correct
+agent command for launching a campaign:
+
+```bash
+sellable create
+```
+
+Campaign creation itself runs inside Claude Code or Codex, where the Sellable
+MCP tools and approval flow are available.
+
 If you do not pass a token, the installer prompts you for one and shows where to get it.
 
 The installer uses package stdio MCP by default:

package/bin/sellable-install.mjs

@@ -129,9 +129,15 @@ function usage() {
   return `Sellable agent installer
 
 Usage:
+  sellable create
   sellable-install [options]
   npx -y @sellable/install@latest -- [options]
 
+Commands:
+  create                   Show how to launch the create-campaign workflow.
+  auth set <token>         Save a Sellable API token for first-run auth.
+  uninstall                Remove Sellable host config and installed artifacts.
+
 Options:
   --host <host>             claude, codex, or all. Default: all
   --server <mode>           package, local, or hosted. Default: package
@@ -158,6 +164,34 @@ Auth:
 `;
 }
 
+function printCreateCommandHint() {
+  printBanner();
+  console.log(
+    `  ${C.bold}Create campaigns from Claude Code or Codex.${C.reset}`
+  );
+  console.log("");
+  console.log(
+    `  ${C.grey}The terminal command installs and verifies Sellable. Campaign creation runs inside your agent session so the workflow can use MCP tools, live state, and approval gates.${C.reset}`
+  );
+  console.log("");
+  console.log(`   ${"═".repeat(63)}`);
+  console.log(`    ${C.bold}Start a Sellable campaign:${C.reset}`);
+  console.log(`   ${"═".repeat(63)}`);
+  console.log("");
+  console.log("");
+  printAgentBox("Using Claude Code?", "claude", "/sellable:create-campaign");
+  console.log("");
+  console.log("");
+  printAgentBox("Using Codex?", "codex", "$sellable:create-campaign");
+  console.log("");
+  console.log(`   ${"─".repeat(63)}`);
+  console.log(`    ${C.grey}If those commands are missing, run:${C.reset}`);
+  console.log("");
+  console.log(`      ${C.cyan}sellable --host all${C.reset}`);
+  console.log(`      ${C.cyan}sellable --verify-only --host all${C.reset}`);
+  console.log("");
+}
+
 function parseArgs(argv) {
   const opts = {
     host: process.env.SELLABLE_INSTALL_HOST || "all",
@@ -1524,8 +1558,17 @@ exec npx -y ${INSTALL_PACKAGE_SPEC} "$@"
   writeFile(binPath, shim, opts, 0o755);
 }
 
+const WATCH_MODE_DRIVER_ENV = {
+  claude: "SELLABLE_WATCH_MODE_DRIVER=claude",
+  codex: "SELLABLE_WATCH_MODE_DRIVER=codex",
+};
+
 function withWatchModeDriver(command, args, driver) {
-  return ["env", [`SELLABLE_WATCH_MODE_DRIVER=${driver}`, command, ...args]];
+  const envArg = WATCH_MODE_DRIVER_ENV[driver];
+  if (!envArg) {
+    throw new Error(`Unknown watch mode driver: ${driver}`);
+  }
+  return ["env", [envArg, command, ...args]];
 }
 
 function mcpCommand(opts) {
@@ -2236,6 +2279,10 @@ async function main() {
       runUninstall();
       process.exit(0);
     }
+    if (rawArgs[0] === "create") {
+      printCreateCommandHint();
+      process.exit(0);
+    }
     const opts = parseArgs(process.argv.slice(2));
     if (opts.help) {
       console.log(usage());

package/package.json

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

package/skill-templates/create-campaign.md

@@ -191,6 +191,11 @@ a fresh watch link once with `create_campaign({ campaignId })` or `get_campaign`
 and print that link. Do not claim the browser was opened, inspected, or
 synchronized.
 
+Never print a placeholder watch link such as "Open campaign" or "link will
+update once the shell is created." If the shell is not created yet, call
+`create_campaign` first. If `create_campaign` does not return `watchUrl`, stop
+and surface the missing watch-link error before lead sourcing.
+
 After every `update_campaign({ campaignId, currentStep })`, use
 `get_campaign_navigation_state` when available as a compact orientation check:
 match the saved campaign state to the expected watch-link step, explain the
@@ -565,6 +570,8 @@ updates.
    `message-validation.md` proves the message-review safety-gate workflow ran,
    `message-review.md` approves the template, rubrics are saved, and the
    approved message set is synced into the campaign brief.
+   Do not ask the user to approve the brief before shell creation unless they
+   explicitly requested a no-write draft; the shell itself is the review surface.
 6. The main thread owns watch navigation. Call
    `mcp__sellable__update_campaign({ campaignId, currentStep })` before major
    visible work so the user can watch progress in the app: `create-offer` for