@sellable/mcp 0.1.217 → 0.1.218

package/package.json

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

package/skills/create-campaign-v2/references/sellable-cleanup-rules.md

@@ -88,6 +88,7 @@ Revise or reject the sample when any of these happen.
 - **PS carries a second proof beat that doesn't answer a different objection** — the second beat must open a dimension beat #1 didn't address (e.g. technical reliability when beat #1 was operator empathy; named backing when beat #1 was founder track record). Default PS is ONE beat
 - **PS has no concrete job** — every PS must lower commitment, preview what the buyer will see, answer a trust/category objection, or tie proof to buyer value. If you cannot name the job and the direct answer, omit the PS. The PS is optional: do not keep one just because proof is true or available.
 - **PS adds friction or seller category anxiety** — if the PS sounds like it is defending against an internal category worry, uses language the buyer would not naturally say, or makes the buyer infer why it matters, cut the weak clause or remove the whole PS.
+- **PS is not concrete and falsifiable** — generic nouns like `workflow`, `process`, `system`, `platform`, or `message draft` do not count unless the same sentence names buyer-visible steps, a specific next-step preview, a concrete artifact, or an outcome the buyer can immediately verify. Use the older Sellable outbound standard: proof is concrete or omitted.
 - **PS or final line fails the explain-back test** — reject any final line that needs an after-the-fact explanation to make sense. Contrast-only lines (`not just...`, `more than...`, `beyond...`) pass only when the same sentence names the concrete workflow, next step, or buyer outcome. Otherwise the reader has to infer the value, so cut or rewrite it.
 - **apologetic source-thread PS** — reject `p.s. if the source thread was just casual reading, ignore me`, `only reaching out where the role and topic looked close`, or any PS that defends why the recipient was sourced. If the source is too weak, omit the personalization line. A relevance-risk PS such as `p.s. if this is not relevant to your outbound workflow, ignore me` is allowed because it lowers pressure without narrating the source.
 - **subject line uses the same banned glue jargon as the body** — any B2B compound noun the buyer wouldn't say naturally in conversation. Subject follows the same jargon rules as the body

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

@@ -253,6 +253,11 @@ Orchestration requirements:
   available. If it adds friction, sounds like internal category anxiety, or uses
   language the buyer would not naturally say, cut the weak clause or remove the
   whole PS.
+- require concrete and falsifiable final-line value. Generic nouns like
+  `workflow`, `process`, `system`, `platform`, or `message draft` do not count
+  unless the same sentence names buyer-visible steps, a specific next-step
+  preview, a concrete artifact, or an outcome the buyer can immediately verify.
+  Use the older Sellable outbound standard: proof is concrete or omitted.
 - pass the PS explain-back gate. If a PS needs an after-the-fact explanation to
   make sense, reject it. Contrast-only lines (`not just...`, `more than...`,
   `beyond...`) pass only when the same sentence names the concrete workflow,

package/skills/generate-messages/SKILL.md

@@ -1228,6 +1228,16 @@ The PS is optional. Do not preserve a PS just because the proof is true or
 available. If the PS adds friction, sounds like internal category anxiety, or
 uses language the buyer would not naturally say, cut the confusing clause or
 remove the whole PS.
+Generic nouns do not satisfy the concrete-job gate. Lines like `built around the
+workflow`, `more than a message draft`, `covers the whole process`, or `full
+system` still fail unless the same sentence is concrete and falsifiable: it
+names buyer-visible steps, a specific next-step preview, a concrete artifact,
+or an outcome the buyer can immediately verify. When the best rewrite is still
+abstract, cut the PS.
+Use the same standard as the older Sellable outbound configs: proof is concrete
+or omitted. Good proof has a real name, number, timeframe, artifact, or visible
+mechanism. Bad proof is vague/unfalsifiable like `helps teams communicate better`
+or `built around the workflow`.
 
 If YC, notable backing, funding, or named investor proof is present AND
 the buyer is in healthcare, financial services, security, enterprise, or