Formats and sends or schedules a Slack message to a channel, DM or thread through your existing Slack connector, after you approve the exact text, and reports what Slack returned.
--- name: slack-message-sender description: Drafts and sends a Slack message to a channel, direct message or thread, or schedules it for later, through a Slack connector or bot token the user already configured. It resolves the channel ID, formats Slack mrkdwn, shows the exact message for confirmation, and reports the message timestamp Slack returns. Without a connector it outputs the API request. Use when asked to post, announce, notify, reply in a thread or schedule a message in Slack. compatibility: Needs an existing Slack connector (for example an MCP server) or a bot or user token with the chat:write scope available to the agent's environment; the bot must be a member of the target channel. This skill does not create Slack apps or tokens. metadata: version: "1.0.0" category: "Communication" --- # Slack Message Sender Posts one well-formatted message where the user wants it, only after they approve the exact text. ## When to use / when not to - Use for: a channel announcement, a thread reply, a DM to one person, a message scheduled for a specific time. - Do not use for: messaging many users individually, impersonating someone, or reading private channels the token cannot access. ## Inputs to collect - Destination: channel name or ID, user for a DM, or the parent message for a thread reply (its `ts`). - Message text and any mentions (`<@U0123ABC>` for a user, `<!here>` only if the user asks). - Optional: send time and time zone for scheduling. ## Workflow 1. Find the tool: a Slack connector in the client, or a token already in the environment. Never ask the user to paste a token. 2. Resolve the destination to an ID (for example `C0123ABCD`) and show the channel name with it. If the bot is not in a private channel, ask the user to invite it; do not try workarounds. 3. Format with Slack mrkdwn: `*bold*`, `_italic_`, `` `code` ``, `<https://example.com|link text>`, `•` or `-` for lists. Keep the text well under 4,000 characters. 4. Show the confirmation block: ``` Post to #release-notes (C0123ABCD) now: --- *v2.8.0 is live* :rocket: - Faster search - <https://example.com/changelog|Full changelog> ``` 5. After an explicit yes: - Send now: `chat.postMessage` with `channel`, `text` and, for a reply, `thread_ts` set to the parent message's `ts`. - Schedule: `chat.scheduleMessage` with `channel`, `text` and `post_at` as a Unix timestamp computed from the user's time and IANA time zone. Slack accepts times up to 120 days ahead. 6. Report what Slack returned: `ok`, the message `ts` (or `scheduled_message_id`) and channel, or the error string such as `not_in_channel`, `channel_not_found`, `missing_scope`, `time_in_past` or `time_too_far`. ## Without a connector Output the method name and JSON body (and a `curl` example with an `Authorization: Bearer $SLACK_BOT_TOKEN` placeholder). State that nothing was posted. ## Safety and limits - Confirm every send and every scheduled message; never auto-retry a send that may have succeeded. - Do not use `@channel`, `@here` or user mentions unless asked. - Slack throttles posting to roughly one message per second per channel; space out multiple messages. ## Example Request: "Post in #release-notes that v2.8.0 is live with faster search and link the changelog at https://example.com/changelog." Result: `#release-notes` resolved to its ID, the formatted message shown, one `chat.postMessage` after confirmation, and the returned `ts` reported (for example `1762345678.000200`).
Generate a GitHub Actions (or other CI) pipeline from the repo's real scripts, with least-privilege permissions, caching, concurrency and a gated deploy.
Generate a compose.yaml for your app, database and cache with health-checked startup, named volumes and secrets in .env, validated with docker compose config.
Automate notifications and alerts
Illustrative input and expected result. This example is a verification guide, not a recorded model run.
Content reviewed .
A release manager wants a launch note in #release-notes; their agent client has a Slack connector whose bot is in that channel.
Post in #release-notes that v2.8.0 is live with faster search, and link the changelog at https://example.com/changelog.
The agent resolves #release-notes to its channel ID, shows the mrkdwn message ('*v2.8.0 is live*', a bullet for faster search, '<https://example.com/changelog|Full changelog>') and waits for approval. It then calls chat.postMessage once with channel and text and reports ok plus the returned ts. Asked to send it 'tomorrow at 9am New York time' instead, it computes post_at as a Unix timestamp from America/New_York and uses chat.scheduleMessage, reporting scheduled_message_id.AI Agent Skills are reusable workflow packages that extend your AI coding assistant with multi-step capabilities. Install Slack Message Sender by following these steps.
SKILL.md inside, in the location documented by your client. Do not assume every AI application reads the same directory.Requires an Agent Skills-compatible client; supported locations and activation vary by version. Read the SKILL.md setup guide. MCP connects tools and data and does not, by itself, install a skill.
Generate a GitHub Actions (or other CI) pipeline from the repo's real scripts, with least-privilege permissions, caching, concurrency and a gated deploy.
Generate a compose.yaml for your app, database and cache with health-checked startup, named volumes and secrets in .env, validated with docker compose config.
Automate notifications and alerts