メニュー
Explain an outage to customers honestly, without leaking internals or blaming a person.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
SOC 職業分類に基づく
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/vstorm-co/agenticos --skill customer-facing-postmortemコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
SKILL.md を表示中
| name | Customer-facing postmortem |
| description | Explain an outage to customers honestly, without leaking internals or blaming a person. |
| category | content |
Customers forgive outages. They do not forgive discovering it was worse than they were told.
What happened, in their terms · when it started and ended, in UTC with a local note · who and what was affected, specifically · what caused it, honestly and without internal detail · what was done · what changes so it does not recur, with dates.
Say "we deployed a change that…" rather than "an issue occurred". Passive voice reads as evasion. Never name an individual — the failure is the system's, and a named engineer is a hostile act.
If data was lost, exposed or delayed, say so in the first paragraph. Burying it turns an outage into an incident of trust, and it always surfaces.
Only what is already scheduled with an owner. A postmortem promise that does not land is worse than not making it.
Overstate the fix, promise it cannot happen again, or publish before the timeline is confirmed.
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.