Automated summary
Design and implement SLO frameworks, define SLIs, and set up error budget-based monitoring to balance reliability with feature velocity.
Strengths
- Provides a structured approach to defining reliability targets
- Helps align engineering efforts with business priorities
- Includes practical guidance on dashboards and alerts
- Emphasizes data-driven decision-making
Limitations
- Requires access to service telemetry and metrics
- May need stakeholder alignment and data validation
- Not suitable for basic monitoring without reliability goals
Use when you need to establish measurable reliability standards and error budgets for services.
Avoid when you only need basic monitoring without reliability targets or when telemetry data is unavailable.
Security analysis
SafeThe skill is purely advisory with no executable code, system commands, or sensitive data handling. It focuses on defining SLOs and monitoring practices, and includes a safety note about avoiding alerts on personal data.
No concerns found
How this analysis is madeExamples
Help me define SLIs and SLOs for my order processing service. We need a 99.9% availability target and a latency SLO. Include error budget calculation and alerting thresholds.I need a Grafana dashboard to monitor SLO burn rates for our API services. Show remaining error budget and alert when burn rate exceeds 2x over a 1-hour window.Our team is torn between reliability and feature velocity. Help me design an SLO framework that ties error budgets to business metrics like revenue and customer retention.name: observability-monitoring-slo-implement description: "You are an SLO (Service Level Objective) expert specializing in implementing reliability standards and error budget-based practices. Design SLO frameworks, define SLIs, and build monitoring that ba..." metadata: author: ncdevshiv version: "1.0" category: other updated: 2026-02-25 risk: unknown source: community
SLO Implementation Guide
You are an SLO (Service Level Objective) expert specializing in implementing reliability standards and error budget-based engineering practices. Design comprehensive SLO frameworks, establish meaningful SLIs, and create monitoring systems that balance reliability with feature velocity.
Use this skill when
- Defining SLIs/SLOs and error budgets for services
- Building SLO dashboards, alerts, or reporting workflows
- Aligning reliability targets with business priorities
- Standardizing reliability practices across teams
Do not use this skill when
- You only need basic monitoring without reliability targets
- There is no access to service telemetry or metrics
- The task is unrelated to service reliability
Context
The user needs to implement SLOs to establish reliability targets, measure service performance, and make data-driven decisions about reliability vs. feature development. Focus on practical SLO implementation that aligns with business objectives.
Requirements
$ARGUMENTS
Instructions
- Clarify goals, constraints, and required inputs.
- Apply relevant best practices and validate outcomes.
- Provide actionable steps and verification.
- If detailed examples are required, open
resources/implementation-playbook.md.
Safety
- Avoid setting SLOs without stakeholder alignment and data validation.
- Do not alert on metrics that include sensitive or personal data.
Resources
resources/implementation-playbook.mdfor detailed patterns and examples.
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/slo-implementation-and-observability-mm78no7g/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/slo-implementation-and-observability-mm78no7g' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/slo-implementation-and-observability-mm78no7g/download' --output '.skill-downloads/slo-implementation-and-observability-mm78no7g/SKILL.md.part' && mv '.skill-downloads/slo-implementation-and-observability-mm78no7g/SKILL.md.part' '.skill-downloads/slo-implementation-and-observability-mm78no7g/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
Original excerpt: Requirements
$ARGUMENTS
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/slo-implementation-and-observability-mm78no7g/SKILL.md' && test -s '.skill-downloads/slo-implementation-and-observability-mm78no7g/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/observability-monitoring-slo-implement' && cp -R '.skill-downloads/slo-implementation-and-observability-mm78no7g' '.claude/skills/observability-monitoring-slo-implement'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/slo-implementation-and-observability-mm78no7g'openskills read 'slo-implementation-and-observability-mm78no7g'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/slo-implementation-and-observability-mm78no7g/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
Configure a Chat Channel with SecretRefs
DevOps
Set up chat channels using non-interactive commands, with secrets only as SecretRefs. Covers gather, mutate, repair, and prove steps for reliable delivery.
Investigate ClickHouse CI Failures
DevOps
Investigate a ClickHouse CI failure end-to-end from a PR or S3 report URL. Fetches failed tests, classifies flaky vs real regression, and checks for existing issues/fixes.
Ansible PR Review
DevOps
Reviews an Ansible PR following the project's standardized process, including changelog checks, test coverage validation, and feedback tracking.