菜单
Use when asked to summarize the current Kit release against the previous release and publish a customer-facing announcement to Slack, including requests such as "announce the latest release", "post release notes", or "share what changed since the last version".
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/speakeasy-api/kit --skill announce-kit-release命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
| name | announce-kit-release |
| description | Use when asked to summarize the current Kit release against the previous release and publish a customer-facing announcement to Slack, including requests such as "announce the latest release", "post release notes", or "share what changed since the last version". |
Confirm the current checkout, latest release tag, and immediately preceding release tag. Fail if the current revision is not the release being announced or if either comparison tag is missing.
Inspect the commit subjects, changed files, user documentation, and release-range diff between the two tags. Use these only as evidence; do not put raw commits, hashes, file lists, diff statistics, or implementation details in the announcement.
Translate the changes into concise customer outcomes. Group related work into a short list, lead with the release version, and mention compatibility or performance fixes only when they affect users. Do not use emojis.
Include mise installation instructions in fenced shell code blocks. The opening fence, command text, and closing fence must be on separate lines. Never put a command on the opening-fence line or put the closing fence after a command. Use this exact payload shape:
```shell
mise use -g github:speakeasy-api/kit
kit --version
```
To pin this version:
```shell
mise use -g github:speakeasy-api/kit@<version-without-v-prefix>
```
Search Slack for the requested channel by name and resolve its current channel ID. Never hard-code a Slack channel ID.
Before sending or drafting, inspect the exact Slack payload. Every opening ```shell fence must end immediately with a newline, every closing ``` fence must be on its own line, and prose or links must appear only after a closing fence. Reject payloads such as or .
```shell commandcommand``` If the user explicitly asked to post, send the announcement directly. Otherwise, create a draft for review. Do not post to an approximate channel name; fail and ask for clarification if the exact channel cannot be found.
Read the sent message back from Slack and verify that the install commands did not absorb later prose or links. If it is malformed, replace or delete it when Slack tools allow that; otherwise post one corrected copy and report that the malformed message requires manual deletion.
Return the Slack message or draft link.
Kit <version> is availableWhat's new with three to six outcome-focused bullets.Install or upgrade with mise with the install, verification, and pinned-version commands.