@sellable/install 0.1.284 → 0.1.285

package/package.json

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

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

@@ -1358,9 +1358,11 @@ Message, and verify current-revision sample messages before final completion.
      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.
+     say it. Prefer sender-agnostic company/team language grounded in the
+     current workspace's verified company, offer, buyer, and proof, plus one
+     clear problem question. Do not reuse unrelated fixture/example customer
+     names, domains, verticals, product categories, use cases, or proof points
+     unless the current workspace/company research independently supports them.
      Before Message Drafting runs, the campaign brief must already include
      these shared-lane hard avoids and source-use rules. Do not rely on a
      failed first generation batch to discover that self-intros, generic
@@ -1370,7 +1372,10 @@ Message, and verify current-revision sample messages before final completion.
      Shared Signal Discovery samples may use a supported topic bridge such as
      "saw you around conversations about [high-level topic], so hope this is
      relevant" when the topic is grounded in source evidence and not
-     activity-log phrasing. Translate source/tool terms into prospect-facing
+     activity-log phrasing. Signal Discovery is only a lead-source provider;
+     do not infer a product category, buyer pain, offer, asset, CTA, or
+     provider-themed message direction from the lane/provider name.
+     Translate source/tool terms into prospect-facing
      business language; do not put internal workflow vocabulary such as
      "Codex-style workflow", "MCP", "agent workflows",
      "Claude Code", or "Claude-style agent workflows" in customer-facing
@@ -1535,7 +1540,10 @@ Message, and verify current-revision sample messages before final completion.
       `issues`.
       Shared Signal Discovery samples may use `"saw you around conversations
       about [high-level topic], so hope this is relevant"` when the topic is
-      supported by source evidence and not activity-log phrasing. Shared Cold
+      supported by source evidence and not activity-log phrasing. Signal
+      Discovery is only a lead-source provider; reject provider-themed campaign
+      copy unless that language is independently supported by the current
+      workspace/company research. Shared Cold
       Fallback samples must still reject source/conversation hedges such as
       `"hope this is relevant"`, `"might be interested"`, or `"saw you in a few
       conversations"`.