@sellable/mcp 0.1.13 → 0.1.14
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/README.md +2 -2
- package/package.json +1 -1
- package/skills/create-campaign-v2/SKILL.md +19 -2
package/README.md
CHANGED
|
@@ -83,14 +83,14 @@ The token is provided when you generate it. Use `list_workspaces` +
|
|
|
83
83
|
For customer/package installs, use the public installer:
|
|
84
84
|
|
|
85
85
|
```bash
|
|
86
|
-
npx -y @sellable/install@0.1.
|
|
86
|
+
npx -y @sellable/install@0.1.14 --host codex --token skt_live_your_token_here --workspace-id your_workspace_id
|
|
87
87
|
```
|
|
88
88
|
|
|
89
89
|
If you already have `~/.sellable/config.json`, rerun/verify without rewriting
|
|
90
90
|
auth:
|
|
91
91
|
|
|
92
92
|
```bash
|
|
93
|
-
npx -y @sellable/install@0.1.
|
|
93
|
+
npx -y @sellable/install@0.1.14 --host codex
|
|
94
94
|
sellable --verify-only --host codex
|
|
95
95
|
```
|
|
96
96
|
|
package/package.json
CHANGED
|
@@ -129,7 +129,8 @@ Validated draft directory:
|
|
|
129
129
|
once if available. This is a shortcut to deduce who the user might be from
|
|
130
130
|
their Sellable API token and connected LinkedIn accounts. Do not present it as
|
|
131
131
|
a sender picker yet. If there is one strong likely sender, use `enrich_sender`
|
|
132
|
-
to infer their current or most recent company, then ask
|
|
132
|
+
to infer their current or most recent company, then ask a structured
|
|
133
|
+
confirmation question:
|
|
133
134
|
|
|
134
135
|
```text
|
|
135
136
|
I’m ready to build this in {workspace}. I found {matched sender} connected here.
|
|
@@ -137,6 +138,22 @@ Validated draft directory:
|
|
|
137
138
|
Is that you, and is this campaign for {company}?
|
|
138
139
|
```
|
|
139
140
|
|
|
141
|
+
The options must be:
|
|
142
|
+
|
|
143
|
+
1. `Yes, that's me and this is for {company}`
|
|
144
|
+
2. `That's me, but this is for a different company`
|
|
145
|
+
3. `No, I'll paste my LinkedIn URL so you can look me up`
|
|
146
|
+
4. `No, I'll paste the company website instead`
|
|
147
|
+
5. `Other / custom`
|
|
148
|
+
|
|
149
|
+
If the user chooses option 2, ask for the company website/domain and call
|
|
150
|
+
`fetch_company` when possible, otherwise one web lookup. If the user chooses
|
|
151
|
+
option 3, ask for their LinkedIn URL, call `fetch_linkedin_profile`, infer
|
|
152
|
+
their current or most recent company, then confirm company and sender again.
|
|
153
|
+
If the user chooses option 4, ask for the company website/domain, call
|
|
154
|
+
`fetch_company` when possible, otherwise one web lookup, then ask who the
|
|
155
|
+
LinkedIn messages should send from.
|
|
156
|
+
|
|
140
157
|
If there is no strong sender match, make the first quick question panel ask
|
|
141
158
|
for the user's LinkedIn URL or company website. The point of this gate is not
|
|
142
159
|
"pick a sender"; it is to learn who the user is, infer the current or most
|
|
@@ -175,7 +192,7 @@ Validated draft directory:
|
|
|
175
192
|
```
|
|
176
193
|
|
|
177
194
|
Sender options should include connected sender names if available, `same as
|
|
178
|
-
|
|
195
|
+
me`, `I’ll paste a different sender profile`, and `Other / custom`.
|
|
179
196
|
|
|
180
197
|
After the user confirms the subject and sender, run one lightweight company
|
|
181
198
|
lookup if it has not already run, then ask the campaign setup questions. The
|