Create or audit SLOs, SLIs, alert rules, incident response steps, escalation paths, postmortems, operational runbooks, and customer-impact communication.
SkillScore73Maintained
Automatic
◆DevOps & SRE pack
Last verified 8/24/2026
What it changes
Passed 16 of 22 test cases with the skill, and 3 of 22 without it.
Without skill14%
With skill73%
Checks it passed that the model alone missed
The output includes the root key `alerts:`.
The output contains the top-level key `slo:`.
The output contains the root field `runbook:`.
and 16 more in the full report
15 fixed1 passed either way4 still failing2 broke
Pass-rate lift
+59 pp
Tokens
-9%
Agent turns
0%
Response time
-17%
Model gemini-3.6-flashMeasured 8/24/2026v116 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 15 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 15
Prompt
We are launching a new e-commerce checkout API and need an operational response strategy before going live. Please generate a complete SLO and runbook specification for this checkout journey. The response should outline the target service details, service level objectives with error budget guidelines, alert triggers, dashboard and query guidelines, triage and mitigation runbook steps, escalation pathways, a postmortem template, and verification checks.
What was checked, without and with the skill
Checked
Without skill
With skill
The response formats the operational specification top-level structure using the key `service_or_journey:`.
Missed
Passed
The response prioritizes user-visible checkout success or latency metrics over internal host metrics such as CPU utilization.
Passed
Passed
The runbook section includes diagnostic checks designed specifically for the initial 5 minutes of an incident.
Missed
Passed
case-01 · gemini-3.6-flash · 8/24/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md57 linessingle file
Incident SLO Runbook
Purpose
Use this skill to connect observability to action. Metrics and logs are not enough; each critical user journey needs an SLO, alert, owner, response path, and post-incident learning loop.
SLO Design
Define:
User journey or system capability.
SLI: request success, latency, freshness, durability, or job completion.
SLO target and measurement window.
Error budget and burn-rate alerts.
Exclusions with rationale.
Dashboard and data source.
Owner and escalation path.
Avoid vanity metrics. Prefer user-visible success and latency over internal counters unless internal counters are the only reliable proxy.
Runbook Requirements
Each runbook should include:
Symptom and alert name.
Impacted users or systems.
First 5-minute checks.
Triage decision tree.
Mitigation steps with commands.
Rollback or failover path.
Escalation owner.
Customer/support communication note.
Postmortem trigger.
Commands must be safe to run or explicitly labeled destructive.