@sellable/mcp 0.1.58 → 0.1.60

package/package.json

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

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

@@ -458,6 +458,14 @@ the message from the same sample.` Never say `kicking off two workstreams`,
   approval decision can be inspected later.
 - Before asking for commit approval, persist a customer-facing
   `approval-packet.md` so the exact packet can be inspected later.
+- The pre-mint approval packet must show exactly one concrete `## Sample
+Message` rendered as the recipient would see it, in addition to the approved
+  message template. Do not make the user mentally expand `{{tokens}}` at final
+  approval.
+- Do not include sequence, cadence, sending-window, mailbox, or campaign
+  settings review in the pre-mint approval packet. Those come after mint. The
+  pre-mint packet approves only the brief, lead source, lead filter/rubric, and
+  first message direction.
 - Persist `customer-roleplay.md` when a customer/operator roleplay critique is
   run. This critique can recommend a decision, but it can never authorize mint.
 - Persist `commit-gate-decision.md` with exactly one of the six gate choices.

package/skills/find-leads/SKILL.md

@@ -279,6 +279,9 @@ Use first when LinkedIn activity plus tighter role / company filters matter.
   `CURRENT_TITLE` lookups. Seniority filters are supporting constraints, not a
   substitute for target roles. Example: VP Sales / VP Revenue / Head of Growth
   should use title filters, not only `SENIORITY_LEVEL: Vice President`.
+- When a title lookup returns multiple options, choose the option that most
+  closely matches the intended role, not the first option by position. If
+  `Head of Growth` appears after `Head of Marketing`, use `Head of Growth`.
 - For reply-likelihood-first outbound, Sales Nav is the second choice after Signals: use it when the TAM is not active enough on LinkedIn, when Signals cannot sustain enough good fits, or when the targeting thesis depends on tighter role/company control than Signals can provide.
 - For InMail or LinkedIn-send motions, establish the baseline TAM first, then test a `POSTED_ON_LINKEDIN` slice when the pool can still sustain a campaign.
 - Treat recent posters as a preferred first-send slice, not just a nice-to-have proxy. When the recently-posted slice still yields enough projected good fits, prefer it because reply / acceptance performance is usually materially better than the cold full-TAM pool.

package/skills/providers/sales-nav.md

@@ -57,6 +57,12 @@ Example search name: "Active CXOs at 201-500 companies"
    business development, partnerships, marketing, operations, and other noisy
    roles.
 
+   Do not blindly use the first `lookup_sales_nav_filter` result. Review the
+   returned options and choose the closest semantic title match. If the first
+   result for "Head of Growth" is "Head of Marketing" but a later option is
+   "Head of Growth", use "Head of Growth". If no close title match exists,
+   retry with a tighter title query or omit that role and call out the tradeoff.
+
    Dynamic filters (REQUIRE lookup):
 
    - REGION: "United States", "California", "London"