@sellable/install 0.1.158 → 0.1.159

package/agents/post-find-leads-message-scout.md

@@ -60,9 +60,11 @@ required message reference cannot be loaded through the MCP asset loader, return
    `get_subskill_prompt({ subskillName: "generate-messages" })`
 
 3. Load every packaged reference asset required by that prompt's Reference Asset
-   Loading section with `get_subskill_asset`. If a required asset cannot load
-   through the MCP asset loader, return `blocked` or `retry-needed` instead of
-   drafting from memory.
+   Loading section with `get_subskill_asset`: load the required pre-draft reference pack before
+   drafting, load final-pass references before approval, and `ai-tells.md` is part of the required pack
+   and never optional. If a required asset cannot
+   load through the MCP asset loader, return `blocked` / `retry-needed`; do not draft from
+   memory or from the prompt alone.
 4. Build positioning in a compact working note: buyer, pain, product, mechanism,
    proof boundary, source-use rule, and CTA.
 5. Draft 3 distinct first-message options: signal-led, product/mechanism-led,
@@ -89,6 +91,7 @@ Return the following to the parent thread:
 
 - proposed first-message template using supported `{{...}}` tokens
 - token fill rules and fallbacks
+- `Reference Asset Loading` note naming which assets were used and why
 - one rendered good-fill sample for a plausible passing campaign-table row
 - message-draft runtime status: `ready`, `blocked`, `retry-needed`, or `stale`
 - approve-or-revise recommendation
@@ -178,16 +181,33 @@ own revision. The parent renders the revised template and waits for
 - Engagement-source personalization is a special case, not the default opener.
   Do not write `saw you {{engagement_context}} on {{post_context}}`, `saw you
 reacted to`, `saw you engaging with`, or equivalent source-citation copy as a
-  default hook. For LinkedIn-post-sourced campaigns, you may reference the
-  source when it explains why the note exists, but keep it topic-level, not
-  activity-log-level. Good: `saw you in a few conversations around [topic], so
-hope this is relevant`, `saw you in a few conversations about [topic], so
-may be off, but this seemed relevant`, `saw you might be interested in [topic],
-so hope this is relevant`, `hope this is relevant if [topic] is on your plate`,
-or `saw you raise your hand for [topic], so figured this was (hopefully) worth sending`.
+  default hook. Sender-owned post sources are different: if the source post was
+  authored by the sender/client and the row proves a reaction/comment, prefer a
+  light first-person acknowledgment such as `appreciate you showing some love on
+  my post about [topic]` or `thanks for showing support on my [topic] post`.
+  Do not name a comment unless the row proves comment text, and do not infer
+  buyer intent from the reaction. Follow that acknowledgment with a soft
+  relevance bridge before any broad problem or product line. Good:
+  `figured this might be relevant if [channel/workflow] is becoming more of a
+  [GTM/pipeline/content] channel for [company/team]`. Bad: jumping directly
+  from `appreciate you showing some love...` to `a lot of B2B teams...` or
+  `most teams...`; that reads stitched together. Every line must make the next
+  line feel earned: source/post signal -> relevance bridge -> product/problem
+  -> next step. If adjacent lines could be swapped, deleted, or joined with
+  `anyway` without changing the meaning, rewrite the bridge or cut the orphan
+  line. For third-party LinkedIn-post-sourced
+  campaigns, keep the source topic-level. Good: `saw you in a few conversations
+around [topic], so hope this is relevant`, `saw you in a few conversations
+about [topic], so may be off, but this seemed relevant`, `saw you might be
+interested in [topic], so hope this is relevant`, `hope this is relevant if
+[topic] is on your plate`, or `found you in a thread about [topic], so may be
+off, but this seemed relevant`. Only use `saw you raise your hand for [topic],
+so figured this was (hopefully) worth sending` when the source was an explicit
+lead-magnet comment, reply, or opt-in.
 The cheekier `saw you raise your hand for [topic] (creepy to reach out based
 on that, i know) - but this felt too on the nose to ignore` version is also
-allowed when the sender's voice can carry it. Bad: `you commented on...`, `you reacted
+allowed only for explicit lead-magnet comments, replies, or opt-ins and when the
+sender's voice can carry it. Bad: `you commented on...`, `you reacted
 to...`, `saw you engaging with...`, `your LinkedIn activity...`, `you might
 not remember the thread...`, or `found you through [source] and your role
 looked close...`. Otherwise omit the engagement signal and use role/company/problem context.
@@ -196,9 +216,9 @@ looked close...`. Otherwise omit the engagement signal and use role/company/prob
   topic looked close` are blocked. If the source is too weak, omit it.
 - Do not assert fit from title/company. `Your [role] role at [company] looked
   close to this problem` is blocked. Keep the apologetic uncertainty instead:
-  `may be off, but if [workflow] is anywhere near your lane...`.
+  `may be off, but if [workflow] is relevant to what you're working on...`.
 - Low-pressure relevance opt-outs are allowed when they do not defend the
-  source: `p.s. if this is nowhere near your outbound workflow, ignore me`.
+  source: `p.s. if this is not relevant to your outbound workflow, ignore me`.
 - Do not use `Caught` as opener language. It reads unnatural in LinkedIn
   outreach.
 - Do not describe the sender in third person inside the outbound message.

package/bin/sellable-install.mjs

@@ -1256,8 +1256,8 @@ Desktop, then start a new thread.
 2. When the canonical prompt asks for \`references/*.md\`, load those files
    with \`mcp__sellable__get_subskill_asset({ subskillName: "interview", assetPath: "references/<file>.md" })\`.
 3. Follow the canonical prompt exactly. Save local memory only where that prompt
-   directs, under \`.sellable/configs/core/**\` and
-   \`.sellable/interviews/**\`.
+   directs, under \`~/.sellable/configs/core/**\` and
+   \`~/.sellable/interviews/**\`.
 
 ## MCP Prompt Fallback
 
@@ -1303,7 +1303,7 @@ Desktop, then start a new thread.
    If the response has \`hasMore=true\`, continue with \`nextOffset\` until
    \`hasMore=false\`.
 2. Follow the canonical prompt exactly. Read the relevant
-   \`.sellable/configs/**\` memory files it names.
+   \`~/.sellable/configs/**\` memory files it names.
 3. Apply the loaded memory silently to the user's requested writing or answer.
    If the user only asked to load voice, summarize the active rules briefly and
    ask what they want drafted, answered, or reviewed.
@@ -2079,7 +2079,7 @@ function patchClaudeAlwaysLoad(opts) {
 }
 
 function installCodex(opts) {
-  if (!commandExists("codex")) {
+  if (!opts.dryRun && !commandExists("codex")) {
     const message =
       "Codex CLI not found. Install/login to Codex, then rerun: sellable --host codex";
     if (opts.host === "all") {
@@ -2088,6 +2088,9 @@ function installCodex(opts) {
     }
     throw new Error(message);
   }
+  if (!opts.dryRun) {
+    mkdirSync(codexHome(), { recursive: true, mode: 0o700 });
+  }
   if (opts.server === "hosted") {
     run("codex", codexMcpAddArgs(opts), opts);
     const info = installCodexDesktopPlugin(opts);
@@ -2654,6 +2657,13 @@ async function main() {
         process.exit(2);
       }
       const token = rawArgs[2];
+      const authSetFlags = rawArgs.slice(3);
+      const dryRun = authSetFlags.includes("--dry-run");
+      const unknownAuthSetFlag = authSetFlags.find((arg) => arg !== "--dry-run");
+      if (unknownAuthSetFlag) {
+        console.error(`Unknown auth set option: ${unknownAuthSetFlag}`);
+        process.exit(2);
+      }
       if (!token) {
         console.error(
           "Usage: sellable auth set <token>\n" +
@@ -2678,9 +2688,13 @@ async function main() {
       writeJson(
         authPath(),
         { token, activeWorkspaceId: null, apiUrl },
-        { dryRun: false }
+        { dryRun }
       );
-      console.log(`✓ Token saved to ${authPath()}`);
+      if (dryRun) {
+        console.log(`Dry run: token would be saved to ${authPath()}`);
+      } else {
+        console.log(`✓ Token saved to ${authPath()}`);
+      }
       console.log(`  apiUrl: ${apiUrl}`);
       console.log(`  Continue in your agent:`);
       console.log(`    Claude Code: /sellable:create-campaign`);

package/package.json

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