@sellable/mcp 0.1.126 → 0.1.127

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

@@ -80,6 +80,9 @@ Quality bar:
 
 - Do not synthesize a lightweight message from general knowledge. The artifact
   must prove the embedded message-review safety-gate workflow ran.
+- There is no generate-message fast mode in this path. The embedded gate is the
+  same campaign-launch quality contract used by the parent-thread compatibility
+  path, not a lower-quality shortcut.
 - Message generation can start before `lead-filter.md`, but message review
   cannot start until the parent verifies the selected basis rows still pass the
   final filter.
@@ -128,6 +131,13 @@ Quality gates:
   `[insert]`, or `[generated]`.
 - Optional row-specific personalization must be grounded in a row field or
   omitted entirely.
+- 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. Only refer to the prospect's engagement when the line is
+  self-aware and low-certainty, for example `not sure if this is too specific,
+but the [topic] thread felt close enough to send`. Otherwise omit the
+  engagement signal and use role/company/problem context.
 - Subjects should be short, buyer-relevant, and specific. Avoid `quick
 question`, `demo`, `founder call`, sender names, and generic `outbound`.
 - If the message is plausible but not ready to send, set `Recommendation:

package/package.json

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

package/skills/create-campaign/SKILL.md

@@ -561,6 +561,7 @@ updates.
    Do not load the full long-form `generate-messages` subskill in this
    create-campaign path; if the safety gate cannot safely approve the draft,
    route to revise messaging with the concrete failure.
+   This compatibility path is not a generate-message fast mode.
    Do not synthesize `message-validation.md` from the brief, lead review, or
    general knowledge.
 5. Create the campaign shell early with the v1 brief so the user can open the

package/skills/create-campaign-v2/SKILL.md

@@ -1248,11 +1248,12 @@ mcp__sellable__get_subskill_asset({ subskillName: "create-campaign-v2", assetPat
 ```
 
 Do not load the full long-form `generate-messages` subskill in
-`create-campaign-v2`. The safety-gate asset is a parent-thread fallback for hosts
-that cannot launch `post-find-leads-message-scout`, not the preferred route. If
-the safety gate is missing a needed campaign-specific rule or the draft fails
-quality gates, stop at `revise-messaging` with the exact failure instead of
-pulling the long prompt into the main thread.
+`create-campaign-v2`. The safety-gate asset is a parent-thread compatibility
+path for hosts that cannot launch `post-find-leads-message-scout`, not a
+generate-message fast-mode prompt and not the preferred route. If the safety gate
+is missing a needed campaign-specific rule or the draft fails quality gates, stop
+at `revise-messaging` with the exact failure instead of pulling the long prompt
+into the main thread.
 
 Do NOT proceed to Step 4 (message review gate) unless `message-validation.md`
 contains the safety-gate required sections, a raw sendable Selected Winner, and an

package/skills/create-campaign-v2/references/message-review-safety-gate.md

@@ -3,17 +3,17 @@
 Use this reference for `create-campaign-v2` message review only in two cases:
 when these rules are embedded inside the `post-find-leads-message-scout` agent
 prompt, or when the host cannot launch that agent and the parent thread needs a
-compact fallback. It is the campaign-launch subset of `generate-messages`: enough
-to prove a truthful first-send message, rendered token examples, and an approval
-decision without loading the full long-form message-generation prompt into the
-main Claude/Codex thread.
+self-contained safety gate. It is the campaign-launch subset of
+`generate-messages`: enough to prove a truthful first-send message, rendered
+token examples, and an approval decision without loading the full long-form
+message-generation prompt into the main Claude/Codex thread.
 
 In a normal installed Claude/Codex session, the message scout owns these rules.
-The parent-thread asset is a compatibility fallback, not a shortcut. Do not load
-the full `generate-messages` subskill in this flow. If the safety gate is missing
-a needed campaign-specific rule or the draft fails quality gates, stop at
-`revise-messaging` with the exact missing rule/failure instead of pulling the
-long prompt into the main thread.
+The parent-thread asset is a compatibility safety path, not a fast-mode prompt
+or a shortcut. Do not load the full `generate-messages` subskill in this flow. If
+the safety gate is missing a needed campaign-specific rule or the draft fails
+quality gates, stop at `revise-messaging` with the exact missing rule/failure
+instead of pulling the long prompt into the main thread.
 
 ## Required Workflow
 
@@ -71,6 +71,13 @@ the full framework.
   `[insert]`, `[generated]`, or any instruction for a later model to fill.
 - Optional row-specific personalization must be grounded in a row field or
   omitted entirely. Never use generic filler like "your work" or "your team."
+- 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. Only refer to the prospect's engagement when the line is
+  self-aware and low-certainty, for example `not sure if this is too specific,
+but the [topic] thread felt close enough to send`. Otherwise omit the
+  engagement signal and use role/company/problem context.
 - Subject lines should be short, buyer-relevant, and specific. Avoid
   `quick question`, `demo`, `founder call`, sender names, and generic `outbound`.
 - If the message is plausible but not ready to send, set

package/skills/generate-messages/SKILL.md

@@ -1411,6 +1411,13 @@ about`, or `clearly relevant` are BLOCKED. Source-y phrases such as
   context instead: `not sure if this is relevant, but if [topic] is part
 of what you're testing...`, `this may be too specific, but [topic] felt
 close enough to send`, or a similarly natural line.
+- **Engagement reference is opt-in, not the default opener:** do not
+  default to `{{first_name}}, saw you {{engagement_context}} on
+{{post_context}}`, `saw you reacted to...`, or equivalent retrieval-log
+  copy. That reads like surveillance unless the line is self-aware about
+  the weak inference and uses low-certainty language. If that sounds
+  awkward, omit the engagement source and open from role, company, problem,
+  or the approved offer.
 - **No internal-metric flex:** internal process details are not proof by
   default. Compute time, token/cache details, model names, number of
   agents, orchestration internals, or `~5 min of compute per message`
@@ -1764,6 +1771,11 @@ Rules:
   - `"Saw you around [topic]."`
   - `"Saw you engaging with [topic]."`
 - signal-led opener shape is a **special case**, not the default. Use it only when the archived motion truly depends on it and the line can stay natural. Follow Superpower's `"saw you were active around some [topic] stuff recently and figured this might actually be relevant"` shape only when it reads like a real human note rather than a retrieval flex.
+- tokenized engagement-source opener shape is BLOCKED by default:
+  `{{first_name}}, saw you {{engagement_context}} on {{post_context}}` reads
+  like surveillance unless the filled line is explicitly self-aware and
+  low-certainty. Prefer `not sure if this is too specific, but the [topic]
+thread felt close enough to send` or omit the engagement reference entirely.
 - if no per-lead signal exists, a category-level opener is acceptable as a fallback, but the Findings section must flag: `"Category-level opener used because lead-sample.json carries no per-lead signal. Real sends should surface signals in lead-sample.json before using this template."`
 - this pushes the real fix upstream to find-leads, where the sample payload should include signals when they exist