What problem does it solve? Slack messages often render poorly when agents output raw markdown: pipe tables appear as literal text, long messages get truncated mid-sentence, and file uploads fail against deprecated APIs. This Skill defines the exact formatting rules and delivery patterns for producing correctly rendered Slack messages. ## Core Features & Use Cases - Dual delivery modes: mrkdwn text for simple messages via send_message, and Block Kit JSON (header, section, table, alert, card, actions, markdown blocks) for rich layouts via chat.postMessage. - Gateway Block Kit pass-through: output a JSON payload with a top-level blocks array and the gateway auto-detects and renders it as native Slack blocks. - Long-content threading: split long reports into threaded messages of 2-3 section blocks each to avoid the 3,000-character mrkdwn truncation limit. - File uploads: the 3-step files.getUploadURLExternal flow with form-encoded bodies, replacing the deprecated files.upload API. - Use Case: An agent generating a daily project digest outputs Block Kit JSON with a header, status summary section, a markdown table of projects, and a context footer, which the gateway renders as a rich Slack message. ## Quick Start Format my project status report as a Slack Block Kit message with a header, summary section, and a table of active projects.