@sellable/install 0.1.47 → 0.1.49

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": "@sellable/install",
3
- "version": "0.1.47",
3
+ "version": "0.1.49",
4
4
  "type": "module",
5
5
  "description": "One-command installer for Sellable MCP in Claude Code and Codex",
6
6
  "bin": {
@@ -70,9 +70,8 @@ instruction loading, file lookup, plugin cache versions, missing linked files,
70
70
  or tool discovery. Start in product language:
71
71
 
72
72
  ```text
73
- I’ll help you launch this as a Sellable campaign. First I’ll confirm who we’re
74
- sending from and which company this is for, then I’ll turn that into a campaign
75
- brief before anything is created.
73
+ I’ll help you launch this as a Sellable campaign. First I’ll confirm the sender
74
+ and company, then draft the campaign brief for your approval.
76
75
  ```
77
76
 
78
77
  If a linked/local skill file is stale or missing, silently use the installed
@@ -181,7 +180,9 @@ senders. If there is any likely connected sender, use
181
180
  recent company, then ask a structured confirmation question:
182
181
 
183
182
  ```text
184
- I’m ready to build this in {workspace}. I found {matched sender} connected here.
183
+ Workspace: {workspace}
184
+
185
+ I found {matched sender} connected here.
185
186
 
186
187
  Is that you, and is this campaign for {company}?
187
188
  ```
@@ -212,11 +213,11 @@ with the structured question tool. Ask in normal chat for the user's LinkedIn
212
213
  URL or the company they want to send on behalf of so you can research context:
213
214
 
214
215
  ```text
215
- I’m ready to build this in {workspace}.
216
+ Workspace: {workspace}
216
217
 
217
- First, paste your LinkedIn URL or the company website you want to send on
218
- behalf of. I’ll use that to understand the company before we pick the target,
219
- offer, proof, and lead source.
218
+ First, paste your LinkedIn URL or the company website. I’ll use it to confirm
219
+ the sender and company, then we’ll choose the target, offer, proof, and lead
220
+ source.
220
221
  ```
221
222
 
222
223
  If there is no strong sender match, do not show a structured choice that says
@@ -226,7 +227,7 @@ current or most recent company, and then confirm who we are sending from. The
226
227
  customer-facing shape should be:
227
228
 
228
229
  ```text
229
- I’m ready to build this in {workspace}.
230
+ Workspace: {workspace}
230
231
 
231
232
  First, what’s your LinkedIn URL? If you’d rather start from the company, paste
232
233
  the company website instead.
@@ -236,6 +237,8 @@ After the user pastes a URL/domain, do the lightweight lookup. For a LinkedIn pr
236
237
  `mcp__sellable__fetch_linkedin_profile` and infer the user's current or most
237
238
  recent company from the profile. For a company website, call
238
239
  `mcp__sellable__fetch_company` when possible, otherwise one web lookup.
240
+ Before the lookup, use concise progress copy:
241
+ `Got it — I’ll look it up and confirm the sender + company.`
239
242
 
240
243
  If `mcp__sellable__list_senders` did not already run, call it once after the
241
244
  lookup to see whether the fetched user appears to match a connected sender. If
@@ -270,14 +273,11 @@ second context read so the four setup questions feel specific.
270
273
  Before the identity gate, use this customer-facing shape:
271
274
 
272
275
  ```text
273
- I’m ready to build the campaign in {workspace}.
274
-
275
- First I’ll check whether you already have a connected LinkedIn account here. If
276
- I can’t confirm it, I’ll ask for your LinkedIn URL or company website and use
277
- that to understand the company before we choose the target, offer, proof, and
278
- lead source.
276
+ Workspace: {workspace}
279
277
 
280
- Then I’ll turn that into a campaign brief for you to approve before anything is created.
278
+ First I’ll check for a connected LinkedIn sender. If I can’t confirm one, I’ll
279
+ ask for your LinkedIn URL or company website before we choose the target, offer,
280
+ proof, and lead source.
281
281
  ```
282
282
 
283
283
  Do not silently ask approval questions as plain chat when `request_user_input` is
@@ -410,7 +410,7 @@ updates.
410
410
  ```text
411
411
  You're in — {activeWorkspaceName} workspace, ready to roll.
412
412
 
413
- Now — paste the LinkedIn profile URL of the person you'll be sending campaigns from. Usually that's you, or whoever's voice the messages should sound like.
413
+ Now — paste the LinkedIn profile URL of the person you'll be sending this campaign from. Usually that's you. If someone else will send this campaign, paste their profile instead.
414
414
 
415
415
  e.g. https://www.linkedin.com/in/your-handle
416
416
  ```
@@ -421,7 +421,7 @@ updates.
421
421
  ```text
422
422
  You're set up — your {activeWorkspaceName} workspace is ready.
423
423
 
424
- Now — paste the LinkedIn profile URL of the person you'll be sending campaigns from. Usually that's you, or whoever's voice the messages should sound like.
424
+ Now — paste the LinkedIn profile URL of the person you'll be sending this campaign from. Usually that's you. If someone else will send this campaign, paste their profile instead.
425
425
 
426
426
  e.g. https://www.linkedin.com/in/your-handle
427
427
  ```