Skills observability-monitoring-slo-implement
๐Ÿ“ฆ

observability-monitoring-slo-implement

Content revision r2 Safe ๐ŸŒ Network accessโš™๏ธ External commands

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.

Supports: Claude Codex Code(CC)
๐Ÿฅ‰ 78 Bronze

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request
Review the Skillstore skill "observability-monitoring-slo-implement" from https://skillstore.io/skills/sickn33-observability-monitoring-slo-implement.md and its manifest at https://skillstore.io/api/skills/sickn33-observability-monitoring-slo-implement/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Test it

Using "observability-monitoring-slo-implement". Design an availability SLO for a customer checkout API with request metrics and a 30-day window.

Expected outcome:

  • Indicator: successful eligible checkout requests divided by all eligible checkout requests.
  • Target: 99.9 percent over a rolling 30-day window, pending baseline validation.
  • Error budget: 0.1 percent of eligible requests may fail during the window.
  • Validation: confirm status classifications, synthetic traffic exclusions, and low-volume behavior with service owners.

Using "observability-monitoring-slo-implement". Recommend alerts for an approved 99.9 percent availability SLO.

Expected outcome:

  • Critical alert: fast burn across short and long windows, routed to the service owner.
  • Warning alert: sustained slower burn, routed for investigation before the budget is exhausted.
  • Each alert includes current burn rate, remaining budget, dashboard link, runbook link, and validation status.

Security Audit

Safe
v5 โ€ข 8/4/2026 Open versioned report

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.

2
Files scanned
1,130
Lines analyzed
0
Review items
0
False positives ignored

Risk Factors

No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.
Audited by: codex View Audit History โ†’
Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report
Security Assessment

Copy report link

https://skillstore.io/skills/sickn33-observability-monitoring-slo-implement/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/sickn33-observability-monitoring-slo-implement/security.svg)](https://skillstore.io/skills/sickn33-observability-monitoring-slo-implement?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/sickn33-observability-monitoring-slo-implement?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-observability-monitoring-slo-implement/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/sickn33-observability-monitoring-slo-implement.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>
Academic citations (APA ยท BibTeX ยท CFF)

APA citation

sickn33. (2026). observability-monitoring-slo-implement security audit report (audit version 5) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-observability-monitoring-slo-implement/audits/5

BibTeX citation

@techreport{sickn33-sickn33-observability-monitoring-slo-implement-2026, author = {sickn33}, title = {observability-monitoring-slo-implement security audit report (audit version 5)}, institution = {Skillstore}, year = {2026}, number = {5}, url = {https://skillstore.io/skills/sickn33-observability-monitoring-slo-implement/audits/5}, note = {Author version unspecified} }

CITATION.cff

cff-version: 1.2.0 message: "If you use this Skill, cite its author and this versioned security audit report." title: "observability-monitoring-slo-implement security audit report (audit version 5)" version: "unspecified" type: report authors: - name: "sickn33" date-released: "2026-08-04" url: "https://skillstore.io/skills/sickn33-observability-monitoring-slo-implement/audits/5" identifiers: - type: other value: "skillstore:sickn33-observability-monitoring-slo-implement:audit:5" description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: High
55
Architecture
85
Maintainability
87
Content
69
Community
83
Spec Compliance

What You Can Build

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.

Try These Prompts

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.

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.

Avoid

  • 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.

Frequently Asked Questions

What information should I provide?
Provide the service purpose, key user journeys, available telemetry, historical performance, business impact, ownership, and current incident practices.
Can this skill choose an SLO target automatically?
It can propose a target, but service owners and stakeholders must validate it against history, user expectations, and business risk.
Does this skill deploy Prometheus or Grafana resources?
No. It designs rules, queries, dashboards, and validation steps that engineers must adapt and deploy in their environment.
How does an error budget help delivery decisions?
It quantifies tolerated unreliability and supports agreed decisions about releases, incident work, and reliability investment.
Can it support latency and quality objectives?
Yes. The playbook covers availability, latency thresholds, and quality indicators when suitable telemetry and user-impact definitions exist.
How should sensitive telemetry be handled?
Use aggregated, access-controlled metrics and exclude personal or sensitive data. Complete required privacy and compliance reviews before deployment.

Developer Details

Author

sickn33

License

MIT

Skillstore revision

r2

Version notice

The author did not declare a version.

Ref

81e05e636292629114b76cbb3922fbe57672fc02

Maintenance freshness

8/5/2026

Usage

6 downloads ยท 101 views

File structure

๐Ÿ“ resources/

๐Ÿ“„ implementation-playbook.md

๐Ÿ“„ SKILL.md

More from sickn33

View all
View all