block-kit
Use proactively for structured or interactive Slack replies, and when asked to author or validate native Slack Block Kit JSON.
- License 许可
- MIT
- 最近更新
- 2026-11-11
- Stars
- ★ 39w
- Forks
- 8.3w
01 前言 Front Matter
- name
- block-kit
- metadata
- { "openclaw": { "emoji": "?", "requires": { "config": [ "channels.slack" ] } } }
- description
- Use proactively for structured or interactive Slack replies, and when asked to author or validate native Slack Block Kit JSON.
- allowed-tools
- [ "message" ]
02 资源文件 2
- 参考文档references/official-block-kit.md15.3 KB
- 参考文档references/official-common-patterns.md11.1 KB
03 SKILL.md 正文
Slack Block Kit
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.
Choose the surface
Use a presentation when the reply has at least one of these shapes:
- a decision, confirmation, or next action that belongs on buttons or a select
- a status, comparison, report, or plan that scans better as titled sections, a table, or a chart
- important context that should be visually separated from the primary result
Use plain text for short answers and casual conversation where structure adds no value.
Send the result
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.
- Put the outcome first. Keep titles, labels, and context concise.
- Give interactive controls real follow-up semantics. Use typed
callbackactions for conversational choices andurlfor an external destination. Do not use genericcommandactions for Slack controls; Slack renders them as text fallback rather than clickable controls. - Include a useful
messagefallback that preserves the meaning without the rich layout. - After the visible send succeeds, do not repeat the same content in the final response.
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.
Native Block Kit authoring
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.
04 同仓库更多 Skills
lobster
暂无简介
xurl
xurl CLI for authenticated X posts, replies, reads/search, DMs, media upload, followers, auth status, or raw v2 API calls.
weather
Current weather and forecasts with web_fetch, falling back to wttr.in curl for locations, rain, temperature, travel planning.
visualize
Create inline visuals for code and explanations, or author persistent OpenClaw dashboard widgets with show_widget.
trello
Manage Trello boards, lists, and cards via the Trello REST API.
tmux
Control tmux sessions/panes for interactive CLIs: list, capture output, send keys, paste text, monitor prompts.