Incident Slo Runbook
Create or audit SLOs, SLIs, alert rules, incident response steps, escalation paths, postmortems, operational runbooks, and customer-impact communication. Use when defining production reliability, preparing launch readiness, responding to an outage, writing a runbook, tuning alerts, or closing the loop after an incident.
Install
$ agentstack add skill-majiayu000-spellbook-incident-slo-runbook ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-majiayu000-spellbook-incident-slo-runbook) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
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.
Incident Flow
- Declare severity and incident commander.
- Confirm impact from live evidence.
- Stabilize with the lowest-risk mitigation.
- Communicate status on a fixed cadence.
- Preserve evidence before cleanup.
- Write a blameless postmortem with action items and owners.
Output Shape
service_or_journey:
slo:
alerts:
dashboard_or_queries:
runbook:
escalation:
postmortem_template:
verification:Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: majiayu000
- Source: majiayu000/spellbook
- License: MIT
- Homepage: https://github.com/majiayu000/spellbook#quick-start
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.