slack-term 1.39.2 → 1.40.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/README.md +1 -1
- package/SKILL.md +17 -1
- package/dist/cli.js +165 -159
- package/package.json +1 -1
- package/ts/cli.ts +205 -2
- package/ts/slack.ts +56 -11
- package/ts/slackTodos.ts +85 -0
- package/ts/urlGuard.ts +162 -10
package/README.md
CHANGED
|
@@ -91,7 +91,7 @@ slack search "deploy" --count 50
|
|
|
91
91
|
slack send "#general" "Hello team"
|
|
92
92
|
# Prints who you're acting as (From: @handle (Uxxxx) — Workspace) + a destination
|
|
93
93
|
# preview + confirm code; rerun with --code=<code> to actually send. Every gated write
|
|
94
|
-
# (send/edit/delete/upload/schedule/channel create/lists/drafts) shows that From: line and
|
|
94
|
+
# (send/edit/delete/upload/schedule/channel create/rename/lists/drafts) shows that From: line and
|
|
95
95
|
# binds it into the code, so a profile switch mid-flow invalidates it instead of acting
|
|
96
96
|
# as the wrong account.
|
|
97
97
|
slack send "#general" "Hello team" --code=<code>
|
package/SKILL.md
CHANGED
|
@@ -120,7 +120,7 @@ plus `[as bot]` under `--as-bot`) and the resolved destination (`→ ... — THR
|
|
|
120
120
|
`→ ... — NEW top-level message`); verify both before re-running with `--code`.
|
|
121
121
|
|
|
122
122
|
**Every** gated write opens its preview with that same `From:` line — `send`, `edit`,
|
|
123
|
-
`delete`, `upload`, `schedule send`, `schedule rm`, `channel create`, `lists create/add/set/share`, `drafts edit`,
|
|
123
|
+
`delete`, `upload`, `schedule send`, `schedule rm`, `channel create`, `channel rename`, `lists create/add/set/share`, `drafts edit`,
|
|
124
124
|
`drafts delete` — and the identity is part of the confirm hash: switching
|
|
125
125
|
profile/token between preview and confirm invalidates the code instead of acting as
|
|
126
126
|
someone else. It matters most on `schedule send`, where the message goes out later,
|
|
@@ -275,6 +275,22 @@ Reason flags stack independently of progress and of each other: ❗ `exclamation
|
|
|
275
275
|
`slack thread`/`slack read` before replying to avoid duplicates; consolidate multiple
|
|
276
276
|
points into one message.
|
|
277
277
|
|
|
278
|
+
### todos — Slack's To-dos tab (read-only)
|
|
279
|
+
|
|
280
|
+
Not `slack todo`: that tracks tasks as reactions. `slack todos` reads Slack's own
|
|
281
|
+
**personal** To-dos tab (the successor of "Later"), the list in the sidebar.
|
|
282
|
+
|
|
283
|
+
```bash
|
|
284
|
+
slack todos # open to-dos, soonest due first (OVERDUE marked)
|
|
285
|
+
slack todos --filter completed # also: saved (everything saved), archived
|
|
286
|
+
slack todos --json -n 20 # one object per item: due, done, permalink, text
|
|
287
|
+
```
|
|
288
|
+
|
|
289
|
+
There is no public API: it uses the desktop client's internal `saved.list`, so
|
|
290
|
+
it needs the **xoxc session** (`slack auth login`) and shows only your own
|
|
291
|
+
to-dos. Bots can't see them. Slack can change this endpoint without notice.
|
|
292
|
+
Adding and completing to-dos is not supported yet.
|
|
293
|
+
|
|
278
294
|
## Output formatting
|
|
279
295
|
|
|
280
296
|
- DM channels render as `@DisplayName`; public channels as `#channel-name`.
|