@sellable/mcp 0.1.329 → 0.1.331
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: create-evergreen-campaigns
|
|
3
|
-
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
|
|
3
|
+
description: Reconcile a sender team's evergreen campaign structure — create-or-reuse the standing campaigns (per-sender post engagers + shared fallback/source lanes) idempotently, with send-lane sequences and prospect-safe message briefs. Never duplicates, never launches. Schedule-automation friendly ("make sure evergreen campaigns exist for these users").
|
|
4
4
|
visibility: internal
|
|
5
5
|
---
|
|
6
6
|
|
|
@@ -16,15 +16,28 @@ producing duplicates. Reconcile/create-reuse only; this skill never launches cam
|
|
|
16
16
|
<inputs>
|
|
17
17
|
The invoking prompt names the senders ("create evergreen campaigns for csreyes92 and thomas"). Resolve each via `list_senders`.
|
|
18
18
|
|
|
19
|
+
If the invoking prompt says scheduled, automation, cron, heartbeat, fresh-thread,
|
|
20
|
+
run without user input, or similar, run in **automation mode**:
|
|
21
|
+
|
|
22
|
+
- Do not ask the user to confirm templates, delivery format, or sample output.
|
|
23
|
+
- Reconcile structure and record any template/config polish as `created`,
|
|
24
|
+
`reused`, `repaired`, `flagged`, or `blocked`.
|
|
25
|
+
- Apply only safe metadata repairs that do not create rows, generate messages,
|
|
26
|
+
approve rows, launch campaigns, send messages, or spend paid InMail.
|
|
27
|
+
|
|
28
|
+
If the invoking prompt explicitly asks for interactive message polish or sample
|
|
29
|
+
proof, run in **interactive polish mode** and use the confirmation/sample steps
|
|
30
|
+
below.
|
|
31
|
+
|
|
19
32
|
Default evergreen plan per workspace (override only if the prompt specifies different lanes):
|
|
20
33
|
|
|
21
34
|
1. **`<Sender Name> - Post Engagers`** — one per sender (warm lane, highest priority)
|
|
22
|
-
2. **`<Workspace/Team> - Shared Signal Discovery`** — one shared across senders
|
|
23
|
-
3. **`<Workspace/Team> - Shared Cold Fallback`** — one shared across senders
|
|
35
|
+
2. **`<Workspace/Team> - Shared Signal Discovery`** — one shared source lane across senders
|
|
36
|
+
3. **`<Workspace/Team> - Shared Cold Fallback`** — one shared source/fallback lane across senders
|
|
24
37
|
</inputs>
|
|
25
38
|
|
|
26
39
|
<objective>
|
|
27
|
-
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.
|
|
40
|
+
1. **Inventory first**: `get_campaigns` + `list_tables` + `get_campaign_waterfall` in the active workspace. Treat `list_tables` and the managed waterfall as authoritative for older managed slots; `get_campaigns` is a recent campaign page and may miss canonical evergreen lanes. Match existing campaigns/tables/waterfall slots to the plan by name (case-insensitive, ignore suffixes like "(Copy)") and stored slot identity. A matching non-archived campaign/table/waterfall slot = REUSE; record it and move on. Never create a second campaign for a slot that already has one in any of those inventories.
|
|
28
41
|
2. **Create only the missing slots** with `create_on_demand_campaign({ name, senderIds, campaignBrief })`:
|
|
29
42
|
- Post Engagers lanes: that sender's ID only. Shared lanes: all the senders' IDs.
|
|
30
43
|
- 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:
|
|
@@ -42,23 +55,28 @@ Default evergreen plan per workspace (override only if the prompt specifies diff
|
|
|
42
55
|
- **InMail lanes can never be multiline**: an InMail is one message and the recipient must reply before anything else can be sent. InMail-bound templates must read as one cohesive message — declare `Delivery format: single message (InMail — no follow-up until reply)` and never structure the copy to depend on multi-message pacing.
|
|
43
56
|
|
|
44
57
|
- The sequence is auto-selected by sender tier; do not hand-author sequence templates here. Never select a paid-InMail template.
|
|
45
|
-
3. **Verify each slot** after create/reuse:
|
|
46
|
-
|
|
58
|
+
3. **Verify each slot** after create/reuse/repair:
|
|
59
|
+
- `get_campaign` shows the campaign exists, remains unlaunched, and has the expected workflow table.
|
|
60
|
+
- Send/action lanes such as Post Engagers have a sequence attached. Use `list_tables({ hasSequence: true })` as a quick cross-check, but do not treat that filter as the only proof. If the canonical campaign/table is missing from the sequence-filtered table list but a safe `attach_recommended_sequence({ campaignId })` repair/precheck returns `SEQUENCE_EXISTS`, record `sequence attached (verified by SEQUENCE_EXISTS precheck; list_tables.hasSequence mismatch)` and do not retry.
|
|
61
|
+
- Only use `attach_recommended_sequence({ campaignId })` for a send-lane sequence repair/precheck when the target is a canonical prod slot and the invoking prompt allows sequence repair. Call it at most once without `confirmed`; a successful response is `repaired`, and `SEQUENCE_EXISTS` is non-mutating proof that a sequence already exists. Never call `attach_recommended_sequence` or `attach_sequence` with `confirmed:true` in evergreen automation unless the user explicitly asks to replace an existing sequence.
|
|
62
|
+
- Source-only shared lanes may legitimately have `hasSequence:false` when they only supply rows through the managed waterfall. For those, verify the active waterfall linkage, table ID, campaign ID, source type, and priority; report `source-only/no sequence expected` instead of repairing or duplicating.
|
|
63
|
+
4. **Interactive polish mode only: confirm the message template with the user — and check it reads chat-native.** Show the exact first-message template each created campaign's brief carries and ask the user to confirm or adjust it before moving on. Because DM copy may send paragraph-by-paragraph (each blank-line block becomes its own message), every paragraph must read like something a human literally typed as a separate chat message:
|
|
47
64
|
- **No letter punctuation.** `Hey {{first_name}}` — never `Hey {{first_name}},` (nobody types a trailing comma and hits send). No `Dear`, no sign-offs, no `Best,`.
|
|
48
65
|
- Each paragraph stands alone as a message — short, lowercase-casual is fine, sentence fragments are fine.
|
|
49
66
|
- No paragraph should depend on letter formatting (no "As I mentioned above" referencing layout).
|
|
50
67
|
If the template violates these, propose the chat-native version and ask; on approval, update the brief via `update_campaign_brief` and show the final version.
|
|
51
68
|
|
|
52
69
|
**Also confirm the delivery format and keep config in sync.** Ask the user whether DM lanes should send multiline (paragraph-per-message) or as a single message. Record the answer as the brief's `Delivery format:` line, and when multiline is chosen, set `actionConfig.sendEachParagraphAsMessage: true` on that campaign's `send_dm` column via `update_column` (config edits run no cells and nothing sends from unlaunched campaigns). Never set the paragraph-split flag on InMail columns — the option does not apply to InMail.
|
|
53
|
-
5. **
|
|
54
|
-
6. **
|
|
70
|
+
5. **Interactive polish mode only: prove the template on one real row.** For ONE campaign that has at least one lead row (add one via `add_on_demand_leads` if every lane is empty and the user provides/approves a test lead), generate a message for exactly one row (`queue_campaign_cells` with `columnRole: "generateMessage"`, `rowSelector: { type: "reviewBatch", limit: 1 }` or the single row's ID), wait for it, then show the user the generated message next to the template — AND show how it would split if paragraph-per-message sending is enabled (list each paragraph as `msg 1:`, `msg 2:`, …) so the user confirms each one reads like a real typed message. Check alignment: tone, structure, no internal vocabulary, correct token substitution, no letter punctuation. Do NOT approve the row or generate for more rows — one sample only.
|
|
71
|
+
6. **Automation mode template/config audit**: inspect existing send-lane briefs for a `Delivery format:` line and chat-native warm template. If a send lane is missing the line and the prompt allows cleanup, update only the campaign brief metadata with the safest default for that lane (`Delivery format: single message (LinkedIn DM; line breaks remain inside one generated message; no follow-up until reply)`). If cleanup is not allowed, flag it. Do not generate a sample row in automation mode unless the invocation explicitly asks for sample proof.
|
|
72
|
+
7. **Report the reconcile plan and result** — every slot tagged `reused`, `created`, `repaired`, `flagged`, or `blocked`, plus template/sample details only when that mode ran:
|
|
55
73
|
|
|
56
74
|
```
|
|
57
75
|
Evergreen Reconcile — {date}
|
|
58
|
-
• Christian Reyes - Post Engagers: reused (18 rows)
|
|
59
|
-
• Thomas Nobbs - Post Engagers: reused (8 rows)
|
|
60
|
-
• Sellable.dev - Shared Signal Discovery: reused
|
|
61
|
-
• Sellable.dev - Shared Cold Fallback: created (
|
|
76
|
+
• Christian Reyes - Post Engagers: reused (18 rows, sequence attached)
|
|
77
|
+
• Thomas Nobbs - Post Engagers: reused (8 rows, sequence attached)
|
|
78
|
+
• Sellable.dev - Shared Signal Discovery: reused (source-only/no sequence expected)
|
|
79
|
+
• Sellable.dev - Shared Cold Fallback: created (source-only/no sequence expected)
|
|
62
80
|
All campaigns remain unlaunched. Next: refresh-sender-engagement to supply the warm lanes, then fill-send-horizon.
|
|
63
81
|
```
|
|
64
82
|
</objective>
|