@sellable/install 0.1.120 → 0.1.122

package/README.md

@@ -6,6 +6,16 @@ Installs Sellable MCP for Claude Code and Codex.
 npx -y @sellable/install@latest --host all
 ```
 
+Paste that command in your terminal, not inside the Codex chat. Mac/Linux
+users can use Terminal. Windows users can use PowerShell or Windows Terminal;
+if PowerShell blocks `npx`, run:
+
+```powershell
+npx.cmd -y @sellable/install@latest --host all
+```
+
+After install, restart Codex Desktop so the Sellable skill appears.
+
 After install, `sellable create` is a terminal helper that prints the correct
 agent command for launching a campaign:
 

package/agents/source-scout-linkedin-engagement.md

@@ -60,9 +60,14 @@ currentStep: "signal-discovery" })` before sampling so the watched Signal
    sampled/projected headline-fit rate clears the 10% planning floor. Treat the
    10% floor as a reject threshold, not as the scrape-count denominator when the
    actual sample rate is higher.
-8. Select/promote enough right-content posts to plausibly hit the target. If the
-   warm Signals pool is useful but too small, return the expected warm range and
-   recommend Sales Nav/Prospeo for scale instead of padding with noisy posts.
+8. Select/promote enough right-content posts to plausibly hit the target. After
+   the sample math is known, treat the promoted sample set and final scrape set
+   as separate: recommend the smallest right-content post subset whose
+   scrapable/reachable engagers clears the required engager count, with a modest
+   buffer when needed. If one 1,200+ engager post clears a ~1,000-engager target,
+   recommend scraping that one post, not all 3 sample posts. If the warm Signals
+   pool is useful but too small, return the expected warm range and recommend
+   Sales Nav/Prospeo for scale instead of padding with noisy posts.
 9. Return false positives and dead ends explicitly.
 
 Return a concise structured result with:

package/bin/sellable-install.mjs

@@ -1,6 +1,7 @@
 #!/usr/bin/env node
 import { spawnSync } from "node:child_process";
 import {
+  cpSync,
   existsSync,
   mkdirSync,
   readdirSync,
@@ -30,16 +31,6 @@ function getInstallVersion() {
   }
 }
 
-function getMcpVersion() {
-  try {
-    const r = spawnSync("npm", ["view", "@sellable/mcp", "version"], {
-      encoding: "utf8",
-      timeout: 5000,
-    });
-    if (r.status === 0 && r.stdout) return r.stdout.trim();
-  } catch {}
-  return "latest";
-}
 const CODEX_PLUGIN_VERSION = "0.1.33";
 const CODEX_PLUGIN_COMPAT_VERSIONS = [
   "0.1.8",
@@ -282,13 +273,59 @@ function run(command, args, opts = {}) {
   return result;
 }
 
-function commandExists(command) {
-  const result = spawnSync("sh", ["-lc", `command -v ${command}`], {
-    encoding: "utf8",
-  });
+function isWindowsPlatform(platform = process.platform) {
+  return platform === "win32";
+}
+
+function packageRunnerCommand(platform = process.platform) {
+  return isWindowsPlatform(platform) ? "npx.cmd" : "npx";
+}
+
+function packageManagerCommand(platform = process.platform) {
+  return isWindowsPlatform(platform) ? "npm.cmd" : "npm";
+}
+
+function commandExists(command, platform = process.platform) {
+  const result = isWindowsPlatform(platform)
+    ? spawnSync("where.exe", [command], {
+        encoding: "utf8",
+      })
+    : spawnSync("sh", ["-lc", `command -v ${command}`], {
+        encoding: "utf8",
+      });
   return result.status === 0;
 }
 
+function commandExistsDetails(command, platform = process.platform) {
+  const result = isWindowsPlatform(platform)
+    ? spawnSync("where.exe", [command], {
+        encoding: "utf8",
+      })
+    : spawnSync("sh", ["-lc", `command -v ${command}`], {
+        encoding: "utf8",
+      });
+  return {
+    exists: result.status === 0,
+    stdout: (result.stdout || "").trim(),
+    platform,
+  };
+}
+
+function getMcpVersion() {
+  try {
+    const r = spawnSync(
+      packageManagerCommand(),
+      ["view", "@sellable/mcp", "version"],
+      {
+        encoding: "utf8",
+        timeout: 5000,
+      }
+    );
+    if (r.status === 0 && r.stdout) return r.stdout.trim();
+  } catch {}
+  return "latest";
+}
+
 function authPath() {
   return join(homedir(), ".sellable", "config.json");
 }
@@ -420,7 +457,26 @@ function ensureSymlink(target, linkPath, opts) {
     // ignore
   }
   const rel = relative(dirname(linkPath), target);
-  symlinkSync(rel, linkPath, "dir");
+  try {
+    symlinkSync(rel, linkPath, "dir");
+  } catch (err) {
+    const code = err && typeof err === "object" ? err.code : "";
+    const message = err instanceof Error ? err.message : String(err);
+    const isDenied =
+      code === "EPERM" ||
+      code === "EACCES" ||
+      /privilege|permission|operation not permitted/i.test(message);
+
+    if (!isWindowsPlatform() || !isDenied) {
+      throw err;
+    }
+
+    logVerbose(
+      `${C.grey}+ symlink denied on Windows; copying compatibility cache ${linkPath}${C.reset}`
+    );
+    rmSync(linkPath, { recursive: true, force: true });
+    cpSync(target, linkPath, { recursive: true, force: true });
+  }
 }
 
 function codexPluginManifest(opts) {
@@ -492,7 +548,7 @@ function codexPluginMcp(opts) {
     mcpServers: {
       sellable: {
         type: "stdio",
-        command: "npx",
+        command: packageRunnerCommand(),
         args: ["-y", opts.mcpPackage],
         env: {
           SELLABLE_WATCH_MODE_DRIVER: "codex",
@@ -608,8 +664,8 @@ instruction loading, file lookup, plugin cache versions, missing linked files,
 or tool discovery. Start in product language:
 
 \`\`\`text
-I’ll help you launch this as a Sellable campaign. First I’ll resolve the
-client/company this campaign is for, then I’ll turn that into a campaign brief
+I’ll help you launch this as a Sellable campaign. First I’ll research the
+person/company this campaign is for, then I’ll turn that into a campaign brief
 before anything is created.
 \`\`\`
 
@@ -655,10 +711,12 @@ should say:
 - that approval authorizes scouting/search only, not lead import or sending
 
 Do not surface blanket source heuristics as product copy. Make the
-recommendation specific to the campaign. If Signal Discovery is recommended,
-name the exact post themes you will search. If relevant public conversations
-look unlikely, recommend the specific Sales Nav or Prospeo lane instead and say
-why. Do not call \`search_signals\`, \`search_sales_nav\`, \`search_prospeo\`,
+recommendation specific to the campaign. If LinkedIn engagement is recommended,
+name the exact post themes you will search and avoid using "Signal Discovery" in
+customer-facing chat; that is the internal provider/app label. If relevant
+public conversations look unlikely, recommend the specific Sales Nav or Prospeo
+lane instead and say why. Do not call \`search_signals\`, \`search_sales_nav\`,
+\`search_prospeo\`,
 \`fetch_post_engagers\`, or provider-scoped subagents until the user approves this
 source plan or explicitly chooses a different source.
 
@@ -677,9 +735,12 @@ precision, and referral paths, but it does not provide hiring-by-role filters;
 say that distinction plainly in the source-plan gate.
 
 After scouting, ask for a second approval on the concrete source action. For
-Signal Discovery, name how many selected posts will be scraped, the target
-engager/source-candidate volume, and the internal campaign-table execution-slice
-size. For Sales Nav or Prospeo, name the specific approved import lane and source lead count.
+LinkedIn engagement (\`signal-discovery\` internally), name how many recommended
+posts will be scraped, the target engager/source-candidate volume, and the
+internal campaign-table execution-slice size. N must be the smallest
+right-content post set that clears the source target, not the default 3
+promoted sample posts. For Sales Nav or Prospeo, name the specific approved
+import lane and source lead count.
 Do not call \`import_leads\` or \`confirm_lead_list\` until this second approval is
 granted.
 
@@ -838,10 +899,10 @@ customer-facing progress copy.
 
 Do not treat the active Sellable workspace as the campaign subject. The
 workspace only tells you where the campaign will be saved. Before buyer, CTA,
-proof, or source questions, identify the campaign identity: the person/profile
-or company this campaign is for, plus enough company/product context to build
-the brief. This is only the client-prospect/bootstrap identity for
-\`clientProspectId\` or \`senderLinkedinUrl\`; it is not a connected-sender check.
+proof, or source questions, identify the person/profile or company this
+campaign is for, plus enough current company/product context to build the
+brief. This client/company lookup feeds \`clientProspectId\` or
+\`senderLinkedinUrl\`; it is not a connected-sender check.
 
 Do not call \`mcp__sellable__list_senders\`, \`mcp__sellable__get_sender\`, or
 surface connected/missing sender state during setup, brief, source, filter, or
@@ -865,19 +926,20 @@ first:
   only if a URL/domain is also available.
 
 Then summarize what you found in one or two lines and ask the user to confirm
-the campaign identity/focus before continuing. Do not mention connected sender
-availability in this confirmation.
+the current company/focus before continuing, especially if public website data
+may be stale. Do not mention connected sender availability in this confirmation.
 
 If the user did not provide the launch identity, ask in normal chat for the
-LinkedIn profile or company website to use as the campaign identity. Do not ask
+LinkedIn profile URL first, with the company website as the fallback. Do not ask
 them to choose an input type with the structured question tool:
 
 \`\`\`text
 I’m ready to build this in {workspace}.
 
-First, paste the LinkedIn profile or company website for the client/company this
-campaign is for. I’ll use that to resolve the campaign identity before we pick
-the target, offer, proof, and lead source.
+What is your LinkedIn profile URL? If you do not have it handy, send your
+company website instead. I’ll research the person and company from that, then
+ask you to correct anything stale before we pick the target, offer, proof, and
+lead source.
 \`\`\`
 
 After the user pastes a URL/domain, do the lightweight lookup. For a LinkedIn
@@ -887,18 +949,28 @@ most recent company from the profile. For a company website, call
 LinkedIn profile URL is available, retain it as \`senderLinkedinUrl\` for
 \`create_campaign\`; if a \`clientProspectId\` is available, pass that instead.
 
-After the user confirms the campaign identity, 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 company/focus, run one lightweight company lookup
+if it has not already run, then ask an offer-readiness question before inferred
+strategy hardens:
+
+\`\`\`text
+Do you already know the offer for this campaign, should I use the researched
+recommendation, or should we shape the offer together? If the website is stale,
+tell me what is current before I build the brief.
+\`\`\`
+
+The setup questions should use the confirmed company context so they do not feel
+generic. When you present a recommendation, introduce it as based on the
+research you just did and keep it editable.
 
 Before the identity gate, use this customer-facing shape:
 
 \`\`\`text
 I’m ready to build the campaign in {workspace}.
 
-First I’ll resolve the client/company this campaign is for. I’ll use that
-context to choose the target, offer, proof, and lead source.
+First I’ll research the person/company this campaign is for. I’ll use that
+context to recommend a target, offer, proof, and lead source, then you can
+correct anything stale before I build from it.
 
 Then I’ll turn that into a campaign brief for you to approve before anything is created.
 \`\`\`
@@ -1266,17 +1338,17 @@ show you the draft next so you can approve it or change it.
 Good opening:
 
 \`\`\`text
-I’ll help you launch this as a Sellable campaign. First I’ll resolve the
-client/company this campaign is for, then I’ll turn that into a campaign brief
-before any leads are imported or anything can send.
+I’ll help you launch this as a Sellable campaign. First I’ll research the
+person/company this is for, then I’ll turn that into a campaign brief before
+any leads are imported or anything can send.
 \`\`\`
 
 Good identity setup:
 
 \`\`\`text
-I’ll confirm the client/company this campaign is for before we pick the target,
-offer, proof, and lead source. Paste a LinkedIn profile or company website and
-I’ll resolve the campaign identity before the setup choices.
+I’ll ask for the LinkedIn profile URL first, with the company website as a
+fallback. Then I’ll show the researched recommendation and you can correct
+anything stale before we pick the target, offer, proof, and lead source.
 \`\`\`
 
 Bad:
@@ -1767,7 +1839,7 @@ function withWatchModeDriver(command, args, driver) {
 
 function mcpCommand(opts) {
   if (opts.server === "package") {
-    return ["npx", ["-y", opts.mcpPackage]];
+    return [packageRunnerCommand(), ["-y", opts.mcpPackage]];
   }
   if (opts.server === "local") {
     if (!opts.localCommand) {
@@ -1789,6 +1861,33 @@ function mcpCommandForHost(opts, driver) {
   return withWatchModeDriver(command, args, driver);
 }
 
+function codexMcpAddArgs(opts) {
+  const [command, args] = mcpCommand(opts);
+  if (command === "hosted") {
+    return ["mcp", "add", "sellable", "--url", args[0]];
+  }
+
+  if (isWindowsPlatform()) {
+    return [
+      "mcp",
+      "add",
+      "sellable",
+      "--env",
+      WATCH_MODE_DRIVER_ENV.codex,
+      "--",
+      command,
+      ...args,
+    ];
+  }
+
+  const [wrappedCommand, wrappedArgs] = withWatchModeDriver(
+    command,
+    args,
+    "codex"
+  );
+  return ["mcp", "add", "sellable", "--", wrappedCommand, ...wrappedArgs];
+}
+
 function installClaude(opts) {
   if (!commandExists("claude")) {
     const message =
@@ -1887,17 +1986,16 @@ function installCodex(opts) {
     throw new Error(message);
   }
   if (opts.server === "hosted") {
-    run("codex", ["mcp", "add", "sellable", "--url", opts.hostedUrl], opts);
+    run("codex", codexMcpAddArgs(opts), opts);
     const info = installCodexDesktopPlugin(opts);
     return { installed: true, ...info };
   }
-  const [command, args] = mcpCommandForHost(opts, "codex");
   run("codex", ["mcp", "remove", "sellable"], {
     ...opts,
     dryRun: opts.dryRun,
     allowFail: true,
   });
-  run("codex", ["mcp", "add", "sellable", "--", command, ...args], opts);
+  run("codex", codexMcpAddArgs(opts), opts);
   const info = installCodexDesktopPlugin(opts);
   return { installed: true, ...info };
 }

package/package.json

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

package/skill-templates/create-campaign.md

@@ -86,8 +86,8 @@ instruction loading, file lookup, plugin cache versions, missing linked files,
 or tool discovery. Start in product language:
 
 ```text
-I’ll help you launch this as a Sellable campaign. First I’ll resolve the
-client/company this campaign is for, then I’ll turn that into a campaign brief
+I’ll help you launch this as a Sellable campaign. First I’ll research the
+person/company this campaign is for, then I’ll turn that into a campaign brief
 before we move into lead sourcing.
 ```
 
@@ -139,10 +139,12 @@ should say:
 - what approval covers in one concise line
 
 Do not surface blanket source heuristics as product copy. Make the
-recommendation specific to the campaign. If Signal Discovery is recommended,
-name the exact post themes you will search. If relevant public conversations
-look unlikely, recommend the specific Sales Nav or Prospeo lane instead and say
-why. Do not call `search_signals`, `search_sales_nav`, `search_prospeo`,
+recommendation specific to the campaign. If LinkedIn engagement is recommended,
+name the exact post themes you will search and avoid using "Signal Discovery" in
+customer-facing chat; that is the internal provider/app label. If relevant
+public conversations look unlikely, recommend the specific Sales Nav or Prospeo
+lane instead and say why. Do not call `search_signals`, `search_sales_nav`,
+`search_prospeo`,
 `fetch_post_engagers`, or provider-scoped subagents until the user approves this
 source plan or explicitly chooses a different source.
 
@@ -161,10 +163,13 @@ precision, and referral paths, but it does not provide hiring-by-role filters;
 say that distinction plainly in the source-plan gate.
 
     After scouting, ask for a second approval on the concrete source action. For
-    Signal Discovery, name how many selected posts will be scraped and the
-    target engager/source-candidate volume. For Sales Nav or Prospeo, name the
-    specific approved import lane and source lead count. Keep the internal
-    15-row campaign-table execution slice separate from source sampling.
+    LinkedIn engagement (`signal-discovery` internally), name how many
+    recommended posts will be scraped and the target engager/source-candidate
+    volume. N must be the smallest right-content post set that clears the source
+    target, not the default 3 promoted sample posts. For Sales Nav or Prospeo,
+    name the specific approved import lane and source lead count. Keep the
+    internal 15-row campaign-table execution slice separate from source
+    sampling.
 
 Do not call `import_leads` or `confirm_lead_list` until this second approval is
 granted.
@@ -181,16 +186,15 @@ granted.
     should `confirm_lead_list({ reviewBatchLimit: 15 })` copy confirmed rows into
     the campaign table and return the initial campaign-table execution slice rows.
 
-For Signal Discovery, the customer-facing approval card must use the exact
-action shape "Approve scraping N Signal Discovery posts?" and the chat summary
-should be a compact `## Source Recommendation` block with:
+For LinkedIn engagement, the customer-facing approval card must use the exact
+action shape "Approve scraping N recommended LinkedIn posts?" and the chat
+summary should be a compact `## Source Recommendation` block with:
 
-- goal: about 300 headline-fit prospects that pass the Signal Discovery
-  headline criteria for now
+- goal: about 300 headline-fit prospects from relevant LinkedIn engagement
 - source-candidate plan: use sample math first: target headline-fit prospects
   divided by sampled headline-pass rate. If there is no stronger sample, use
   about 1,500 raw engagers from the 20% working headline-pass assumption.
-- planning floor: continue with Signal Discovery only when sampled/projected
+- planning floor: continue with LinkedIn engagement only when sampled/projected
   headline-fit rate is at least 10%; below that, move to Sales Nav recent
   activity instead of scraping noisy engagers. Do not use the 10% floor as the
   scrape-count denominator when the actual sample rate is higher.
@@ -394,10 +398,10 @@ customer-facing progress copy.
 
 Do not treat the active Sellable workspace as the campaign subject. The
 workspace only tells you where the campaign will be saved. Before buyer, CTA,
-proof, or source questions, identify the campaign identity: the person/profile
-or company this campaign is for, plus enough company/product context to build
-the brief. This is only the client-prospect/bootstrap identity for
-`clientProspectId` or `senderLinkedinUrl`; it is not a connected-sender check.
+proof, or source questions, identify the person/profile or company this
+campaign is for, plus enough current company/product context to build the
+brief. This client/company lookup feeds `clientProspectId` or
+`senderLinkedinUrl`; it is not a connected-sender check.
 
 Do not call `mcp__sellable__list_senders`, `mcp__sellable__get_sender`, or
 surface connected/missing sender state during setup, brief, source, filter, or
@@ -421,19 +425,20 @@ first:
   only if a URL/domain is also available.
 
 Then summarize what you found in one or two lines and ask the user to confirm
-the campaign identity/focus before continuing. Do not mention connected sender
-availability in this confirmation.
+the current company/focus before continuing, especially if public website data
+may be stale. Do not mention connected sender availability in this confirmation.
 
 If the user did not provide the launch identity, ask in normal chat for the
-LinkedIn profile or company website to use as the campaign identity. Do not ask
+LinkedIn profile URL first, with the company website as the fallback. Do not ask
 them to choose an input type with the structured question tool:
 
 ```text
 I’m ready to build this in {workspace}.
 
-First, paste the LinkedIn profile or company website for the client/company this
-campaign is for. I’ll use that to resolve the campaign identity before we pick
-the target, offer, proof, and lead source.
+What is your LinkedIn profile URL? If you do not have it handy, send your
+company website instead. I’ll research the person and company from that, then
+ask you to correct anything stale before we pick the target, offer, proof, and
+lead source.
 ```
 
 After the user pastes a URL/domain, do the lightweight lookup. For a LinkedIn
@@ -443,10 +448,19 @@ most recent company from the profile. For a company website, call
 LinkedIn profile URL is available, retain it as `senderLinkedinUrl` for
 `create_campaign`; if a `clientProspectId` is available, pass that instead.
 
-After the user confirms the campaign identity, 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 company/focus, run one lightweight company lookup
+if it has not already run, then ask an offer-readiness question before inferred
+strategy hardens:
+
+```text
+Do you already know the offer for this campaign, should I use the researched
+recommendation, or should we shape the offer together? If the website is stale,
+tell me what is current before I build the brief.
+```
+
+The setup questions should use the confirmed company context so they do not feel
+generic. When you present a recommendation, introduce it as based on the
+research you just did and keep it editable.
 
 ### Sufficient Intake Bypass
 
@@ -474,9 +488,9 @@ If the invocation or any later user message explicitly asks for "yolo mode",
 me", "use best estimates", or "just run it", enable YOLO mode for the rest of
 the run. Treat YOLO as `interactionMode: "autonomous"` plus an intake policy:
 
-- If campaign identity is missing, ask only for the LinkedIn profile or company
-  website in normal chat; do not ask buyer, offer, proof, source, or filter setup
-  questions before that.
+- If the campaign subject is missing, ask only for the LinkedIn profile URL
+  first, with company website as the fallback, in normal chat; do not ask buyer,
+  offer, proof, source, or filter setup questions before that.
 - Treat any freeform directions already provided, or added later by the user, as
   operator directions for the rest of the run. If directions conflict, the newest
   user direction wins.
@@ -498,8 +512,9 @@ Before the identity gate, use this customer-facing shape:
 ```text
 I’m ready to build the campaign in {workspace}.
 
-First I’ll resolve the client/company this campaign is for. I’ll use that
-context to choose the target, offer, proof, and lead source.
+First I’ll research the person/company this campaign is for. I’ll use that
+context to recommend a target, offer, proof, and lead source, then you can
+correct anything stale before I build from it.
 
 Then I’ll turn that into a campaign brief for you to approve before any leads
 are sourced.
@@ -634,9 +649,9 @@ updates.
        ```text
        You're in — {activeWorkspaceName} workspace, ready to roll.
 
-       Now — paste the LinkedIn profile or company website for the client/company this campaign is for. I’ll use that to resolve the campaign identity before we pick the target, offer, proof, and lead source.
+      Now — what is your LinkedIn profile URL? If you do not have it handy, send your company website instead. I’ll research the person and company from that, then ask you to correct anything stale before we pick the target, offer, proof, and lead source.
 
-       e.g. https://example.com or https://www.linkedin.com/in/client-handle
+      e.g. https://www.linkedin.com/in/client-handle or https://example.com
        ```
 
      - If `isReturningUser === false`, prepend ONE line confirming the new
@@ -645,9 +660,9 @@ updates.
        ```text
        You're set up — your {activeWorkspaceName} workspace is ready.
 
-       Now — paste the LinkedIn profile or company website for the client/company this campaign is for. I’ll use that to resolve the campaign identity before we pick the target, offer, proof, and lead source.
+      Now — what is your LinkedIn profile URL? If you do not have it handy, send your company website instead. I’ll research the person and company from that, then ask you to correct anything stale before we pick the target, offer, proof, and lead source.
 
-       e.g. https://example.com or https://www.linkedin.com/in/client-handle
+      e.g. https://www.linkedin.com/in/client-handle or https://example.com
        ```
 
      No other lines. No "all set", no "signed in", no other acknowledgement.