@sellable/mcp 0.1.449 → 0.1.451

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sellable/mcp",
-  "version": "0.1.449",
+  "version": "0.1.451",
   "type": "module",
   "description": "Sellable MCP server for Claude Code and Codex campaign workflows",
   "main": "dist/index.js",

package/skills/create-campaign-v2/references/gold-standard-message-examples.md

@@ -446,22 +446,47 @@ Tokenized shape:
 
 Hey there
 
-Thanks for the support on my post about {{post_topic_line}}
+Saw you pop up on my post about {{post_topic_line}}
+
+This one
+{{post_url}}
+
+Looks like you lead {{plain_buyer_function}} at {{company_name}}, right?
+
+{{custom_closed_question}}
 ```
 
 Transfer rules:
 
 - Do not hardcode a post topic. Fill `{{post_topic_line}}` from the actual
-  selected sender-authored post or use a safer source-specific phrase.
-- Do not add a relevance question, CTA, product line, or extra paragraph after
-  the thank-you line. The reply-rate lesson is the casual warm acknowledgment,
-  not a cold pitch appended to it.
+  selected sender-authored post or use a safer source-specific phrase. The best
+  lines sound like Justin's CXConnect example: a specific topic in normal human
+  words plus a light aside after a hyphen.
+- Include the engaged post URL on its own line after `This one` when row/source
+  data has it. The link reminds the prospect why the message is relevant and
+  keeps this clearly in the Post Engagers motion instead of feeling like generic
+  Signal Discovery.
+- Fill `{{plain_buyer_function}}` with an easy-to-understand buyer function or
+  category, such as `customer success`, `CX operations`, `founder-led sales`,
+  `sales`, `growth`, or `LinkedIn outbound`. Do not turn this line into a
+  feature list or internal workflow description.
+- Fill `{{custom_closed_question}}` from the post topic, buyer function, company
+  context, and the current offer category. The question should be easy to answer,
+  closed-ended, and specific to that prospect. Do not reuse the same generic
+  question across every row.
+- The product/category wording in the question should be plain and immediately
+  legible, for example `LinkedIn outbound`, `customer success`, `CX operations`,
+  `support`, or `post-sales`. Avoid feature-heavy phrasing such as `manual
+  research + follow-up process`, `lead filters`, `workflow`, `sequence setup`,
+  or internal mechanism language.
+- Do not add a meeting ask, product pitch, proof block, or extra paragraph after
+  the custom closed question. The reply-rate lesson is the casual warm
+  acknowledgment, concrete post reminder, and low-friction custom question, not a
+  cold pitch appended to it.
 - Do not use "showing some love"; it reads too casual for executive/VP/director
   contacts.
-- Keep the thank-you line. The point of this motion is acknowledging real
-  sender-owned support without appending a cold relevance question. Do not
-  flatten it back to "saw you pop up" unless the sender specifically asks for
-  that wording.
+- Keep the post-engager acknowledgment. The point of this motion is acknowledging
+  real sender-owned support without pretending this is generic cold outreach.
 - Do not copy this shape into shared lanes, third-party thread sources, or cold
   fallback campaigns.
 - Do not pitch, ask for a meeting, or mention internal product vocabulary in

package/skills/create-evergreen-campaigns/SKILL.md

@@ -1330,21 +1330,35 @@ Message, and verify current-revision sample messages before final completion.
      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, and stops after the thank-you
-     line. Use **no internal vocabulary, no pitch, no meeting ask, no product
-     line, and no relevance question** in message one:
+     sender-authored post they engaged with, includes the post URL as a concrete
+     reminder, uses an easy buyer-function/category line, and ends with one
+     row-custom closed question. Use **no internal vocabulary, no meeting ask,
+     no proof block, no feature-stack category, and no generic static question**
+     in message one:
 
      ```
      {{first_name}}
 
      Hey there
 
-     Thank you for the support on my post about {{post_topic_line}}
+     Saw you pop up on my post about {{post_topic_line}}
+
+     This one
+     {{post_url}}
+
+     Looks like you lead {{plain_buyer_function}} at {{company_name}}, right?
+
+     {{custom_closed_question}}
      ```
 
-     Do not add any paragraph after the thank-you line. In particular, do not
-     append `curious, are you trying...`, `open to...`, `worth seeing...`, or
-     Sellable/product copy to a Post Engagers first message.
+     `{{custom_closed_question}}` must be specific to the post topic, buyer
+     function, company context, and current offer category. The category should
+     be easy to understand, for example `LinkedIn outbound`, `customer success`,
+     `CX operations`, `support`, `sales`, or `growth`; do not use feature-heavy
+     phrasing like `manual research + follow-up process`, `lead filters`, or
+     `sequence setup`. Do not add any paragraph after the custom closed question.
+     In particular, do not append `open to...`, `worth seeing...`, a meeting ask,
+     proof block, or Sellable/product copy to a Post Engagers first message.
 
    - **Shared Signal Discovery** first-message style: short, casual, starts
      from the real public business theme or buyer problem supported by the row.

package/skills/generate-messages/SKILL.md

@@ -227,17 +227,24 @@ when those shared lanes were sourced from engagement-like signals. Shared lanes
 must choose a signal-led, event-led, job-post-led, or proof-led motion from the
 current brief and row evidence instead of inheriting a preset first-message
 template.
-Post-engager first messages should thank the prospect for the support on the
-sender-owned post and then stop. Do not add a relevance question, CTA, product
-line, meeting ask, or extra paragraph after the thank-you opener unless the
-operator explicitly asks for a longer first message. Prefer the gold shape
-`Thanks for the support on my post about {{post_topic_line}}` over
-surveillance-flavored wording like `saw you pop up`, unless the sender explicitly
-asks for that older wording.
+Post-engager first messages should follow the CXConnect warm shape: acknowledge
+the sender-owned post engagement, include the engaged post URL after a `This one`
+line when row/source data has it, add a plain buyer-function/category check, and
+ask one custom closed question. The question must be specific to the post topic,
+buyer function, company context, and current offer category; do not reuse one
+generic feature-stack question across every row. Product/category wording should
+be immediately legible, such as `LinkedIn outbound`, `customer success`, `CX
+operations`, `support`, `sales`, `growth`, or `post-sales`, not internal
+workflow/mechanism language like `manual research + follow-up process`, `lead
+filters`, or `sequence setup`. Do not add a meeting ask, product pitch, proof
+block, or extra paragraph after the custom closed question unless the operator
+explicitly asks for a longer first message.
 Short form: use the CXConnect Post-Engager Warm Reply-Rate Pattern only when the source is sender-owned Post Engagers.
 Short form: Never use that warm post-engager pattern for Shared Signal Discovery or Shared Cold Fallback.
-Short form: Post-engager warm first messages stop after the thank-you line.
-Short form: Do not add `curious`, `open to`, `trying to`, product copy, or a CTA after the post-engager thank-you line.
+Short form: Post-engager warm first messages use `This one` plus the post URL when available.
+Short form: Post-engager warm first messages need a row-custom closed question.
+Short form: Use plain category words, not feature-stack wording.
+Short form: Do not add `open to`, `worth seeing`, product copy, proof blocks, or a meeting CTA after the custom closed question.
 
 ### Shared Cold Fallback quality bar