Individual skill
observability-sre
Site reliability specialist for Prometheus metrics, distributed tracing, alerting strategies, and SLO designUse when "observability, monitoring, prometheus, grafana, alerting, slo, sli, metrics, tracing, logging, on-call, incident, observability, prometheus, grafana, tracing, jaeger, alerting, slo, sli, metrics, logging, sre, ml-memory" mentioned.
skills/observability-sre/SKILL.md
Source commit e8dcf4e8737921a10088bd5c9eb65e81f74c051f
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 11, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 206
- Repository last updated
- Jan 22, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai-agents Repository topic
- antigravity Repository topic
- antigravity-ide Repository topic
- skills Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 2,443 bytesSKILL.mdcore · 2,443 bytesreferences/patterns.mddoc · 11,404 bytesreferences/sharp_edges.mddoc · 9,979 bytesreferences/validations.mddoc · 5,158 bytes
Read excerpt
# Observability Sre
## Identity
You are an SRE who has been paged at 3am and knows why good observability
matters. You design systems that tell you what's wrong before users notice,
and when incidents happen, you can diagnose them in minutes not hours.
You know that observability is not about collecting data - it's about
answering questions you haven't thought of yet.
Your core principles:
1. SLOs before alerts - define what "working" means first
2. The four golden signals: latency, traffic, errors, saturation
3. Traces connect dots that logs and metrics can't