Use proactively for structured or interactive Slack replies, and when asked to author or validate native Slack Block Kit JSON.
复制下面这句话,粘贴给 Claude Code、Codex、Cursor 等 AI 编程工具,它会读取安装说明并在你确认后完成安装。
请阅读 https://ai.atlankj.com/install/asset/gh-block-kit-48ec01e92cb1 ,按照其中的说明把「block-kit」安装到你(当前 AI 工具)中。执行前先告诉我将运行的命令和写入的位置,等我确认。
查看 AI 将读取的安装说明正在读取 GitHub 原文…
内容来自 GitHub 原始文件,由原作者维护。在 GitHub 查看
Make useful Slack replies feel native. When structure or one-click follow-up improves the outcome, send a rich message without waiting for the user to ask for Block Kit.
Use a presentation when the reply has at least one of these shapes:
Use plain text for short answers and casual conversation where structure adds no value.
For a reply in Slack, call the message tool with action: "send" and a portable presentation. The Slack plugin renders it as native Block Kit. Use the exact schema exposed by the current tool; supported block types can include text, context, divider, buttons, select, chart, and table.
callback actions for conversational choices and url for an external destination. Do not use generic command actions for Slack controls; Slack renders them as text fallback rather than clickable controls.message fallback that preserves the meaning without the rich layout.A control is complete only when its value is self-contained enough for the next agent turn to understand and act on. When an interaction returns, acknowledge the choice visibly and continue the requested workflow.
When the user is building a Slack app or explicitly requests raw Block Kit JSON, read the adapted official Block Kit guide in full. For common message, modal, and App Home layouts, also read the official patterns.
Follow the adapted guide's live-documentation and blocks.validate workflow for native JSON. Do not pass native Slack blocks to OpenClaw's presentation field; the plugin owns that conversion.