@sellable/install 0.1.45 → 0.1.46

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.45",
3
+ "version": "0.1.46",
4
4
  "type": "module",
5
5
  "description": "One-command installer for Sellable MCP in Claude Code and Codex",
6
6
  "bin": {
@@ -253,10 +253,18 @@ Cool — I have this campaign as {company}. Who should the LinkedIn messages sen
253
253
  Sender options should include connected sender names if available, `same as
254
254
  me`, `I’ll paste a different sender profile`, and `Other / custom`.
255
255
 
256
- After the user confirms the subject and sender, run one lightweight company
257
- lookup if it has not already run, then ask the campaign setup questions. The
258
- setup questions should use the confirmed company context so they do not feel
259
- generic.
256
+ After the user confirms the subject and sender, run one bounded lightweight
257
+ company-context pass before asking the campaign setup questions. A sender
258
+ LinkedIn profile lookup is not enough by itself unless it clearly includes the
259
+ company's website, product category, customer, and offer context. If the host can
260
+ run tools in parallel, use one parallel batch with at most 2-3 cheap lookups:
261
+ `mcp__sellable__fetch_company` on a LinkedIn company URL from the profile when
262
+ available; `WebFetch` for the company website/domain when available; otherwise
263
+ one `WebSearch` for `{company} official website` or `{company} product`. If
264
+ parallel tool calls are unavailable, do the single highest-confidence lookup
265
+ first and continue. Do not run full company research, source discovery, Sales
266
+ Nav, Prospeo, Signals, or multi-query browsing here. The goal is a fast 15-30
267
+ second context read so the four setup questions feel specific.
260
268
 
261
269
  Before the identity gate, use this customer-facing shape:
262
270
 
@@ -400,7 +408,7 @@ updates.
400
408
  ```text
401
409
  You're in — {activeWorkspaceName} workspace, ready to roll.
402
410
 
403
- Now — paste the LinkedIn profile URL of the person you'll be sending campaigns from. Usually that's you (the founder), or whoever's voice the messages should sound like.
411
+ 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.
404
412
 
405
413
  e.g. https://www.linkedin.com/in/your-handle
406
414
  ```
@@ -411,7 +419,7 @@ updates.
411
419
  ```text
412
420
  You're set up — your {activeWorkspaceName} workspace is ready.
413
421
 
414
- Now — paste the LinkedIn profile URL of the person you'll be sending campaigns from. Usually that's you (the founder), or whoever's voice the messages should sound like.
422
+ 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.
415
423
 
416
424
  e.g. https://www.linkedin.com/in/your-handle
417
425
  ```