slack-api

name

slack-api

description

Read Slack from the agent — thread replies, channel history, user lookup and mention resolution, and opening a DM. Channel and thread resolve env-first ($SLACK_CHANNEL_ID / $SLACK_THREAD_TS) with a --channel fallback, so you can usually omit them. TRIGGER when asked to fetch a thread or channel history, find someone's user id, resolve a mention, or DM someone. This skill does NOT post, edit, delete or react — your answer is just the text you write, and progress goes through the slack-status skill.

slack-api — Slack Web API toolbox

Reading Slack, and nothing else. Built on the same @slack/web-api WebClient (from $SLACK_BOT_TOKEN) the chat surface uses.

This skill used to write. It could post, edit, delete, react, post ephemerals and set titles, and every one of those bypassed the surface: no update rationing, no markdown block, no one-answer-per-turn rule. The SKILL.md carried a warning asking the agent not to use chat.postMessage for its reply because it produced a duplicate message — a hazard documented rather than removed. Those commands are gone.

This skill does not write at all. Progress goes through slack-status, questions through slack-questions or slack-ask, pictures through slack-chart and slack-image, and a new thread through spawn-thread. Your answer itself is posted by the surface when the turn ends.

CLI usage

bun features/slack/skills/slack-api/scripts/slack.ts <command> [--flags ...]

On success it prints the Slack API response (or aggregated data) as pretty JSON and exits 0. On failure it prints to stderr and exits 1.