@sortlist/cli 0.58.0 → 0.60.0
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/dist/index.js +28 -8
- package/dist/index.js.map +1 -1
- package/package.json +1 -1
- package/skills/sortlist-cli/SKILL.md +10 -7
- package/skills/sortlist-go-to-market/SKILL.md +11 -7
package/package.json
CHANGED
|
@@ -185,10 +185,11 @@ sl schema inspect ContactsFilterInput # an input object or enum used by a
|
|
|
185
185
|
`--filter '{"domain":{"in":["google.com"]}}'`.
|
|
186
186
|
- Keep output small: `--fields` takes dotted paths, relative to a record when the result is a page
|
|
187
187
|
(`jobTitle`, `organization.name`, not `contacts.nodes.jobTitle`); the page's `pageInfo` comes along
|
|
188
|
-
on its own
|
|
189
|
-
|
|
190
|
-
|
|
191
|
-
|
|
188
|
+
on its own. `--total-count` adds the total on other services' lists; never pass it to an Atlas
|
|
189
|
+
command, where counting every match is too slow. In a terminal a table shows a page only as a
|
|
190
|
+
count of its entries, so pass `--json` there; from a tool call the output is JSON already.
|
|
191
|
+
`--exclude` drops heavy fields, and `--depth` controls how deep nested objects are selected
|
|
192
|
+
(default 0) and never selects a deprecated field; name one in `--fields` to get it anyway.
|
|
192
193
|
- A mutation prints the object it returns, and its `--fields` name that object's fields:
|
|
193
194
|
`create-company --fields id,slug`, not `company.id`.
|
|
194
195
|
- Operation descriptions carry the business rules. Read `--help` before a mutation, not after.
|
|
@@ -217,7 +218,7 @@ sl atlas find-organizations --filter '{"domain":{"eq":"acme.com"}}' --page '{"fi
|
|
|
217
218
|
--fields name,domain
|
|
218
219
|
|
|
219
220
|
sl atlas find-contacts --organization-filter '{"domain":{"eq":"acme.com"}}' --wait \
|
|
220
|
-
--fields jobTitle,jobLevel
|
|
221
|
+
--fields jobTitle,jobLevel
|
|
221
222
|
```
|
|
222
223
|
|
|
223
224
|
- A page is sent `FILLING` while Atlas may still change it and again `COMPLETE` on its last version;
|
|
@@ -228,7 +229,7 @@ sl atlas find-contacts --organization-filter '{"domain":{"eq":"acme.com"}}' --wa
|
|
|
228
229
|
--page '{"first":20,"after":"…"}' --wait`): run it as given. With `after`, Atlas
|
|
229
230
|
reads on in the same search and ignores the call's own `--filter`, `--organization-filter` and
|
|
230
231
|
`--sort`. A search lives one hour and lists at most 1000 records; `hasNextPage` says whether more
|
|
231
|
-
follow
|
|
232
|
+
follow. Atlas gives no count of every match: say "more follow", never a total.
|
|
232
233
|
- **One record:** `--page '{"first":1}'` with a filter naming it: an organization by
|
|
233
234
|
`"domain":{"eq":…}`; a contact by `"id"`, `"linkedinUrl"` or `"emailAddress"` with `eq`, or by
|
|
234
235
|
`"name":{"eq":…}` together with `--organization-filter '{"id":{"eq":"<organization id>"}}'`.
|
|
@@ -438,7 +439,9 @@ sl outreach outbound-channel-accounts --fields id,channel,provider,status,extern
|
|
|
438
439
|
(section 3). Create it while acting for the company the user chose.
|
|
439
440
|
- **Find the LinkedIn member id** with a silent lookup (2 credits, nobody is notified):
|
|
440
441
|
`sl outreach perform-outbound-channel-action --channel-account-id <id> --external-id lookup-<slug>
|
|
441
|
-
--action '{"linkedinLookupProfile":{"identifier":"<
|
|
442
|
+
--action '{"linkedinLookupProfile":{"identifier":"<public identifier>"}}' --wait`. The identifier is
|
|
443
|
+
the **last segment of the profile URL** (`jane-doe-1a2b3c` for `https://www.linkedin.com/in/jane-doe-1a2b3c/`),
|
|
444
|
+
or a member id: never the full URL, which LinkedIn refuses with a 403 (`FAILED`, nothing charged). Its
|
|
442
445
|
`result` carries `member_id` (the `ACoAA…` id every other action takes), `network_distance` (`SELF`
|
|
443
446
|
… `OUT_OF_NETWORK`) and `pending_invitation`. Don't invite a first-degree connection or someone with a
|
|
444
447
|
pending invitation: LinkedIn doesn't always refuse it.
|
|
@@ -86,21 +86,23 @@ two minutes) and loose (people outside the place or the industry), so never run
|
|
|
86
86
|
```bash
|
|
87
87
|
sl atlas find-organizations --filter '{"divisionIds":{"in":[…]},"companySize":{"overlaps":[10,200]},"description":[{"queries":["fashion brand","clothing brand"],"match":"INCLUDED_STRICT"}]}' \
|
|
88
88
|
--sort '[{"field":"DESCRIPTION_DISTANCE","query":"<what the ideal company does>","direction":"ASC"}]' \
|
|
89
|
-
--page '{"first":20}' --wait --fields id,domain
|
|
89
|
+
--page '{"first":20}' --wait --fields id,domain
|
|
90
90
|
sl atlas find-contacts --organization-filter '{"id":{"in":["<the 20 organization ids>"]}}' \
|
|
91
91
|
--filter '{"jobTitle":[{"queries":["Founder","CEO","Head of E-commerce"],"match":"INCLUDED_STRICT"}],"reachableBy":{"all":["LINKEDIN_URL"]}}' \
|
|
92
|
-
--page '{"first":20}' --wait --fields id,jobTitle,city,organization.node.domain
|
|
92
|
+
--page '{"first":20}' --wait --fields id,jobTitle,city,organization.node.domain
|
|
93
93
|
```
|
|
94
94
|
|
|
95
|
+
- Never pass `--total-count` to an Atlas command: counting every match is too slow.
|
|
95
96
|
- Describe what the company **does** with `description`, not only `industry`: industry alone lets
|
|
96
97
|
through companies with no industry recorded (`gmail.com` came first in a rehearsal).
|
|
97
98
|
- Run one `sl` command per tool call, without `;`, `&&`, `echo` or redirects to files: each extra
|
|
98
99
|
operation is a permission prompt the user has to answer.
|
|
99
100
|
|
|
100
|
-
Show a compact result: how many companies and people
|
|
101
|
-
|
|
102
|
-
|
|
103
|
-
|
|
101
|
+
Show a compact result: how many companies and people the pages hold, whether more follow
|
|
102
|
+
(`pageInfo.hasNextPage`, never a total), and a table of up to 10 people with **temporary labels**
|
|
103
|
+
(P1, P2…), job title, company domain and city. Names are locked: don't reveal them to decorate the
|
|
104
|
+
table. If a filter returns nothing or too much, adjust it once and say what changed; don't silently
|
|
105
|
+
loosen geography, seniority or industry.
|
|
104
106
|
|
|
105
107
|
## Step 3. Watch buying signals (Signals)
|
|
106
108
|
|
|
@@ -154,12 +156,14 @@ Approval covers **step 1 and 2 for the named prospects only**. Then, per prospec
|
|
|
154
156
|
```bash
|
|
155
157
|
sl outreach perform-outbound-channel-action --channel-account-id <account> \
|
|
156
158
|
--external-id <campaign>-<prospect>-lookup \
|
|
157
|
-
--action '{"linkedinLookupProfile":{"identifier":"<
|
|
159
|
+
--action '{"linkedinLookupProfile":{"identifier":"<public identifier>"}}' --wait
|
|
158
160
|
sl outreach perform-outbound-channel-action --channel-account-id <account> \
|
|
159
161
|
--external-id <campaign>-<prospect>-invite \
|
|
160
162
|
--action '{"linkedinInvite":{"memberId":"<member id>","message":"<note>"}}' --wait
|
|
161
163
|
```
|
|
162
164
|
|
|
165
|
+
- The lookup's `identifier` is the last segment of the prospect's LinkedIn URL (`jane-doe-1a2b3c`),
|
|
166
|
+
never the whole URL: a full URL fails with a 403 and nothing is charged.
|
|
163
167
|
- Skip the invitation when the lookup shows a first-degree connection or a pending invitation; go
|
|
164
168
|
straight to a message, after asking.
|
|
165
169
|
- Report each action's state. A `FAILED` action is reported, never resent under a new external id.
|