Service Level Objective Validator

Validate SLO definitions against real metrics and generate structured reports.

6|Updated Oct 25, 2025
One-click install
npx skills add https://github.com/williamzujkowski/cognitive-toolworks --skill service-level-objective-validator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Service Level Objective Validator
Source: https://github.com/williamzujkowski/cognitive-toolworks/tree/main/skills/slo-validator
Command: npx skills add https://github.com/williamzujkowski/cognitive-toolworks --skill service-level-objective-validator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validates SLO definitions against real metrics to ensure reliability, aligning targets with observed performance and producing actionable outputs.

Core Features & Use Cases

  • Validate SLO definitions against actual metrics
  • Generate platform-specific alerting rules (Prometheus/CloudWatch/Datadog) and dashboards
  • Produce multi-window breach timelines, error-budget reports, and compliance artifacts

Quick Start

Validate a given SLO definition through the validator to obtain a validation report, alert rules, and budget status.

Frequently Asked Questions about Service Level Objective Validator

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

FAQPage Schema
How do I validate SLO definitions against real metrics?

SLO validation checks your service level objective definitions against actual observed metrics to ensure reliability targets align with real performance. It applies multi-window validation to produce a structured validation report and accurate error-budget calculations.

Can I generate Prometheus alerting rules from an SLO definition?

Yes, you can generate platform-specific alerting rules from an SLO definition. The validator outputs multi-window burn-rate alerts and Prometheus alert rules, alongside compatible configurations for CloudWatch and Datadog.

What is a multi-window burn-rate alert?

A multi-window burn-rate alert triggers when error budget consumption spikes across multiple time windows simultaneously. This mechanism prevents false positives while ensuring you detect SLO breaches quickly before the error budget is exhausted.

How do I calculate error budget burn rate for CI/CD pipelines?

Error budget burn rate is calculated by comparing observed metrics against your SLO targets within a CI/CD pipeline. The validator automates this computation, producing compliance artifacts and breach timelines for monitoring integration.

Does this SLO validator work with Datadog and CloudWatch?

Yes, the SLO validator works with Datadog and CloudWatch, alongside Prometheus. It generates platform-specific alert rules and dashboards tailored to each monitoring system, ensuring seamless integration across diverse observability stacks.

What is the best way to produce breach timelines for SLO compliance?

The best way to produce breach timelines for SLO compliance is to validate SLO definitions against real metrics using multi-window analysis. This generates detailed error-budget reports and structured compliance artifacts for your monitoring pipelines.