@sellable/mcp 0.1.141 → 0.1.143

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

@@ -17,20 +17,26 @@ instead of pulling the long prompt into the main thread.
 
 ## Required Workflow
 
-1. Read `brief.md`, `lead-review.md`, `lead-sample.json`, and `lead-filter.md`
-   when present.
-2. Pick 2-3 sample rows from `lead-sample.json`, preferring rows that pass the
-   filter or are likely to pass. Do not invent new rows.
-3. Build the message from the approved brief and the sampled rows. Use only
-   proof that appears in the brief, source review, sample, or explicit user
-   answers. Unsupported reply-rate, meeting-rate, ROI, revenue, and customer-logo
-   claims are blocked.
-4. Produce `message-validation.md` with the required sections below.
-5. Produce `message-review.md` as the customer-facing checkpoint.
+1. Read the live campaign basis: campaign id, campaign revision or
+   `campaignUpdatedAt`, campaign brief content, selected source decision,
+   selected lead list/source state, `workflowTableId`, imported review-batch
+   row ids/hash, and any saved rubric/filter summary supplied by the parent.
+2. Pick 2-3 sample rows from the imported review-batch rows, preferring rows
+   that pass the saved rubrics or are likely to pass. Do not invent new rows.
+3. Build the message from the approved campaign brief, selected source context,
+   sampled rows, and explicit user answers. Use only proof that appears in that
+   live basis. Unsupported reply-rate, meeting-rate, ROI, revenue, and
+   customer-logo claims are blocked.
+4. Return a compact message recommendation to the parent thread. Do not write
+   local markdown/json artifacts in normal customer runs; emit debug artifacts
+   only when the parent explicitly asks for debug/UAT output.
+5. Render the customer-facing message review in chat before asking for approval.
+   After approval, the parent persists template and token rules into campaign
+   state with `update_campaign_brief`.
 6. Ask exactly `approve-message` or `revise-messaging`. Do not import, queue,
    attach sequence, or start before `approve-message`.
 
-## Required `message-validation.md` Sections
+## Required Message Recommendation Sections
 
 - `Status`
 - `Mode`
@@ -51,8 +57,8 @@ instead of pulling the long prompt into the main thread.
 - `Findings`
 - `Recommendation`
 
-Keep this artifact concise. It should prove the reasoning path, not reproduce
-the full framework.
+Keep this recommendation concise. It should prove the reasoning path, not
+reproduce the full framework.
 
 ## Message Quality Gates
 
@@ -83,7 +89,7 @@ but the [topic] thread felt close enough to send`. Otherwise omit the
 - If the message is plausible but not ready to send, set
   `Recommendation: revise-messaging`.
 
-## Customer-Facing `message-review.md`
+## Customer-Facing Message Review
 
 Render this in chat before asking:
 

package/skills/create-campaign-v2/references/watch-guide-narration.md

@@ -214,7 +214,9 @@ and do not say filtering the batch before rubrics and message approval are
 saved. Only show worker statuses as running if those branches actually started.
 When the user chooses filters, immediately persist `enableICPFilters: true` and
 move to `create-icp-rubric` so the watched app shows Filter Rules while Codex
-defines the rules in chat.
+defines the rules in chat. After `save_rubrics`, move to `apply-icp-rubric`
+so the watched app shows Filter Leads with saved rules before message approval
+unlocks any enrichment or filtering.
 
 Fit + message:
 

package/skills/find-leads/SKILL.md

@@ -132,9 +132,9 @@ The kickoff doc is the resume surface. Re-open it before repeating discovery wor
 - Before the first provider prompt, search, source scout, or signal-discovery
   call, show the user a compact source plan and get approval. The plan must say
   which campaign-specific options are plausible, which lane you recommend
-  first, why active LinkedIn engagers are or are not likely to exist for this
-  ICP/offer, what fallback lane you will use if the evidence is thin, and that
-  approval authorizes scouting/search only.
+  first, the exact evidence you expect to test for this ICP/offer, what
+  fallback lane you will use if the evidence is thin, and that approval
+  authorizes scouting/search only.
 - When enough context exists, try 1-2 alternate hypotheses if the first lane is too weak or noisy.
 - Directional preview does not require a sender, campaign, or selected lead list. Start with count/sample exploration first; only attach searches to a campaign when the user is ready to import.
 - If the user already has a LinkedIn-profile CSV, treat that as a direct lead-list path and skip discovery.

package/skills/research/config.json

@@ -1,9 +0,0 @@
-{
-  "parallelMode": "wide",
-  "agentCount": 6,
-  "maxToolCallsPerAgent": 2,
-  "senderMaxAgents": 2,
-  "senderMaxToolCallsPerAgent": 3,
-  "progressMode": true,
-  "debugMode": true
-}