@sellable/install 0.1.233 → 0.1.234

package/bin/sellable-install.mjs

@@ -37,7 +37,7 @@ function getInstallVersion() {
   }
 }
 
-const CODEX_PLUGIN_VERSION = "0.1.50";
+const CODEX_PLUGIN_VERSION = "0.1.51";
 const CODEX_PLUGIN_COMPAT_VERSIONS = [
   "0.1.8",
   "0.1.9",

package/package.json

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

package/skill-templates/create-evergreen-campaigns.md

@@ -696,13 +696,20 @@ Parent-thread handwritten copy or setting `currentStep` is not proof.
      "my post" unless the selected source post was actually authored by the
      sending sender. Do not thank the prospect for showing support, reacting,
      commenting, or popping up unless this is a sender-owned Post Engagers lane
-     with sender-authored source evidence.
+     with sender-authored source evidence. When the shared lane has multiple
+     senders, the copy must be safe for every attached sender to send. Do not
+     use founder-only first person such as "I'm building", "my company", "my
+     team", or "I have a framework" unless every attached sender can credibly
+     say it. Prefer sender-agnostic company/team language such as "we're
+     helping CX teams..." or "at cxconnect.ai, we help..." and one clear
+     problem question.
    - **Shared Cold Fallback** first-message style: cold, direct, and cohesive.
      It must not pretend there was engagement, must not say "saw you pop up",
      and must not use a standalone name line followed by "Hey there" or other
      generic greeting. It should open with a light role/company/problem
-     observation, avoid awkward phrases like "looks like a team where", and ask
-     one clear problem question. This is a single-message
+     observation, avoid awkward phrases like "looks like a team where", avoid
+     founder-only first person unless every attached sender can credibly say it,
+     and ask one clear problem question. This is a single-message
      cold path unless the approved create-campaign message workflow proves a
      better delivery format.
    - Every customer-visible lane must run Message Drafting from the current