@sellable/install 0.1.246 → 0.1.248

package/package.json

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

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

@@ -908,6 +908,8 @@ Parent-thread handwritten copy or setting `currentStep` is not proof.
      Short form: Do not pass the warm template into Shared Signal Discovery or Shared Cold Fallback.
      Short form: Shared lanes must reject generic product-summary samples.
      Short form: Shared lanes must reject three nearly identical samples.
+     Short form: Shared lanes must reject low-confidence relevance hedges.
+     Short form: Shared lanes must reject internal workflow vocabulary.
      Short form: revise or rerun the packaged create-campaign/generate-messages path.
    - **Post Engagers** first-message style: short, casual, references the
      sender-authored post they engaged with, closed question, **no internal
@@ -940,9 +942,16 @@ Parent-thread handwritten copy or setting `currentStep` is not proof.
      product summaries, or repeated structure are bad. If the first generated
      batch violates these rules, rerun, but record that as a repaired UAT path
      rather than the desired zero-shot path.
+     Do not use low-confidence relevance hedges such as "hope this is
+     relevant" in Shared Signal Discovery samples. Translate source/tool terms
+     into prospect-facing business language; do not put internal workflow
+     vocabulary such as "Codex-style workflow", "MCP", "agent workflows", or
+     "Claude-style agent workflows" in customer-facing message one.
      Short form: Shared Signal Discovery uses no self-intro such as "I'm building Sellable".
      Short form: Shared Signal Discovery uses no self-intro such as "We're building Sellable".
      Short form: Shared Signal Discovery uses no "I've put together".
+     Short form: no low-confidence relevance hedge such as "hope this is relevant".
+     Short form: no internal workflow vocabulary such as "Codex-style workflow", "MCP", "agent workflows", or "Claude-style agent workflows".
    - **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
@@ -957,6 +966,11 @@ Parent-thread handwritten copy or setting `currentStep` is not proof.
      Sellable/Codex/Claude-Code feature summary
      across prospects. This is a single-message cold path unless the approved
      create-campaign message workflow proves a better delivery format.
+     Do not open with "hope this is relevant" or a similar low-confidence
+     relevance hedge. Do not use a repeated product-definition paragraph such
+     as "Sellable is a GTM system" across samples; every reviewed cold sample
+     should be specific enough to the role, company, or problem that the three
+     sample messages do not share the same body skeleton.
      Before Message Drafting runs, the campaign brief must already forbid
      self-intros, generic product summaries, opt-out shrugs, product-stack
      dumps, and repeated template structure. Do not let the first generation
@@ -968,6 +982,8 @@ Parent-thread handwritten copy or setting `currentStep` is not proof.
      Short form: Shared Cold Fallback uses no "I've put together".
      Short form: Shared Cold Fallback uses no opt-out shrug such as "If this isn't relevant, ignore me".
      Short form: Shared Cold Fallback uses no product-stack dump.
+     Short form: no low-confidence relevance hedge such as "hope this is relevant".
+     Short form: no repeated product-definition paragraph such as "Sellable is a GTM system".
     - Customer-visible evergreen lanes must enable ICP filtering before Message
       Drafting. This applies to Post Engagers, Shared Signal Discovery, and
       Shared Cold Fallback. Do not skip filtering for evergreen setup, even when
@@ -1055,8 +1071,9 @@ Parent-thread handwritten copy or setting `currentStep` is not proof.
       or a product-stack dump that repeats the same
       Sellable/Codex/Claude-Code feature summary across prospects. For all
       shared lanes, reject generic product-summary samples, repeated
-      near-identical samples, any sample with non-empty `issues`, and any
-      preserved Post Engagers opener; revise or rerun the packaged
+      near-identical samples, low-confidence relevance hedges such as "hope this
+      is relevant", internal workflow vocabulary, any sample with non-empty
+      `issues`, and any preserved Post Engagers opener; revise or rerun the packaged
       create-campaign/generate-messages path before reporting completion. Do not
       approve or final-report samples with `verdict:"passed"` and non-empty
       `issues`.