@sellable/mcp 0.1.91 → 0.1.92

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

@@ -20,11 +20,11 @@ Required first steps:
 1. Read the three required inputs.
 2. Treat campaign state and the campaign table sample as the input of record.
    Disk files are context/debug aids, not durable state.
-3. Use the embedded Message Review Fast Path below. Do not load the full
-   long-form `generate-messages` subskill in the normal path. Load it only when
-   the fast path is missing a needed campaign-specific rule, the user explicitly
-   asks for deep calibration, or the first fast-path draft fails quality gates
-   and no local reference explains how to repair it.
+3. Use the embedded Message Review Safety Gate below. Do not load the full
+   long-form `generate-messages` subskill in this `create-campaign-v2` path. If
+   a needed rule is missing or the draft fails quality gates, return
+   `revise-messaging` with the exact failure instead of pulling the long prompt
+   into this worker.
 
 Owned outputs:
 
@@ -46,8 +46,8 @@ Do not write or modify:
 
 Process:
 
-1. Run the embedded fast-path workflow in dry mode from the approved brief,
-   lead-review source decision, and `lead-sample.json`.
+1. Run the embedded message-review safety-gate workflow in dry mode from the
+   approved brief, lead-review source decision, and `lead-sample.json`.
 2. Use `lead-sample.json` as the only lead sample source. Do not fetch new
    prospects or invent richer row signals.
 3. Build proof inventory, token fill rules, token adherence, angle drafts,
@@ -69,7 +69,8 @@ Process:
 Return a concise final status with:
 
 - artifacts written
-- whether embedded fast-path rules were used or the full fallback was needed
+- whether the embedded message-review safety-gate rules passed or returned
+  `revise-messaging`
 - lead sample basis used
 - proposed template and one sample message
 - selected winner summary
@@ -78,12 +79,12 @@ Return a concise final status with:
 Quality bar:
 
 - Do not synthesize a lightweight message from general knowledge. The artifact
-  must prove the embedded fast-path workflow ran.
+  must prove the embedded message-review safety-gate workflow ran.
 - 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.
 
-## Embedded Message Review Fast Path
+## Embedded Message Review Safety Gate
 
 Use this campaign-launch subset to produce a truthful first-send message,
 rendered token examples, and a decision without loading the full long-form

package/dist/tools/campaigns.js

@@ -26,6 +26,17 @@ function buildWatchUrl(config, redirect) {
         : "";
     return `${config.apiUrl}/auth/continue?token=${config.token}&redirect=${redirect}${workspaceParam}`;
 }
+function isLinkedInProfileUrl(input) {
+    try {
+        const url = new URL(input);
+        const host = url.hostname.toLowerCase();
+        return ((host === "linkedin.com" || host.endsWith(".linkedin.com")) &&
+            /^\/in\/[^/]+\/?$/i.test(url.pathname));
+    }
+    catch {
+        return false;
+    }
+}
 export const campaignToolDefinitions = [
     {
         name: "get_campaigns",
@@ -613,9 +624,10 @@ export async function createCampaign(input) {
     if (!hasClientProspectId && !senderLinkedinUrl) {
         missing.push("clientProspectId or senderLinkedinUrl");
     }
-    // Cheap URL sanity check on senderLinkedinUrl when supplied.
-    if (senderLinkedinUrl && !senderLinkedinUrl.includes("linkedin.com")) {
-        throw new Error("VALIDATION_ERROR: senderLinkedinUrl must be a LinkedIn URL (must contain 'linkedin.com'). Got: " +
+    // Cheap URL sanity check on senderLinkedinUrl when supplied. This input is a
+    // profile bootstrap fallback; company pages should use clientProspectId.
+    if (senderLinkedinUrl && !isLinkedInProfileUrl(senderLinkedinUrl)) {
+        throw new Error("VALIDATION_ERROR: senderLinkedinUrl must be a LinkedIn profile URL like https://www.linkedin.com/in/name/. Company pages require clientProspectId or a discovered profile URL. Got: " +
             senderLinkedinUrl);
     }
     if (missing.length > 0) {

package/dist/tools/flow-preflight.js

@@ -16,6 +16,14 @@ export function markResearchPromptLoaded(mode = "generic", subskillName) {
             : mode === "prospect"
                 ? "research-prospect"
                 : "research");
+    const existing = researchPromptStates[mode];
+    // Re-loading the same research prompt is a context-management detail, not
+    // new research. Preserve the original load timestamp so a completed research
+    // marker does not become stale just because the host refreshed instructions.
+    if (existing?.subskillName === normalizedSubskillName) {
+        latestResearchPromptState = existing;
+        return existing;
+    }
     const state = {
         loadedAt: new Date().toISOString(),
         mode,

package/dist/tools/prompts.js

@@ -289,7 +289,7 @@ export function getPostFindLeadsScoutRegistry() {
         usage: {
             codex: "After the user approves or auto-confirms the lead source, spawn both returned scout `name` values in one assistant turn only when the current Codex host exposes those custom agents.",
             claude: "After lead source approval, invoke both returned Task/Agent subagents in one assistant message only when the current Claude session lists those agents, so filter-leads and message generation run concurrently.",
-            parentThreadRule: "Named agents are optional acceleration. If they are absent, do not customer-surface install status; the main thread still orchestrates filter and message branches from brief.md, lead-review.md, and lead-sample.json. The message branch should use the baked-in message-scout prompt or the create-campaign-v2 message-review fast-path asset, not the full long generate-messages prompt in the normal path. Join before message review.",
+            parentThreadRule: "Named agents are optional acceleration. If they are absent, do not customer-surface install status; the main thread still orchestrates filter and message branches from brief.md, lead-review.md, and lead-sample.json. The message branch should use the baked-in message-scout prompt or the create-campaign-v2 message-review safety gate asset, not the full long generate-messages prompt in the normal path. Join before message review.",
         },
     };
 }

package/package.json

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

package/skills/create-campaign/SKILL.md

@@ -490,14 +490,17 @@ updates.
 4. For message generation, use the `post-find-leads-message-scout` agent when
    available; its prompt carries the campaign-launch message rules. In the
    parent-thread fallback, load
-   `mcp__sellable__get_subskill_asset({ subskillName: "create-campaign-v2", assetPath: "references/message-review-fast-path.md" })`.
+   `mcp__sellable__get_subskill_asset({ subskillName: "create-campaign-v2", assetPath: "references/message-review-safety-gate.md" })`.
+   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.
    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
    watch link and see useful setup state immediately. Import only the first
    bounded review batch after the source is attached to the campaign; do not
    queue workflow cells, attach a sequence, or start until
-   `message-validation.md` proves the fast-path message workflow ran,
+   `message-validation.md` proves the message-review safety-gate workflow ran,
    `message-review.md` approves the template, rubrics are saved, and the
    approved message set is synced into the campaign brief.
 6. Keep `selectedLeadListId` as the source list and `workflowTableId` as the

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

@@ -189,7 +189,10 @@ Validated draft directory:
   it as the preferred `create_campaign` identity input. If it includes a
   LinkedIn profile URL, keep that URL as `senderLinkedinUrl` so the backend can
   resolve/materialize the sender prospect when the watchable campaign shell is
-  created. Do not require a connected sender before shell creation.
+  created. Do not pass a LinkedIn company page as `senderLinkedinUrl`; for a
+  company-only identity, use `clientProspectId` if already materialized or do
+  one lightweight lookup to find the relevant founder/operator profile. Do not
+  require a connected sender before shell creation.
 - If the user supplied a LinkedIn profile, website, domain, company name, or
   explicit client prospect identity in the invocation, do one lightweight lookup
   first:
@@ -217,7 +220,8 @@ Validated draft directory:
   profile, call `fetch_linkedin_profile` and infer the current or most recent
   company from the profile. For a company website, call `fetch_company` when
   possible, otherwise one web lookup. If a LinkedIn profile URL is available,
-  retain it as `senderLinkedinUrl` for `create_campaign`; if a
+  retain it as `senderLinkedinUrl` for `create_campaign`; if only a LinkedIn
+  company page is available, do not pass it as `senderLinkedinUrl`. If a
   `clientProspectId` is available, pass that instead.
 
   After the user confirms the campaign identity, check whether the company
@@ -424,6 +428,10 @@ message we should test.`
 - `brief.md` is the single user-facing debug copy of the brief. The
   `CampaignOffer.campaignBrief` field is the stable downstream thesis source.
 - `lead-review.md` and `lead-sample.json` are the required outputs of `find leads`.
+  `lead-review.md` is customer-readable: describe source paths as provider
+  lanes checked (Signals, Sales Nav, Prospeo) and never include custom agent
+  names, host availability, install state, allowed-tool state, or fallback
+  implementation details.
 - `lead-filter.md` is the primary output of `filter leads`.
 - `rubric.json` is optional and secondary to `lead-filter.md`.
 - `message-prep.md` is an optional speed artifact produced by the explicit
@@ -1058,21 +1066,22 @@ Do not:
 Step 3 is orchestrated by the main thread and executed either by the
 `post-find-leads-message-scout` worker or by the parent-thread fallback. The
 worker carries the campaign-launch message rules in its agent prompt. The
-parent-thread fallback must load the small fast-path reference before writing
+parent-thread fallback must load the small safety-gate reference before writing
 message artifacts:
 
 ```
-mcp__sellable__get_subskill_asset({ subskillName: "create-campaign-v2", assetPath: "references/message-review-fast-path.md" })
+mcp__sellable__get_subskill_asset({ subskillName: "create-campaign-v2", assetPath: "references/message-review-safety-gate.md" })
 ```
 
-Do not force the main thread to load the full long-form `generate-messages`
-subskill in the normal path. Load the full `generate-messages` subskill only
-when the fast path is missing a needed campaign-specific rule, the user
-explicitly asks for deep calibration, or the first fast-path draft fails quality
-gates and no local reference explains how to repair it.
+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.
 
 Do NOT proceed to Step 4 (message review gate) unless `message-validation.md`
-contains the fast-path required sections, a raw sendable Selected Winner, and an
+contains the safety-gate required sections, a raw sendable Selected Winner, and an
 explicit single-first-send PASS. If `message-validation.md` contains post-accept
 DM, follow-up, second-touch, cadence, branch, or other sequence-shaped copy, do
 not summarize it as ready; route back to message-generation and require a

package/skills/create-campaign-v2/core/flow.v2.json

@@ -947,7 +947,7 @@
               "ownership": "proof inventory, token strategy, angle drafting, skeptical-prospect review, and selected winner only"
             }
           ],
-          "earlyMessageStartRule": "After auto-execute-leads confirms the 10-row review batch and workflowTableId is ready, launch message-generation from brief.md, lead-review.md, lead-sample.json, and the imported campaign table sample. The message worker carries the campaign-launch message rules in its agent prompt; parent-thread fallback loads references/message-review-fast-path.md. Legacy/resume preview prep still requires at least 5 probable good-fit rows. It may run beside filter-leads, but the cascade cannot queue until save_rubrics and update_campaign_brief both succeed.",
+          "earlyMessageStartRule": "After auto-execute-leads confirms the 10-row review batch and workflowTableId is ready, launch message-generation from brief.md, lead-review.md, lead-sample.json, and the imported campaign table sample. The message worker carries the campaign-launch message rules in its agent prompt; parent-thread fallback loads references/message-review-safety-gate.md. Legacy/resume preview prep still requires at least 5 probable good-fit rows. It may run beside filter-leads, but the cascade cannot queue until save_rubrics and update_campaign_brief both succeed.",
           "finalMessageReconcileRule": "message-validation.md may start before lead-filter.md exists, but before message-review it must cite only imported review-batch rows that still pass lead-filter.md. If the selected winner depends on a row later excluded by lead-filter.md, revise message-generation before message review.",
           "claudeRule": "In Claude Code, launch both returned post-find-leads scouts with Task/Agent subagents in the same assistant message only when the current session lists those agent names. Do not run filter first and then message generation unless subagents/background work are unavailable.",
           "codexRule": "In Codex, launch both returned post-find-leads scout names as disjoint subagents in the same assistant turn only when the host exposes those custom agents for this run. If the host cannot spawn them, run the same branches sequentially and say so.",
@@ -1014,7 +1014,7 @@
         "The post-lead workstreams are disjoint: filter-leads owns lead-filter.md/rubric.json; message-generation owns message-validation.md/message-prep.md/message-candidate-drafts.md.",
         "message-generation can start before lead-filter.md, but message-review cannot start until both lead-filter.md and message-validation.md exist and reconcile against the same lead-sample.json.",
         "Do not let filter-leads create a new message sample. Do not let message-generation fetch new prospects.",
-        "Before writing message-validation.md, message-generation must either run in the post-find-leads-message-scout agent that carries the campaign-launch message rules in its prompt or load get_subskill_asset({ subskillName: \"create-campaign-v2\", assetPath: \"references/message-review-fast-path.md\" }) in the parent-thread fallback. Do not load the full long generate-messages prompt in the normal path.",
+        "Before writing message-validation.md, message-generation must either run in the post-find-leads-message-scout agent that carries the campaign-launch message rules in its prompt or load get_subskill_asset({ subskillName: \"create-campaign-v2\", assetPath: \"references/message-review-safety-gate.md\" }) in the parent-thread fallback. Do not load the full long generate-messages prompt in create-campaign-v2; if the safety gate cannot safely approve the draft, route to revise-messaging with the concrete failure.",
         "Do not queue, enrich, attach sequence, or start until save_rubrics succeeds and the approved message set is synced into campaignBrief."
       ],
       "doNotAllow": [
@@ -1181,11 +1181,11 @@
       "onEnter": [
         {
           "action": "run_or_reconcile_subskill",
-          "target": "message-review-fast-path",
+          "target": "message-review-safety-gate",
           "mode": "DRY MODE",
           "sampleSource": "lead-sample.json from find-leads",
           "toolCallRequiredBeforeArtifacts": [
-            "get_subskill_asset({ subskillName: \"create-campaign-v2\", assetPath: \"references/message-review-fast-path.md\" }) unless the post-find-leads-message-scout agent prompt already supplied these rules"
+            "get_subskill_asset({ subskillName: \"create-campaign-v2\", assetPath: \"references/message-review-safety-gate.md\" }) unless the post-find-leads-message-scout agent prompt already supplied these rules"
           ],
           "skipIfFreshArtifactExists": "message-validation.md",
           "reconcileWith": "lead-filter.md; lead-sample.json remains the sample source"
@@ -1204,18 +1204,17 @@
         "message-validation.md"
       ],
       "allowedTools": [
-        "get_subskill_prompt",
         "get_subskill_asset",
         "AskUserQuestion",
         "request_user_input"
       ],
       "toolRules": [
-        "Before writing message-validation.md, message-review.md, or a message-review AskUserQuestion, the current run must either execute inside the post-find-leads-message-scout agent that carries the campaign-launch message rules in its prompt or load get_subskill_asset({ subskillName: \"create-campaign-v2\", assetPath: \"references/message-review-fast-path.md\" }) in the parent-thread fallback.",
+        "Before writing message-validation.md, message-review.md, or a message-review AskUserQuestion, the current run must either execute inside the post-find-leads-message-scout agent that carries the campaign-launch message rules in its prompt or load get_subskill_asset({ subskillName: \"create-campaign-v2\", assetPath: \"references/message-review-safety-gate.md\" }) in the parent-thread fallback.",
         "Lead Sample Basis must cite rows from lead-sample.json produced by find-leads. lead-filter.md only gates those rows; it is not a source for a new sample.",
         "Do not hand-write message-validation.md from message-prep.md, message-candidate-drafts.md, or general campaign knowledge.",
-        "message-validation.md must prove the fast-path workflow ran: Gold Standard Strategy Map, Campaign Element Pool, Current Campaign Translation, Token Fill Rules, Token Adherence Table, Angle Drafts, Kill / Combine Review, Finalizer Pass, Gold-Standard Quality Gate, Skeptical Prospect Review, Winner Gate, and a raw sendable Selected Winner are required before message-review can recommend approve-message.",
-        "If the Codex-hosted output is plausible but weaker than the loaded gold-standard examples, stop at message-review with revise-messaging. Do not continue to approval or mint just because the mechanical flow worked.",
-        "Load the full generate-messages subskill only when the fast path is missing a needed campaign-specific rule, the user explicitly asks for deep calibration, or the first fast-path draft fails quality gates and no local reference explains how to repair it.",
+        "message-validation.md must prove the message-review safety-gate workflow ran: Gold Standard Strategy Map, Campaign Element Pool, Current Campaign Translation, Token Fill Rules, Token Adherence Table, Angle Drafts, Kill / Combine Review, Finalizer Pass, Gold-Standard Quality Gate, Skeptical Prospect Review, Winner Gate, and a raw sendable Selected Winner are required before message-review can recommend approve-message.",
+        "If the hosted output is plausible but weaker than the safety-gate gold-standard rules, stop at message-review with revise-messaging. Do not continue to approval or mint just because the mechanical flow worked.",
+        "Do not load the full generate-messages subskill in create-campaign-v2. If the safety gate is missing a needed campaign-specific rule or the first safety-gate draft fails quality gates, route to revise-messaging with the concrete failure instead of loading the long prompt.",
         "The approved message set must be written back into campaignBrief before validate-sample queues the review-batch cascade."
       ],
       "doNotAllow": [

package/skills/create-campaign-v2/references/approval-gate-framing.md

@@ -32,12 +32,14 @@ Before showing the commit gate, the draft directory must contain all of:
 - `message-validation.md`
 - `approval-packet.md`
 
-The current run must also have retrieved the real message-generation prompt
-through `get_message_prompt({ promptName: "generate-messages" })` or
-`get_subskill_prompt({ subskillName: "generate-messages" })` before
-`message-validation.md`, `approval-packet.md`, or the commit gate is written.
-If the message template was written directly from memory or planning artifacts,
-do not show the commit gate; route back to message generation.
+The current run must also have retrieved message-generation rules before
+`message-validation.md`, `approval-packet.md`, or the commit gate is written. In
+`create-campaign-v2`, use the compact
+`references/message-review-safety-gate.md` asset or the embedded
+`post-find-leads-message-scout` prompt. Do not load the full long-form
+`generate-messages` subskill for the hosted campaign launch path. If the message
+template was written directly from memory or planning artifacts, do not show the
+commit gate; route back to message generation.
 
 `rubric.json` is optional but strongly preferred — when missing, derive it from
 `lead-filter.md` in the atomic mint step.

package/skills/create-campaign-v2/references/{message-review-fast-path.md → message-review-safety-gate.md}

@@ -1,14 +1,19 @@
-# Message Review Fast Path
+# Message Review Safety Gate
 
-Use this reference for `create-campaign-v2` message review. It is the
-campaign-launch subset of `generate-messages`: enough to produce a truthful
-first-send message, rendered token examples, and an approval decision without
-loading the full long-form message-generation prompt into Claude/Codex.
+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.
 
-Load the full `generate-messages` subskill only when the fast path is missing a
-needed campaign-specific rule, the user explicitly asks for deep calibration, or
-the first fast-path draft fails quality gates and no local reference explains
-how to repair it.
+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.
 
 ## Required Workflow