# Implement Reliable SLO Monitoring

Teams often collect metrics without clear reliability targets or decision rules. This skill converts service goals and telemetry into measurable SLOs, error budgets, alerts, and reviews.

## Install

```bash
npx skillstore add sickn33/observability-monitoring-slo-implement
```

## Metadata

- Status: approved
- Slug: sickn33-observability-monitoring-slo-implement
- Skillstore revision: r2
- Version status: missing
- Tree hash: 96ff0a86cd04fd429fc2263969682ca47d53505c8d7d2b8b8a5aede6ef573902
- Author: sickn33
- GitHub username: sickn33
- License: MIT
- Repository: https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/observability-monitoring-slo-implement
- Ref: 81e05e636292629114b76cbb3922fbe57672fc02
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: network, external\_commands
- Quality score: 78
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/sickn33-observability-monitoring-slo-implement
- Manifest: https://skillstore.pages.dev/api/skills/sickn33-observability-monitoring-slo-implement/manifest

## Capabilities

- Defines availability, latency, and quality SLIs from user journeys and service telemetry.
- Calculates SLO targets, compliance windows, and remaining error budgets.
- Designs Prometheus recording rules and multi-window burn-rate alerts.
- Outlines Grafana dashboards and recurring SLO reports for technical and business audiences.
- Creates error-budget policies that guide releases, reliability work, and incident responses.
- Provides review templates and governance practices for SLO adoption across teams.

## Use Cases

- Launch a Service SLO: Define measurable indicators, targets, and error budgets for a production service with existing telemetry.
- Add Actionable Reliability Alerts: Translate an approved SLO into burn-rate alerts and dashboard requirements that reduce noisy paging.
- Establish Reliability Governance: Create review routines and error-budget policies that connect reliability performance with roadmap decisions.

## Prompt Templates

### Draft a Basic SLO

```
Create an SLO for [service] using [availability or latency metric]. Explain the SLI, target, measurement window, exclusions, and required validation.
```

### Design SLIs from User Journeys

```
For [service], analyze these user journeys: [journeys]. Propose measurable SLIs using [telemetry], then rank them by user impact and implementation effort.
```

### Build Error-Budget Alerts

```
Using this approved SLO: [SLO], design multi-window burn-rate alerts. Include warning and critical conditions, response ownership, and alert validation steps.
```

### Create an SLO Operating Model

```
Design an SLO program for [organization]. Use [services], [business priorities], and [telemetry maturity]. Include governance, reporting, error-budget policy, adoption stages, and success measures.
```

## Limitations

- Requires accurate service telemetry, ownership details, and business priorities from the user.
- Does not deploy monitoring resources or query production systems by itself.
- Example thresholds and queries require validation against the target environment.
- Does not replace privacy, compliance, or safety review for monitored data.

## Best Practices

- Start with user journeys and business impact before selecting available metrics.
- Validate event definitions, exclusions, traffic volume, and historical performance before approving targets.
- Pair every alert with clear ownership, response guidance, and an error-budget policy.

## Anti Patterns

- Do not copy example targets without checking service history and stakeholder expectations.
- Do not treat infrastructure health metrics as direct evidence of successful user outcomes.
- Do not page on every SLO deviation without burn-rate windows and actionable response criteria.

## Security Audit

- Audited at: 2026-08-04T16:35:15.424\+00:00
- Summary: All eight static findings are false positives caused by placeholder URLs, Markdown formatting, safety guidance, CSS, and ordinary template syntax. No prompt injection, data exfiltration intent, concealed execution, or other semantic security issue was found.

## Stats

- Views: 101
- Downloads: 8
- Favorites: 0
- Popularity score: 0