slack-term 1.19.1 → 1.21.0

package/README.md

@@ -13,6 +13,7 @@ byte-for-byte by [`tests/parity.sh`](tests/parity.sh).
 - **Search** — Full-text search across the workspace
 - **Send** — Send messages to channels, DMs, or threads with a confirm-hash safety gate (prevents accidental sends); targeting a message permalink replies in that message's thread
 - **Edit / Delete** — Rewrite or remove a sent message, guarded by the same confirm-hash gate
+- **React** — Add or remove an emoji reaction — a lightweight ack that doesn't grow the thread
 - **Dump** — Bulk-export channel history as markdown
 
 ### Output formatting
@@ -77,6 +78,11 @@ slack send "#general" "ping @ops on call" --no-mentions   # leave @ops as plain
 slack edit "<permalink>" "fixed wording"
 slack delete "<permalink>"
 
+# React instead of replying for a simple ack — keeps the thread tidy (no confirm gate)
+# 👀 seen  ✅ done  ⏳ working on it — target is the #chan:<ts> / permalink form
+slack react "#general:1700000000.000100" white_check_mark
+slack react "<permalink>" eyes --remove   # take a reaction back
+
 # Bulk export channel history
 slack dump --days 7 --filter eng
 
@@ -122,6 +128,14 @@ Requires a Slack user token (`xoxp-...`) with the following scopes:
 - `channels:read`, `groups:read`, `im:read`, `mpim:read` — for channel listing
 - `users:read` — for resolving display names
 - `chat:write` — for sending messages
+- `reactions:write` — for `react` (add/remove reactions)
+
+> Add each scope to the **token type the CLI actually uses**. The CLI defaults to the
+> **user token** (`xoxp-...`), so `reactions:write` must be under **User Token Scopes**.
+> Adding it only to **Bot Token Scopes** makes `slack doctor` (which checks the bot
+> token) look green while `slack react` still fails with `missing_scope` — the bot scope
+> only helps `--as-bot`/bot-token usage. After changing scopes, **reinstall the app** to
+> the workspace for it to take effect.
 
 Set the token via environment variable:
 

package/SKILL.md

@@ -66,8 +66,18 @@ slack send "https://acme.slack.com/archives/C0123456789/p1700000000000100" "Repl
 slack edit "<permalink>" "fixed wording"
 slack delete "<permalink>"
 
+# React instead of replying for a simple ack — keeps threads tidy (no confirm gate)
+# 👀 seen  ✅ done  ⏳ working on it
+slack react "#general:1700000000.000100" white_check_mark
+slack react "<permalink>" eyes --remove   # take it back
+
 # Bulk export a channel's history
 slack dump "#channel-name"
+
+# Download a file attachment (by file ID or file permalink) to disk
+slack download F0123ABC                      # → ./<filename>
+slack download F0123ABC ./invoices/          # into a directory
+slack download "https://acme.slack.com/files/U1/F0123ABC/invoice.pdf"
 ```
 
 Targets for `send` are `#channel`, `@user`, `#channel:<thread_ts>`, or a Slack URL —
@@ -75,12 +85,30 @@ a message permalink replies in that message's thread; a channel-only URL posts t
 The confirm preview prints the resolved destination (`→ ... — THREAD REPLY` or
 `→ ... — NEW top-level message`); verify it before re-running with `--code`.
 
+`send` also runs a **warn-only untagged-mention lint**: if the body names a workspace
+member in plain text (honorifics like `松田さん` / `張老师`, or `Hi Dave`) without a
+matching `<@USERID>` tag, it prints `⚠ possible untagged mention: …` alongside the
+confirm code. It never blocks — third-party/external references are expected to trip it.
+To actually notify someone, write `@handle` (auto-converted to `<@USERID>`; see below).
+
+When the target is a **thread**, the confirm preview shows the thread's recent messages
+(not the channel's last message) and prints `⚠ possible duplicate: …` if your text is
+near-identical to an existing reply — so you can avoid re-posting something already said.
+
+**Etiquette:** prefer a `react` over a reply for simple acks (了解 → `eyes`, 完了 →
+`white_check_mark`, 処理中 → `hourglass`) so threads stay short; read the thread with
+`slack thread`/`slack read` before replying to avoid duplicates; consolidate multiple
+points into one message.
+
 ## Output formatting
 
 - DM channels render as `@DisplayName`; public channels as `#channel-name`.
 - `<@UID>` mention tokens are resolved to display names.
 - `<!date^...>` markup is rendered as human-readable dates.
 - Messages are grouped by day (Today / Yesterday / weekday).
+- Attachments show a `📎 <name> (<size>) [<file-id>]` line under the message; `--json`
+  adds a `files[]` array (`id`, `name`, `mimetype`, `size`, `url_private_download`,
+  `permalink`) only on messages that have attachments. Fetch one with `slack download <file-id>`.
 
 ## Getting a Slack token (first-time setup)
 
@@ -95,6 +123,12 @@ Under **User Token Scopes**:
 - `channels:read`, `groups:read`, `im:read`, `mpim:read` — channel/DM listing
 - `users:read` — resolve display names
 - `chat:write` — send messages
+- `reactions:write` — add/remove reactions (`react`)
+
+> **Token-type gotcha:** the CLI uses the **user token** (`xoxp-`) by default, so scopes
+> must be under **User Token Scopes**. Adding `reactions:write` only to *Bot* Token Scopes
+> makes `slack doctor` (which checks the bot token) pass while `slack react` still errors
+> `missing_scope`. Add it under User Token Scopes, then **reinstall** the app.
 
 ### Steps