Skip to content
cccskills
FreePublished on GitHub

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.

The English summary is being prepared. Showing the original description.

Run score Not tested

See how to install

Files included (2)

  • SKILL.md1.8 KB
  • agents/openai.yaml230 B

SKILL.md (original)

Review the instructions the agent will receive before you install.

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:

  1. User journey or system capability.
  2. SLI: request success, latency, freshness, durability, or job completion.
  3. SLO target and measurement window.
  4. Error budget and burn-rate alerts.
  5. Exclusions with rationale.
  6. Dashboard and data source.
  7. 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

  1. Declare severity and incident commander.
  2. Confirm impact from live evidence.
  3. Stabilize with the lowest-risk mitigation.
  4. Communicate status on a fixed cadence.
  5. Preserve evidence before cleanup.
  6. Write a blameless postmortem with action items and owners.

Output Shape

service_or_journey:
slo:
alerts:
dashboard_or_queries:
runbook:
escalation:
postmortem_template:
verification:

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Audit and organize AI coding-agent instructions, including AGENTS.md, CLAUDE.md, skills, and agent definitions. Use when the user asks to diagnose conflicting instructions, excessive approval pauses, broad skill triggers, duplicate guidance, or broken instruction references, or to clean up that instruction set. Ordinary code review, Markdown editing, or application debugging alone does not trigger this workflow. Inspection stays read-only; apply changes when authorized.

The English summary is being prepared. Showing the original description.

majiayu000/spellbook288Updated Oct 22, 2026

Generate or update repository-specific AGENTS.md instruction files from real repo evidence. Use when asked to create, design, scaffold, split, or improve root or scoped AGENTS.md files for Codex/Claude/agent workflows, especially when a repo needs directory-specific rules, validation commands, generated-file boundaries, or a short agent onboarding router.

The English summary is being prepared. Showing the original description.

majiayu000/spellbook288Updated Oct 22, 2026

REST/GraphQL/gRPC API design best practices. Use when designing APIs, defining contracts, handling versioning. Covers OpenAPI 3.2, GraphQL Federation, gRPC streaming.

The English summary is being prepared. Showing the original description.

majiayu000/spellbook288Updated Oct 22, 2026

Mobile app UI design expert for iOS and Android. Use when designing app interfaces, creating design systems, ensuring accessibility, or following platform guidelines. Covers Material Design 3, Human Interface Guidelines, color theory, typography, and 2025 trends.

The English summary is being prepared. Showing the original description.

majiayu000/spellbook288Updated Oct 22, 2026

End-to-end app feature inventory and user-story testing workflow with a canonical tracker. Use when the user asks to audit every feature, derive expected behavior from code, test user journeys, or explicitly fix and retest documented UX or logistical defects.

The English summary is being prepared. Showing the original description.

majiayu000/spellbook288Updated Oct 22, 2026

Design architecture foundations before implementation. Use when asked to design or refactor architecture, choose Rust/Go crate, package, module, runtime, workflow, or service boundaries, compare mature project architecture, prevent stacked one-off PRs, audit migration debt in existing repos, or produce a spec before coding.

The English summary is being prepared. Showing the original description.

majiayu000/spellbook288Updated Oct 22, 2026

See all skills by majiayu000

Report a problem with this skill