@sellable/install 0.1.44 → 0.1.46

package/bin/sellable-install.mjs

@@ -1295,9 +1295,62 @@ function installClaude(opts) {
     ["mcp", "add", "--transport", "stdio", "sellable", "--", command, ...args],
     opts
   );
+  // Patch ~/.claude.json to add `alwaysLoad: true` so Claude Code v2.1.121+
+  // pre-loads all mcp__sellable__* tool schemas instead of deferring them
+  // behind ToolSearch (saves 2 round trips per `/sellable:create-campaign`
+  // session). Older Claude Code versions ignore the field — no harm.
+  patchClaudeAlwaysLoad(opts);
   return true;
 }
 
+function patchClaudeAlwaysLoad(opts) {
+  if (opts.dryRun) {
+    logVerbose(
+      `${C.grey}+ would set alwaysLoad: true on sellable MCP server in ~/.claude.json${C.reset}`
+    );
+    return;
+  }
+  const claudeJsonPath = join(homedir(), ".claude.json");
+  if (!existsSync(claudeJsonPath)) {
+    logVerbose(
+      `${C.grey}+ ~/.claude.json missing — skipping alwaysLoad patch (claude mcp add should have created it)${C.reset}`
+    );
+    return;
+  }
+  try {
+    const raw = readFileSync(claudeJsonPath, "utf8");
+    const config = JSON.parse(raw);
+    let touched = false;
+    // Top-level mcpServers.sellable (older claude versions)
+    if (config.mcpServers?.sellable) {
+      if (config.mcpServers.sellable.alwaysLoad !== true) {
+        config.mcpServers.sellable.alwaysLoad = true;
+        touched = true;
+      }
+    }
+    // Per-project mcpServers.sellable (current claude default)
+    for (const projectPath of Object.keys(config.projects || {})) {
+      const projServers = config.projects[projectPath]?.mcpServers;
+      if (projServers?.sellable && projServers.sellable.alwaysLoad !== true) {
+        projServers.sellable.alwaysLoad = true;
+        touched = true;
+      }
+    }
+    if (touched) {
+      writeFileSync(claudeJsonPath, JSON.stringify(config, null, 2), {
+        mode: 0o600,
+      });
+      logVerbose(
+        `${C.grey}+ patched ${claudeJsonPath} sellable.alwaysLoad = true${C.reset}`
+      );
+    }
+  } catch (err) {
+    logVerbose(
+      `${C.grey}+ could not patch alwaysLoad: ${err instanceof Error ? err.message : String(err)} (non-fatal)${C.reset}`
+    );
+  }
+}
+
 function installCodex(opts) {
   if (!commandExists("codex")) {
     const message =

package/package.json

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

package/skill-templates/create-campaign.md

@@ -253,10 +253,18 @@ Cool — I have this campaign as {company}. Who should the LinkedIn messages sen
 Sender options should include connected sender names if available, `same as
 me`, `I’ll paste a different sender profile`, and `Other / custom`.
 
-After the user confirms the subject and sender, run one lightweight company
-lookup if it has not already run, then ask the campaign setup questions. The
-setup questions should use the confirmed company context so they do not feel
-generic.
+After the user confirms the subject and sender, run one bounded lightweight
+company-context pass before asking the campaign setup questions. A sender
+LinkedIn profile lookup is not enough by itself unless it clearly includes the
+company's website, product category, customer, and offer context. If the host can
+run tools in parallel, use one parallel batch with at most 2-3 cheap lookups:
+`mcp__sellable__fetch_company` on a LinkedIn company URL from the profile when
+available; `WebFetch` for the company website/domain when available; otherwise
+one `WebSearch` for `{company} official website` or `{company} product`. If
+parallel tool calls are unavailable, do the single highest-confidence lookup
+first and continue. Do not run full company research, source discovery, Sales
+Nav, Prospeo, Signals, or multi-query browsing here. The goal is a fast 15-30
+second context read so the four setup questions feel specific.
 
 Before the identity gate, use this customer-facing shape:
 
@@ -400,7 +408,7 @@ updates.
        ```text
        You're in — {activeWorkspaceName} workspace, ready to roll.
 
-       Now — paste the LinkedIn profile URL of the person you'll be sending campaigns from. Usually that's you (the founder), or whoever's voice the messages should sound like.
+       Now — paste the LinkedIn profile URL of the person you'll be sending campaigns from. Usually that's you, or whoever's voice the messages should sound like.
 
        e.g. https://www.linkedin.com/in/your-handle
        ```
@@ -411,7 +419,7 @@ updates.
        ```text
        You're set up — your {activeWorkspaceName} workspace is ready.
 
-       Now — paste the LinkedIn profile URL of the person you'll be sending campaigns from. Usually that's you (the founder), or whoever's voice the messages should sound like.
+       Now — paste the LinkedIn profile URL of the person you'll be sending campaigns from. Usually that's you, or whoever's voice the messages should sound like.
 
        e.g. https://www.linkedin.com/in/your-handle
        ```