@sellable/mcp 0.1.948 → 0.1.950

package/skills/first-campaign-onboarding/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: first-campaign-onboarding
-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.
+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.
 ---
 
 # First Campaign Onboarding
@@ -39,12 +39,29 @@ Classify the run before taking action.
 
 ### Interactive
 
-The user is present and can answer. A plain **yes** in the thread whose parent
-asks "Ready to create your first LinkedIn outbound campaign?" is explicit
-permission to begin preparation, not permission to send. Acknowledge briefly
-and enter **Create-Campaign Handoff** in the same turn. Do not ask for a second
-command, a mention, sender connection, DNC list, or integrations first. The
-existing workflow owns intake; do not invent a second onboarding questionnaire.
+The user is present and can answer. The welcome is the thread parent. It asks
+one question, "what's your LinkedIn profile URL?", and says the profile is used
+to research the customer and their company. (A welcome sent before October 2026
+asks "Ready to create your first LinkedIn outbound campaign?" instead; treat a
+reply to either the same way.)
+
+A reply in that thread is explicit permission to begin preparation, not
+permission to send. It needs no mention of this Agent.
+
+- **The reply contains a LinkedIn profile URL.** Before any tool call, send
+  one short line so the customer is not left looking at silence: "Got it.
+  Researching you and your company now. I'll be back in a couple of minutes
+  with a first campaign to review." Then enter **Create-Campaign Handoff** in
+  the same turn, with that URL as the sender identity.
+- **The reply is a yes, or anything else that agrees, with no profile URL.**
+  Ask for it once, in one sentence: "What's your LinkedIn profile URL? I'll
+  use it to research you and your company." Ask nothing else.
+- **The reply is a question.** Answer it briefly, then repeat the one ask.
+
+Do not ask for a second command, a mention, sender connection, DNC list, or
+integrations first. The existing workflow owns intake; do not invent a second
+onboarding questionnaire. Never guess the company name; use it only once the
+profile or the workspace gives it.
 
 Use the parent thread to interpret short replies; a yes elsewhere is not
 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.
 1. **Invite not accepted:** include the refreshed invite link and ask them to
    join. Do not combine it with a sender/DNC checklist.
 2. **Member present, no draft:** "Want to get your first LinkedIn outbound
-   campaign started? Reply yes in this thread and we'll work out who to reach."
+   campaign started? Reply in this thread with your LinkedIn profile URL. I'll
+   research you and your company and bring back a first campaign to review."
    Do not block this invitation on a connected sender or DNC list.
 3. **Draft present:** name the most advanced draft and the saved next action
    (for example, approving its brief). Offer to continue it, never duplicate it.
@@ -186,8 +204,8 @@ approval. Do not repeat multiple safety disclaimers.
 
 ## Create-Campaign Handoff
 
-After explicit agreement (including yes to the welcome), continue in the same
-conversation; do not ask the user to run another command.
+After explicit agreement (a profile URL or a yes in the welcome thread),
+continue in the same conversation; do not ask the user to run another command.
 
 1. Call `bootstrap_create_campaign({ flowVersion:"v2", host:<current host> })`.
 2. Load `get_subskill_prompt({ subskillName:"create-campaign-v2" })` to