write-slo

Define service reliability targets with SLIs, SLOs, and error budgets.

Updated Apr 1, 2026

Search Tags:#monitoring #reliability #slo #error-budget #incident-management #service-level-objectives

Ready to run

npx skills add https://github.com/hpsgd/turtlestack --skill write-slo

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: write-slo
Source: https://github.com/hpsgd/turtlestack/tree/main/plugins/engineering/devops/skills/write-slo
Command: npx skills add https://github.com/hpsgd/turtlestack --skill write-slo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Defines and governs Service Level Objectives (SLOs) from user impact to turn reliability goals into explicit, actionable targets.

Core Features & Use Cases

Define SLIs for availability, latency, correctness, and freshness.
Create rolling-window SLO targets with formalized error budgets, burn-rate alerts, and policy enforcement.
Provide templates and checklists to generate complete SLO documentation for new and existing services.

Quick Start

Provide a production-ready SLO package for a service by following the steps in this guide.

Frequently Asked Questions about write-slo

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I define service level objectives for a production API?▼

To define service level objectives for a production API, you establish measurable service level indicators for availability and latency, then set concrete SLO targets with formalized error budgets and structured alerting policies.

What is an error budget and how does it govern incident management?▼

An error budget is the allowable threshold of unreliability derived from your SLO targets. It governs incident management by enforcing policies that pause feature deployments when burn-rate alerts indicate the budget is being exhausted.

How do I create SLIs for availability, latency, and correctness?▼

You create SLIs for availability, latency, and correctness by identifying measurable service level indicators from the user perspective, applying Google SRE-inspired guidance to generate rolling-window SLO targets and complete documentation.

Can I use Google SRE style SLOs for existing services across multiple teams?▼

Yes, you can apply Google SRE style SLOs to existing services across multiple teams. The process provides templates and checklists to define reliability targets, covering freshness and correctness with periodic review structures.

What is the best way to structure SLO documentation for new services?▼

The best way to structure SLO documentation for new services is to follow a quick start guide that generates a complete service profile, covering SLIs, concrete SLO targets, an enforceable error budget policy, and structured alerting.