@sellable/mcp 0.1.102 → 0.1.103

package/dist/tools/prompts.js

@@ -319,7 +319,8 @@ export function listSubskillPrompts(limit, includePublic, includeInternal) {
     };
 }
 function markSubskillPromptLoaded(subskillName) {
-    if (subskillName === "create-campaign" || subskillName === "create-campaign-v2") {
+    if (subskillName === "create-campaign" ||
+        subskillName === "create-campaign-v2") {
         markCreateCampaignPromptLoaded();
     }
     if (subskillName === "research") {

package/package.json

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

package/skills/create-campaign-v2/references/final-handoff-contract.md

@@ -42,17 +42,17 @@ order (all before waiting for the user):
    connected sender to attach. Attach only the chosen sender. In explicit UAT
    safe mode, auto-select only the safe mock sender; never select a real sender.
 7. Call `update_campaign({ campaignId, senderIds: [selectedSenderId],
-   currentStep: "sequence" })` to attach the sender via the v3 senders route and
+currentStep: "sequence" })` to attach the sender via the v3 senders route and
    move the watch link to Sequence.
 8. Call `attach_recommended_sequence({ campaignId, currentStep: "send" })` to
    bind the tier-aware recommended sequence. If that response does not persist
    `currentStep: "send"`, call `update_campaign({ campaignId, currentStep:
-   "send" })`.
+"send" })`.
 9. Re-surface the `watchUrl` using the exact block in
    `references/watch-link-handoff.md`.
 10. Surface the `handoff.orientation` string from `auto-execute.yaml`
-   alongside the watch link so the user sees both the link and the
-   "what to do next" sentence.
+    alongside the watch link so the user sees both the link and the
+    "what to do next" sentence.
 11. Ask the final launch greenlight with the structured question function:
     Start campaign, Review campaign first, or Pause here.
 12. STOP unless the user explicitly chooses Start campaign. Do not call
@@ -117,7 +117,7 @@ order, atomically:
 2. **Validate sender + sequence state.** If no sender is attached, refuse start
    and return the Settings link. If no sequence is attached but a sender is
    attached, call `attach_recommended_sequence({ campaignId, currentStep:
-   "send" })` before approving messages.
+"send" })` before approving messages.
 3. **Bulk-approve queued messages** via the existing endpoint
    `POST /api/v3/workflow-tables/cells/approve-batch` with
    `{ tableId }`.

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

@@ -313,6 +313,13 @@ awaiting-user-greenlight, or start-campaign. It must hand off as
 `sample_revision_required` with the observed counts so the user can decide
 whether the source or filter should change.
 
+If the same source lane has already failed after a revision, do not present
+another same-source revision as the recommended/default next action. Recommend
+the strongest fallback lane first (for example, Sales Nav after repeated
+Signals underfloor results), then offer revise-filter only if the imported rows
+look close to ICP but the rubric is too strict. This prevents customer-visible
+loops where the agent keeps asking to retry the same weak source.
+
 When the sample passes the projected-pass floor, call
 `update_campaign({ campaignId, currentStep: "auto-execute-messaging" })`
 and orient the user that messaging will complete for the review batch only.
@@ -435,7 +442,7 @@ Shape:
    sender to attach. Attach only after the user chooses. In explicit UAT safe
    mode, use only the safe mock sender; never pick a real sender.
 7. Call `update_campaign({ campaignId, senderIds: [selectedSenderId],
-   currentStep: "sequence" })` to attach the sender through the v3 senders
+currentStep: "sequence" })` to attach the sender through the v3 senders
    route and orient the watch link to Sequence.
 8. Call `attach_recommended_sequence({ campaignId, currentStep: "send" })`
    (bind the tier-recommended sequence to the campaign). If the tool response
@@ -443,15 +450,15 @@ Shape:
    `update_campaign({ campaignId, currentStep: "send" })`.
 9. Re-surface the `watchUrl` using `references/watch-link-handoff.md`.
 10. Surface the `handoff.orientation` string from `auto-execute.yaml`
-   alongside the link.
+    alongside the link.
 11. Ask the final launch greenlight with the structured question function:
-   Start campaign, Review campaign first, or Pause here.
+    Start campaign, Review campaign first, or Pause here.
 12. STOP unless the user explicitly chooses Start campaign. Do NOT call
-   `start_campaign` from Step 16 itself; that belongs only to the Claude
-   greenlight path. The autonomous tail ends here.
+    `start_campaign` from Step 16 itself; that belongs only to the Claude
+    greenlight path. The autonomous tail ends here.
 13. Make the credit boundary explicit in the handoff: only the first review
-   batch has been enriched/messaged; expanding to more leads requires a
-   separate user instruction.
+    batch has been enriched/messaged; expanding to more leads requires a
+    separate user instruction.
 
 Two equally valid greenlight channels take Step 16 into a running
 campaign: