slack-term 1.25.0 → 1.26.1

package/README.md

@@ -143,13 +143,17 @@ The other two are the flags:
 They stack with each other and with ❗/❓; `--state stuck` matches a task with any of them.
 
 ```sh
-slack todo ls                              # --state open (default): marked, not done/dropped
+# Two listings, split by whose reactions count — the distinction is the command,
+# not a flag, so "everyone's list" and "my list" can't be confused at a glance.
+slack todo ls                              # EVERYONE's tasks (has:)
+slack mytodo ls                            # only tasks YOU reacted to (hasmy:)
+
 slack todo ls --state untriaged            # marked, no progress reaction yet
 slack todo ls --state doing --in "#eng"    # scoped to a channel
-slack todo ls --state stuck                # unfinished AND carrying a reason flag
+slack mytodo ls --state stuck              # my unfinished tasks carrying a reason flag
 slack todo ls --state stuck --from "@alice" # …and it was alice who wrote it
-slack todo ls --from me                    # tasks on my own messages
-slack todo ls --state done --shared        # anyone's reactions, not just mine
+slack todo ls --from me                    # tasks on my own messages (any reactor)
+slack todo ls --mine                       # same as `slack mytodo ls`
 slack todo set "#eng:1700000000.000100" doing
 slack todo flag "<permalink>" waiting          # their ball now
 slack todo flag "<permalink>" needs-discussion
@@ -160,10 +164,15 @@ slack todo doctor --in "#eng" --fix        # keep the highest-priority one
 
 Notes:
 
-- `todo ls` is read-only and runs **exactly one** `search.messages` call — priority is
-  expressed as negated `hasmy:` terms in the query, not as multiple searches
-  (`search.messages` is Tier 2, ~20 req/min). By default it matches only *your* reactions
-  (`hasmy:`); `--shared` switches to anyone's (`has:`). Slack's search index lags a little
+- **`todo ls` vs `mytodo ls`** — `todo ls` matches anyone's reactions (`has:`), `mytodo ls`
+  only your own (`hasmy:`). Everything else about them is identical. Both print a
+  `From: @handle (Uxxxx) — Workspace` line first, because `hasmy:` resolves against
+  whichever account the token belongs to — "my tasks" means nothing until you know who
+  *my* is, and a stale profile otherwise lists someone else's list without saying so.
+  (`todo ls --mine` is a one-off shortcut to the narrow view.)
+- Both are read-only and run **exactly one** `search.messages` call — priority is expressed
+  as negated `has:`/`hasmy:` terms in the query, not as multiple searches
+  (`search.messages` is Tier 2, ~20 req/min). Slack's search index lags a little
   behind `reactions.add`, so a just-set task may take a moment to appear.
 - `todo set` **adds the new reaction before removing the old ones**, and removes serially.
   The reverse order would leave a window with no progress reaction at all — a crash or a
@@ -287,6 +296,19 @@ delivery (3-second interval). Supports `--since=<duration>` for backfill,
 that mention you. Uses `conversations.history?oldest=<ts>` as a cursor so
 already-seen messages are never re-printed, even across reconnects.
 
+## Ecosystem
+
+This CLI is the human-comms surface of the
+[agent-yes](https://github.com/snomiao/agent-yes) fleet: agent-yes runs, watches and
+delegates to AI coding agents, and `slack` is how they read and answer the humans they
+work with. Neither depends on the other — they share a stance rather than a library:
+file-based state over daemons, one command surface across two runtimes, gates on the
+irreversible and warnings on the merely unwise, and no real operational data in a public
+repo.
+
+A write-up of the design decisions behind the confirm gate lives on the agent-yes lab:
+[A confirm code that goes stale](https://lab.agent-yes.com/2026-08-11-slack-term-safe-writes).
+
 ## Related / prior art
 
 - [`slkcli`](https://www.npmjs.com/package/slkcli) by

package/SKILL.md

@@ -8,11 +8,15 @@ description: "Terminal Slack CLI — read news/mentions/DMs/channel history, ful
 A lightweight Slack CLI for quick workspace interaction from the terminal.
 Two implementations share one command surface (parity-tested):
 
-- **TypeScript** (bun-first), published as `@snomiao/slack` on npm.
+- **TypeScript** (bun-first), published as `slack-term` on npm.
 - **Rust** native binary, installable via `cargo install`.
 
 Binary name: `slack` (also aliased as `sl` / invoked via `sc sl ...` in some setups).
 
+Part of the [agent-yes](https://github.com/snomiao/agent-yes) ecosystem — this is the CLI an
+agent uses to talk to humans. Design notes:
+[lab.agent-yes.com](https://lab.agent-yes.com/2026-08-11-slack-term-safe-writes).
+
 ## When to use
 
 - User wants to read Slack activity, mentions, DMs, or channel history without opening the Slack app.
@@ -25,10 +29,13 @@ Binary name: `slack` (also aliased as `sl` / invoked via `sc sl ...` in some set
 TypeScript (recommended — any platform with Node 18+):
 
 ```sh
-npm install -g @snomiao/slack
-# or: bun add -g @snomiao/slack / pnpm add -g @snomiao/slack
+npm install -g slack-term
+# or: bun add -g slack-term / pnpm add -g slack-term
 ```
 
+> Previously published as `@snomiao/slack`; that name is deprecated on npm and
+> no longer updated. Install `slack-term`.
+
 Rust (native binary):
 
 ```sh
@@ -79,9 +86,10 @@ slack react "#general:1700000000.000100" white_check_mark
 slack react "<permalink>" eyes --remove   # take it back
 
 # Task tracking on reactions — 📌 marks a task, a second reaction holds progress
-slack todo ls                                     # my open tasks (read-only, 1 search)
+slack todo ls                                     # EVERYONE's open tasks (has:)
+slack mytodo ls                                   # only tasks YOU reacted to (hasmy:)
 slack todo ls --state untriaged --in "#general"   # marked but no progress yet
-slack todo ls --state stuck                       # unfinished + a reason flag
+slack mytodo ls --state stuck                     # my unfinished tasks + a reason flag
 slack todo set "#general:1700000000.000100" doing # pending|doing|done|dropped
 slack todo ls --state stuck --from "@alice"        # …and alice wrote it
 slack todo flag "<permalink>" waiting             # alert|needs-discussion|waiting|blocked
@@ -148,8 +156,13 @@ Reason flags stack independently of progress and of each other: ❗ `exclamation
 
 (⏳ `hourglass_flowing_sand` pending already means "my ball", which is why only these two are needed.)
 
-- `todo ls` is read-only and issues **one** `search.messages` call; priority is encoded as
-  negated `hasmy:` terms. Default is `hasmy:` (my reactions only), `--shared` uses `has:`.
+- **`todo ls` = anyone's reactions (`has:`), `mytodo ls` = only yours (`hasmy:`).** Two
+  commands rather than a flag, so the two lists can't be mistaken for each other. Both
+  print `From: @handle (Uxxxx) — Workspace` first: `hasmy:` resolves against whoever the
+  token is, so "my tasks" is only meaningful once you know who *my* is. `todo ls --mine`
+  is a shortcut to the narrow view; `--shared` is accepted but is now the default.
+- Both are read-only and issue **one** `search.messages` call; priority is encoded as
+  negated `has:`/`hasmy:` terms.
   `search.messages` returns no reaction data, so this filtering can only happen in the
   query. The search index lags slightly behind `reactions.add`.
 - `todo set` adds the target reaction **first**, then removes the stale ones one at a time.