@sellable/mcp 0.1.322 → 0.1.323

package/dist/tools/prompts.d.ts

@@ -137,7 +137,7 @@ export interface PostFindLeadsScoutRegistryResponse {
 }
 export declare const DEFAULT_SUBSKILL_PROMPT_CHUNK_CHARS = 48000;
 export declare const MAX_SUBSKILL_PROMPT_CHUNK_CHARS = 48000;
-export declare const ALLOWED_SUBSKILL_PROMPT_NAMES: readonly ["building-gtm-tables", "content", "create-ab-test", "create-campaign", "create-campaign-brief", "create-campaign-v2", "create-campaign-v2-tail", "create-campaign-v2-validation", "create-post", "create-rubric", "engage", "enrich-prospects", "fill-send-horizon", "find-leads", "foundation", "generate-messages", "interview", "load-voice", "refresh-sender-engagement", "research", "research-prospect", "research-sender", "weekly-campaign-summary", "workflow-sequences"];
+export declare const ALLOWED_SUBSKILL_PROMPT_NAMES: readonly ["building-gtm-tables", "content", "create-ab-test", "create-campaign", "create-campaign-brief", "create-campaign-v2", "create-campaign-v2-tail", "create-campaign-v2-validation", "create-evergreen-campaigns", "create-post", "create-rubric", "engage", "enrich-prospects", "fill-send-horizon", "find-leads", "foundation", "generate-messages", "interview", "load-voice", "refresh-sender-engagement", "research", "research-prospect", "research-sender", "weekly-campaign-summary", "workflow-sequences"];
 export declare const promptToolDefinitions: ({
     name: string;
     description: string;
@@ -181,7 +181,7 @@ export declare const promptToolDefinitions: ({
         properties: {
             subskillName: {
                 type: string;
-                enum: readonly ["building-gtm-tables", "content", "create-ab-test", "create-campaign", "create-campaign-brief", "create-campaign-v2", "create-campaign-v2-tail", "create-campaign-v2-validation", "create-post", "create-rubric", "engage", "enrich-prospects", "fill-send-horizon", "find-leads", "foundation", "generate-messages", "interview", "load-voice", "refresh-sender-engagement", "research", "research-prospect", "research-sender", "weekly-campaign-summary", "workflow-sequences"];
+                enum: readonly ["building-gtm-tables", "content", "create-ab-test", "create-campaign", "create-campaign-brief", "create-campaign-v2", "create-campaign-v2-tail", "create-campaign-v2-validation", "create-evergreen-campaigns", "create-post", "create-rubric", "engage", "enrich-prospects", "fill-send-horizon", "find-leads", "foundation", "generate-messages", "interview", "load-voice", "refresh-sender-engagement", "research", "research-prospect", "research-sender", "weekly-campaign-summary", "workflow-sequences"];
                 description: string;
             };
             offset: {
@@ -216,7 +216,7 @@ export declare const promptToolDefinitions: ({
         properties: {
             subskillName: {
                 type: string;
-                enum: readonly ["building-gtm-tables", "content", "create-ab-test", "create-campaign", "create-campaign-brief", "create-campaign-v2", "create-campaign-v2-tail", "create-campaign-v2-validation", "create-post", "create-rubric", "engage", "enrich-prospects", "fill-send-horizon", "find-leads", "foundation", "generate-messages", "interview", "load-voice", "refresh-sender-engagement", "research", "research-prospect", "research-sender", "weekly-campaign-summary", "workflow-sequences"];
+                enum: readonly ["building-gtm-tables", "content", "create-ab-test", "create-campaign", "create-campaign-brief", "create-campaign-v2", "create-campaign-v2-tail", "create-campaign-v2-validation", "create-evergreen-campaigns", "create-post", "create-rubric", "engage", "enrich-prospects", "fill-send-horizon", "find-leads", "foundation", "generate-messages", "interview", "load-voice", "refresh-sender-engagement", "research", "research-prospect", "research-sender", "weekly-campaign-summary", "workflow-sequences"];
                 description: string;
             };
             assetPath: {

package/dist/tools/prompts.js

@@ -25,6 +25,7 @@ export const ALLOWED_SUBSKILL_PROMPT_NAMES = [
     "create-campaign-v2",
     "create-campaign-v2-tail",
     "create-campaign-v2-validation",
+    "create-evergreen-campaigns",
     "create-post",
     "create-rubric",
     "engage",

package/dist/tools/registry.d.ts

@@ -236,7 +236,7 @@ export declare const allTools: ({
         properties: {
             subskillName: {
                 type: string;
-                enum: readonly ["building-gtm-tables", "content", "create-ab-test", "create-campaign", "create-campaign-brief", "create-campaign-v2", "create-campaign-v2-tail", "create-campaign-v2-validation", "create-post", "create-rubric", "engage", "enrich-prospects", "fill-send-horizon", "find-leads", "foundation", "generate-messages", "interview", "load-voice", "refresh-sender-engagement", "research", "research-prospect", "research-sender", "weekly-campaign-summary", "workflow-sequences"];
+                enum: readonly ["building-gtm-tables", "content", "create-ab-test", "create-campaign", "create-campaign-brief", "create-campaign-v2", "create-campaign-v2-tail", "create-campaign-v2-validation", "create-evergreen-campaigns", "create-post", "create-rubric", "engage", "enrich-prospects", "fill-send-horizon", "find-leads", "foundation", "generate-messages", "interview", "load-voice", "refresh-sender-engagement", "research", "research-prospect", "research-sender", "weekly-campaign-summary", "workflow-sequences"];
                 description: string;
             };
             offset: {
@@ -271,7 +271,7 @@ export declare const allTools: ({
         properties: {
             subskillName: {
                 type: string;
-                enum: readonly ["building-gtm-tables", "content", "create-ab-test", "create-campaign", "create-campaign-brief", "create-campaign-v2", "create-campaign-v2-tail", "create-campaign-v2-validation", "create-post", "create-rubric", "engage", "enrich-prospects", "fill-send-horizon", "find-leads", "foundation", "generate-messages", "interview", "load-voice", "refresh-sender-engagement", "research", "research-prospect", "research-sender", "weekly-campaign-summary", "workflow-sequences"];
+                enum: readonly ["building-gtm-tables", "content", "create-ab-test", "create-campaign", "create-campaign-brief", "create-campaign-v2", "create-campaign-v2-tail", "create-campaign-v2-validation", "create-evergreen-campaigns", "create-post", "create-rubric", "engage", "enrich-prospects", "fill-send-horizon", "find-leads", "foundation", "generate-messages", "interview", "load-voice", "refresh-sender-engagement", "research", "research-prospect", "research-sender", "weekly-campaign-summary", "workflow-sequences"];
                 description: string;
             };
             assetPath: {

package/package.json

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

package/skills/create-evergreen-campaigns/SKILL.md

@@ -0,0 +1,59 @@
+---
+name: create-evergreen-campaigns
+description: Reconcile a sender team's evergreen campaign structure — create-or-reuse the standing campaigns (per-sender post engagers + shared fallback lanes) idempotently, with sequences attached and prospect-safe message briefs. Never duplicates, never launches. Schedule-automation friendly ("make sure evergreen campaigns exist for these users").
+visibility: internal
+---
+
+# Create Evergreen Campaigns
+
+<role>
+You are a campaign structure reconciler. Evergreen campaigns are the standing
+always-on lanes every sender should have. Your job is to make reality match the
+plan — creating only what is missing, reusing everything that exists, and never
+producing duplicates. Reconcile/create-reuse only; this skill never launches campaigns.
+</role>
+
+<inputs>
+The invoking prompt names the senders ("create evergreen campaigns for csreyes92 and thomas"). Resolve each via `list_senders`.
+
+Default evergreen plan per workspace (override only if the prompt specifies different lanes):
+
+1. **`<Sender Name> - Post Engagers`** — one per sender (warm lane, highest priority)
+2. **`<Workspace/Team> - Shared Signal Discovery`** — one shared across senders
+3. **`<Workspace/Team> - Shared Cold Fallback`** — one shared across senders
+</inputs>
+
+<objective>
+1. **Inventory first**: `get_campaigns` + `list_tables` in the active workspace. Match existing campaigns to the plan by name (case-insensitive, ignore suffixes like "(Copy)"). A matching non-archived campaign = REUSE; record it and move on. Never create a second campaign for a slot that already has one.
+2. **Create only the missing slots** with `create_on_demand_campaign({ name, senderIds, campaignBrief })`:
+   - Post Engagers lanes: that sender's ID only. Shared lanes: all the senders' IDs.
+   - The brief must include the warm post-engager first-message template style — short, casual, references the post they engaged with, closed question, **no internal vocabulary, no pitch, no meeting ask** in message one:
+
+     ```
+     {{first_name}}
+
+     Hey there
+
+     Saw you pop up on my post about {{post_topic_line}}
+     ```
+
+   - The sequence is auto-selected by sender tier; do not hand-author sequence templates here. Never select a paid-InMail template.
+3. **Verify each slot** after create/reuse: `get_campaign` shows the table exists and a sequence is attached (`list_tables({ hasSequence: true })` as a cross-check).
+4. **Report the reconcile plan and result** — every slot tagged `reused` or `created`, nothing else:
+
+```
+Evergreen Reconcile — {date}
+• Christian Reyes - Post Engagers: reused (18 rows)
+• Thomas Nobbs - Post Engagers: reused (8 rows)
+• Sellable.dev - Shared Signal Discovery: reused
+• Sellable.dev - Shared Cold Fallback: created (empty — needs leads)
+All campaigns remain unlaunched. Next: refresh-sender-engagement to supply the warm lanes, then fill-send-horizon.
+```
+</objective>
+
+<safety>
+- **Idempotent by construction**: rerunning on a schedule must produce all-`reused` and zero new campaigns. If a name matches ambiguously (two candidates), reuse the most recently updated and flag the duplicate for the operator instead of creating a third.
+- Never call `start_campaign` / `start_on_demand_campaign`. New campaigns stay in their default unlaunched state.
+- Never archive, rename, or delete existing campaigns — reconcile is additive; structural removals are operator actions.
+- Respect workspace boundaries: senders and campaigns must belong to the active workspace.
+</safety>

package/skills/fill-send-horizon/SKILL.md

@@ -17,7 +17,7 @@ The invoking prompt (often a scheduled automation) names the targets. Accept any
 - Sender names ("…for csreyes92 and thomas") — resolve via `list_senders`, then `get_campaigns` and match campaigns attached to those senders
 - Nothing specific ("fill send horizon") — operate on all non-archived campaign tables in the active workspace that have a sequence attached (`list_tables({ hasSequence: true })`), skipping ARCHIVED ones
 
-Optional inputs: `targetPreparedMessages` (default: leave unset for the adaptive default), and an explicit "approve" instruction (see safety rules).
+Optional inputs: `targetPreparedMessages` (default: leave unset for the adaptive default), an explicit "approve" instruction (see safety rules), and a **waterfall priority order** (see below).
 </inputs>
 
 <objective>
@@ -30,6 +30,24 @@ For each target campaign:
 5. Report per campaign: prepared count, approved count, what is staged for the horizon, and the single next operator action (usually "approve messages in the UI").
 </objective>
 
+<waterfall>
+## Campaign hierarchy (waterfall order)
+
+When the invoking prompt gives an ordered list — or when a sender has the standard evergreen lanes — fill in **priority order** and only fall through when a lane runs dry:
+
+1. **Default order per sender**: `<Sender> - Post Engagers` (warmest) → `Shared Signal Discovery` → `Shared Cold Fallback` (coldest). The invoking prompt can override with any explicit order ("fill in this order: A, B, C").
+2. **Fill the top lane first.** Move to the next lane ONLY when the current one stops with source exhaustion / no more eligible rows — never because it is merely slow.
+3. **Stop descending once the horizon target is met.** If the warm lane alone fills the horizon, the cold lanes get nothing this run — that is correct, not a gap.
+4. **Report per lane** so the operator can see the waterfall working:
+
+```
+csreyes92 waterfall: Post Engagers filled 4/4 (horizon met — lower lanes skipped)
+thomas waterfall: Post Engagers 1/4 (source thin) → Shared Signal Discovery 3/3 remaining
+```
+
+To **change the hierarchy**, the scheduled automation just states the new order in its prompt — the order is an input to this skill, not stored state.
+</waterfall>
+
 <safety>
 - **Never call `start_campaign`, `start_on_demand_campaign`, or `start_direct_campaign`.** Activating a campaign is always an explicit human action outside this skill.
 - Use `approvalMode: "approve"` ONLY when the invoking prompt explicitly says to auto-approve (e.g. "fill and approve"). Default is `mark_ready` — a human approves in the UI.