@sellable/mcp 0.1.949 → 0.1.950
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: first-campaign-onboarding
|
|
3
|
-
description: Help a new Sellable workspace create its first LinkedIn outbound campaign. A yes reply to the welcome starts the existing create-campaign workflow immediately, with DNC and sender setup at the appropriate gates. Send one next-step scheduled reminder for at most 14 days. Use for welcome-thread replies, first-campaign setup, self-serve onboarding, or scheduled onboarding check-ins.
|
|
3
|
+
description: Help a new Sellable workspace create its first LinkedIn outbound campaign. A LinkedIn profile URL (or a yes) in reply to the welcome starts the existing create-campaign workflow immediately, with DNC and sender setup at the appropriate gates. Send one next-step scheduled reminder for at most 14 days. Use for welcome-thread replies, first-campaign setup, self-serve onboarding, or scheduled onboarding check-ins.
|
|
4
4
|
---
|
|
5
5
|
|
|
6
6
|
# First Campaign Onboarding
|
|
@@ -39,12 +39,29 @@ Classify the run before taking action.
|
|
|
39
39
|
|
|
40
40
|
### Interactive
|
|
41
41
|
|
|
42
|
-
The user is present and can answer.
|
|
43
|
-
|
|
44
|
-
|
|
45
|
-
|
|
46
|
-
|
|
47
|
-
|
|
42
|
+
The user is present and can answer. The welcome is the thread parent. It asks
|
|
43
|
+
one question, "what's your LinkedIn profile URL?", and says the profile is used
|
|
44
|
+
to research the customer and their company. (A welcome sent before October 2026
|
|
45
|
+
asks "Ready to create your first LinkedIn outbound campaign?" instead; treat a
|
|
46
|
+
reply to either the same way.)
|
|
47
|
+
|
|
48
|
+
A reply in that thread is explicit permission to begin preparation, not
|
|
49
|
+
permission to send. It needs no mention of this Agent.
|
|
50
|
+
|
|
51
|
+
- **The reply contains a LinkedIn profile URL.** Before any tool call, send
|
|
52
|
+
one short line so the customer is not left looking at silence: "Got it.
|
|
53
|
+
Researching you and your company now. I'll be back in a couple of minutes
|
|
54
|
+
with a first campaign to review." Then enter **Create-Campaign Handoff** in
|
|
55
|
+
the same turn, with that URL as the sender identity.
|
|
56
|
+
- **The reply is a yes, or anything else that agrees, with no profile URL.**
|
|
57
|
+
Ask for it once, in one sentence: "What's your LinkedIn profile URL? I'll
|
|
58
|
+
use it to research you and your company." Ask nothing else.
|
|
59
|
+
- **The reply is a question.** Answer it briefly, then repeat the one ask.
|
|
60
|
+
|
|
61
|
+
Do not ask for a second command, a mention, sender connection, DNC list, or
|
|
62
|
+
integrations first. The existing workflow owns intake; do not invent a second
|
|
63
|
+
onboarding questionnaire. Never guess the company name; use it only once the
|
|
64
|
+
profile or the workspace gives it.
|
|
48
65
|
|
|
49
66
|
Use the parent thread to interpret short replies; a yes elsewhere is not
|
|
50
67
|
blanket authorization. Keep replies in the same thread. To start a separate
|
|
@@ -172,7 +189,8 @@ sent separately when the Agent becomes ready; do not repeat it daily.
|
|
|
172
189
|
1. **Invite not accepted:** include the refreshed invite link and ask them to
|
|
173
190
|
join. Do not combine it with a sender/DNC checklist.
|
|
174
191
|
2. **Member present, no draft:** "Want to get your first LinkedIn outbound
|
|
175
|
-
campaign started? Reply
|
|
192
|
+
campaign started? Reply in this thread with your LinkedIn profile URL. I'll
|
|
193
|
+
research you and your company and bring back a first campaign to review."
|
|
176
194
|
Do not block this invitation on a connected sender or DNC list.
|
|
177
195
|
3. **Draft present:** name the most advanced draft and the saved next action
|
|
178
196
|
(for example, approving its brief). Offer to continue it, never duplicate it.
|
|
@@ -186,8 +204,8 @@ approval. Do not repeat multiple safety disclaimers.
|
|
|
186
204
|
|
|
187
205
|
## Create-Campaign Handoff
|
|
188
206
|
|
|
189
|
-
After explicit agreement (
|
|
190
|
-
conversation; do not ask the user to run another command.
|
|
207
|
+
After explicit agreement (a profile URL or a yes in the welcome thread),
|
|
208
|
+
continue in the same conversation; do not ask the user to run another command.
|
|
191
209
|
|
|
192
210
|
1. Call `bootstrap_create_campaign({ flowVersion:"v2", host:<current host> })`.
|
|
193
211
|
2. Load `get_subskill_prompt({ subskillName:"create-campaign-v2" })` to
|