tachyon-slack-notifylisted
Install: claude install-skill quantum-box/tachyon-skills
# Tachyon Slack Notify
## Overview
Use the installed `tachyon` CLI to verify real notification delivery through Tachyon's `/v1/chat/send` path. Prefer concrete execution evidence over code-only conclusions.
Since tachyon-api 0.92.112 (PLT-3042), a notification sent with a `thread_key` records its Slack thread, and replies in that thread can be collected via `GET /v1/chat/replies` or the `wait_slack_reply` MCP tool.
Since tachyon-api 0.92.114 and CLI 0.6.28 (PLT-3087), the loop closes in both directions: the same `thread_key` can be used to post an answer back into the thread, or to put an emoji reaction on the notification or on a specific reply. Without one of those, a human who replied has no way to tell the reply was read.
## Workflow
1. Confirm the CLI version:
```bash
tachyon --version
```
Expect `tachyon 0.5.3` or newer for nested `--tenant-id` support, and `0.6.28` or newer for `--thread-key` and `ops slack react`. If older, ask whether to update, or run the repo's release/update workflow if the user explicitly requested it.
2. List accessible operators when possible:
```bash
tachyon org operators list --json
```
If this fails after switching to a forbidden tenant, recover by switching back to a known accessible tenant.
3. Test the notification with explicit tenant selection:
```bash
tachyon ops slack send --tenant-id <tenant_id_or_alias> --text "Codex test notification from tachyon CLI" --json
```
`ops slack` is an alias for `ops notify`. Both should cal