基于 SOC 职业分类
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/vstorm-co/agenticos --skill release-notes-writer命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
| name | Release notes writer |
| description | Turn merged changes into notes a user can act on, grouped by what they mean. |
| category | content |
The reader wants to know whether anything they use has changed. Sort for that.
Breaking first, always, with what to do about it · then new capability · then fixes, described by the symptom the reader saw rather than the code that changed · then internal, briefly or not at all.
"Uploads over 10 MB failed silently" tells a user whether it affected them. "Fixed a race in the ingestion worker" does not.
State what breaks, what to do, and by when. If a migration is needed, link it. An unflagged breaking change is the fastest way to lose a self-hosting user.
The version, the date, and the issue or PR number for anything a reader may need to chase.
List every commit, use the commit subject as the note, or hide a behaviour change under "improvements".
Work with messaging-channel bots — Telegram, Slack or Mattermost. Register a bot, route inbound messages through an agent, choose webhook vs polling, handle an @slug mention, or add a new channel adapter. Use when wiring chat into a messaging platform or debugging bot delivery, identity linking or "the bot answered as itself".
Change the agent spec — add or remove a field, rename one, tighten a rule, bump SPEC_VERSION, change publish-time validation, or touch YAML export/import. Use whenever editing app/agents/spec.py or anything that reads a stored spec. Every published agent and every client git repository holds a copy of this format, so a change that only works forwards breaks agents nobody touched.
Work with MCP servers — connect one, add an entry to the server catalog, debug "the agent cannot see my MCP tools" or a failing OAuth flow, or change how connections are probed, prefixed or filtered. Use when the ask involves an external SaaS tool (GitHub, Linear, Notion, Slack, Stripe, Postgres…) and before writing a capability that would just be an API client for one.