slack-saylisted

Post a one-line progress update into the Slack thread or channel a run started from. Use exactly at stage boundaries of long-running work — e.g. finishing discovery, starting implementation, opening a PR, entering a fix loop — so a human watching Slack can see the run is alive and where it is. Do NOT use for chatter, for every small step, or as a substitute for the agent's final response — it is a best-effort ping, not the answer. Triggers on: multi-step commands/skills that run long enough a human might wonder if they stalled (dev-task, patch, review, plan-session, deploy), or when the user mentions "post progress to Slack", "slack-say", or "progress ping". Invokes `scripts/slack-say.ts` via `bun run` — never throws, never fails the caller.
app-vitals/shipwright · ★ 14 · AI & Automation · score 75

Install: claude install-skill app-vitals/shipwright

# slack-say — Skill Post a single-line progress message into the Slack thread (or channel) a run started from. It exists so a human watching a long-running command can see it is still moving without waiting for the final response. --- ## When to use this - **One line at each stage boundary** of long-running work — e.g. "starting implementation", "opening PR #123", "CI failed, retrying fix (2/6)". A stage boundary is a transition between the major phases of a command/skill (discovery → build → review → ship), not every individual tool call. - **Never for chatter.** Do not narrate routine tool calls, intermediate reasoning, or anything that isn't a meaningful phase transition. - **Never as a replacement for the final response.** The calling command/skill still owes the user its normal end-of-run summary — `slack-say` only pings interim progress. --- ## Invocation ```bash bun run "${CLAUDE_PLUGIN_ROOT}/scripts/slack-say.ts" [--channel C] [--thread T] "text" ``` - `text` — every non-flag argument is joined with a space, so an unquoted multi-word message still works. - `--channel` — overrides the resolved channel (see resolution order below). - `--thread` — overrides the resolved thread timestamp. - There is no `--token` flag, on purpose — the Slack bot token is env-only. --- ## Resolution order | Value | Source (highest priority first) | |---|---| | Channel | `--channel` flag → `SLACK_CHANNEL_ID` env var | | Thread | `--thread` flag → `SLACK_THREAD_TS` env