@sellable/mcp 0.1.181 → 0.1.182

package/package.json

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

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

@@ -23,12 +23,14 @@ validate-sample tool:
 get_subskill_prompt({ subskillName: "create-campaign-v2-tail" })
 ```
 
-CampaignOffer state and the watch link are canonical. Resume/gating reads
-state: `campaignId`, `watchUrl`, `campaignBrief`,
-`currentStep`, source/search association, `selectedLeadListId`,
-`workflowTableId`, `leadScoringRubrics`, `approvedMessageTemplate`,
-`senderIds`, `sequenceTemplate`, and running state. Local draft files are debug
-only; do not create, link, or surface them in normal runs.
+CampaignOffer state and the watch link are canonical. CampaignOffer state is
+canonical for resume, gating, and handoff. Resume, gating, and handoff read campaign state first:
+`campaignId`, `watchUrl`, `campaignBrief`, `currentStep`, source/search
+association, `selectedLeadListId`, `workflowTableId`, `leadScoringRubrics`,
+`approvedMessageTemplate`, `senderIds`, `sequenceTemplate`, and running state.
+Local draft files are debug; do not create, link, or surface them in
+normal runs. These files are debug outputs; resume and gating read campaign
+state first.
 
 ## Normal Flow
 
@@ -64,13 +66,12 @@ First visible request when no identity is known:
 What is your LinkedIn profile URL or handle?
 ```
 
-Require a LinkedIn profile URL or public profile handle before setup continues.
-If the user provides a bare handle like `csreyes92` or a `/in/...` path,
-normalize it to `https://www.linkedin.com/in/{handle}/`. If the user provides
-anything else, ask again for the person's LinkedIn profile URL or handle. Retain
-the normalized URL as `senderLinkedinUrl` or resolve `clientProspectId` for
-`create_campaign`. Run one lightweight profile/company lookup before strategy
-questions, then say public research may be stale and invite corrections.
+Require a LinkedIn profile URL or handle before setup continues. Normalize
+`csreyes92`, `@csreyes92`, or `/in/csreyes92` to
+`https://www.linkedin.com/in/{handle}/`; otherwise ask again. Retain it as
+`senderLinkedinUrl` or resolve `clientProspectId` for `create_campaign`. Run one
+lightweight profile lookup before strategy questions, then invite
+corrections.
 
 Restore the full setup intake before the brief. Ask bounded choices for:
 
@@ -170,9 +171,12 @@ copy.
 ## Lead Source
 
 Default source order when source is unspecified: LinkedIn post engagement,
-Sales Nav recent activity, broader Sales Nav title search, then Prospeo. If
-the campaign is hiring-led or needs hiring-by-role signals, start with Prospeo;
-Sales Nav is only an activity/referral fallback for those campaigns.
+Sales Nav recent activity, broader Sales Nav title search, then Prospeo. Use that order only
+when the campaign is not hiring-led and does not need hiring-by-role signals.
+If the campaign is hiring-led or needs hiring-by-role signals, start with
+Prospeo because `search_prospeo` supports
+`company_job_posting_hiring_for` and `company_job_posting_quantity`; Sales Nav
+is only an activity/referral fallback because it does not provide hiring-by-role filters.
 
 Before any provider prompt/search/scout call, move the watched campaign to
 provider/source selection, then show one `## Find Buyers Plan` gate. The plan