メニュー
Generate a blameless incident postmortem from the current or recent SRE Agent investigation. Use after an incident is resolved, when asked for a postmortem, RCA report, or lessons learned document.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/Azure/sre-agent-plugins --skill incident-postmortem-generatorコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
Assess security, reliability, and cost posture of Azure OpenAI and AI Foundry deployments. Detects anti-patterns like API keys instead of Managed Identity, public endpoints, disabled content filtering, deprecated models, over-provisioned PTU, missing AI Gateway, and single-region deployment.
Assess Azure resource capacity, quota utilization, and growth trends to prevent outages from resource exhaustion. Use when asked about capacity, quotas, scaling readiness, load testing prep, or growth projections.
Audit Azure environment for compliance and governance posture. Checks Azure Policy, RBAC, tagging, resource locks, naming conventions, and regulatory alignment. Use when asked about compliance, governance, audit readiness, or policy violations.
SKILL.md を表示中
| name | incident_postmortem_generator |
| description | Generate a blameless incident postmortem from the current or recent SRE Agent investigation. Use after an incident is resolved, when asked for a postmortem, RCA report, or lessons learned document. |
Automatically generate a structured, blameless postmortem document from the context of a resolved incident investigation.
From the current conversation and agent memory, extract:
| Metric | Description |
|---|---|
| Time to detect (TTD) | Issue start to alert firing |
| Time to acknowledge (TTA) | Alert to human engagement |
| Time to mitigate (TTM) | Engagement to mitigation |
| Time to resolve (TTR) | Total duration |
Apply the 5 Whys technique to the root cause to identify systemic issues.
For each finding, create a SMART action item with owner, priority, and due date. Categories: prevent recurrence, improve detection, improve response, improve resilience.
Generate the full document with: executive summary, impact, timeline, root cause, Five Whys, detection assessment, what went well, what could be improved, action items, and lessons learned.
| Field | Value |
|---|---|
| Incident Date | 2026-07-10 |
| Severity | Sev-2 |
| Duration | 1h 23m |
Summary: payment-service returned HTTP 500 errors for 1h 23m due to OOM-killed pod. Root cause: memory leak in connection pool from release v2.14.0. Impact: ~340 failed transactions, 120 customers.
| Metric | Value | Target | Status |
|---|---|---|---|
| TTD | 6m | <5m | ⚠️ |
| TTA | 4m | <15m | ✅ |
| TTM | 28m | <30m | ✅ |
| TTR | 1h 23m | <2h | ✅ |
