@sellable/mcp 0.1.211 → 0.1.212

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

@@ -70,15 +70,17 @@ required message reference cannot be loaded through the MCP asset loader, return
 6. Combine the strongest opener, product line, mechanism line, proof treatment,
    and CTA into one reusable template.
 7. Define token fill rules and fallbacks, then render one good sample.
-8. Before returning, load the validation prompt:
+8. Before returning, load the validation prompt and any validation assets it
+   requires:
 
    `get_subskill_prompt({ subskillName: "create-campaign-v2-validation" })`
 
    Use it only as a validation contract for the candidate message in this live
-   campaign branch. Do not write dry-mode artifacts. Run the final candidate
-   against token safety, proof safety, source safety, Thomas filters, AI tells,
-   single-send rule, and "would I take this call?". If it fails, revise once and
-   validate again.
+   campaign branch. If the validation prompt references packaged assets, load
+   them through `get_subskill_asset` before judging the draft. Do not write
+   dry-mode artifacts. Run the final candidate against token safety, proof
+   safety, source safety, Thomas filters, AI tells, single-send rule, and
+   "would I take this call?". If it fails, revise once and validate again.
 9. Keep the work provisional until the user chooses `Use Template` in Messages.
 
 ## Owned Output

package/package.json

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

package/skills/create-campaign/SKILL.md

@@ -285,9 +285,11 @@ rule, and 3-5 sample workflow-table rows with `rowId`, name, title, company, and
 signal. Optional: campaign name, `selectedLeadListId`, and filter choice. Do not
 paste copied row counts, brief hashes, review-batch hashes, full row ID lists,
 broad row data, or local debug artifacts into the spawn prompt. Message Drafting
-must load the current campaign brief/context, full `generate-messages` prompt,
-all referenced assets, and `create-campaign-v2-validation`; validation is an
-internal gate before it returns the concise review-ready recommendation.
+must load the current campaign brief/context, the full `generate-messages`
+prompt, every message asset referenced by that prompt, and
+`create-campaign-v2-validation` plus any validation assets it references.
+Validation is an internal gate before it returns the concise review-ready
+recommendation.
 
 Use rendered Markdown for user review surfaces, not fenced code blocks. Keep
 lines short, use indexed section labels and bullets, and translate internal
@@ -761,7 +763,8 @@ updates.
    prompt, every referenced message asset through
    `mcp__sellable__get_subskill_asset`, and before returning
    `mcp__sellable__get_subskill_prompt({ subskillName: "create-campaign-v2-validation" })`
-   as the internal validation gate.
+   plus any validation assets it references through
+   `mcp__sellable__get_subskill_asset` as the internal validation gate.
    In Codex, YOLO/autonomous mode counts as campaign-scoped permission to use
    this single Message Drafting background agent. If the user has not enabled
    YOLO and has not explicitly asked for background agents, subagents, parallel
@@ -782,9 +785,10 @@ updates.
    synthesize local validation artifacts from general knowledge. The handoff to
    Message Drafting should pass lean basis only, not hashes, counts, or a long
    row-id list; the branch loads current brief/context, the full
-   `generate-messages` prompt, all referenced assets, and
-   `create-campaign-v2-validation` itself. Do not render fallback sample,
-   concerns, or a QA receipt on the normal happy path.
+   `generate-messages` prompt, all referenced message assets,
+   `create-campaign-v2-validation`, and any validation assets it references. Do
+   not render fallback sample, concerns, or a QA receipt on the normal happy
+   path.
 6. Create the campaign shell early with the v1 brief so the user can open the
    watch link and see useful setup state immediately. Materialize the approved
    source list, copy confirmed rows into the campaign, and internally process the