JPeetz/agent-skills / skills/devops-infrastructure/observability-engineering
observability-engineering
VerifiedUse this skill when setting up monitoring, adding observability, or instrumenting with OpenTelemetry — also when creating SLOs and error budgets, designing alerts, aggregating logs, tracing distributed requests, or building Grafana/Prometheus dashboards. Implements vendor-neutral telemetry with structured incident response and alert-fatigue control.
| File | Kind | Size |
|---|---|---|
| CHANGELOG.md | markdown | 2.8 KB |
| LICENSE | other | 1.0 KB |
| SKILL.md | skill md | 37.1 KB |
| evals/evals.json | config | 4.0 KB |
| references/incident-response.md | markdown | 22.8 KB |
| references/otel-instrumentation-guide.md | markdown | 19.3 KB |
| references/sli-slo-cookbook.md | markdown | 16.2 KB |
| scripts/generate-slo-dashboard.shexecutable | script | 14.6 KB |
| scripts/validate-observability-stack.shexecutable | script | 12.5 KB |
CHANGELOG.md
View on GitHub# Changelog
All notable changes to the observability-engineering skill.
## Unreleased
### Changed
- Description rewritten to be trigger-first ("Use this skill when ...") and under 1024 chars per the agentskills.io spec.
## v1.0.0 — 2026-06-18
### Initial Release
Synthesized from:
- **observability-engineer** (mk-knight23/AGENTS-COLLECTION) — monitoring, metrics, and incident response patterns
- **OpenTelemetry skill** (dash0hq/agent-skills) — OpenTelemetry SDK instrumentation and context propagation
- **SRE best practices** — Google SRE book, incident management frameworks, postmortem templates
### What's Included
**Core Capabilities:**
- OpenTelemetry instrumentation across 6+ languages (Node.js, Python, Go, Java, .NET, Ruby)
- Auto-instrumentation and manual span creation patterns
- Context propagation (W3C TraceContext) across HTTP, gRPC, and messaging
- Prometheus/Grafana monitoring with RED/USE methodology
- Structured JSON logging with trace correlation (Loki/ELK)
- Distributed tracing with head-based and tail-based sampling strategies
- Full semantic conventions for HTTP, database, and messaging spans
- SLI/SLO/SLA framework with error budget calculation
- Multi-window burn rate alerting
- Alert design principles and Alertmanager routing configuration
- Incident response playbook with severity classification and communication templates
- Postmortem structure and timeline reconstruction
- Observability-as-Code patterns (Terraform/Pulumi)
- GitOps workflow for dashboards and alert configuration
- Cost optimization guidance (cardinality management, sampling, retention policies)
**Material Improvements Over Sources:**
- Unified previously separate concerns (monitoring, logging, tracing, incident response) into one cohesive skill
- Added SLI/SLO frameworks with error budget mathematics not present in source skills
- Included observability-as-code patterns for GitOps workflows
- Added incident postmortem templates with timeline reconstruction
- Provided cost optimization guidance (cardinality management, sampling calculator)
- Added production readiness and debugging checklists
- Multi-language coverage (6+ languages vs typical 2-3 in source skills)
**Deliverables:**
- `SKILL.md` — 11-section comprehensive observability skill
- `references/otel-instrumentation-guide.md` — Multi-language OpenTelemetry patterns deep-dive
- `references/sli-slo-cookbook.md` — SLI definition patterns, error budget formulas, burn rate alert configs
- `references/incident-response.md` — Incident classification, IC role, templates, postmortem structure
- `scripts/validate-observability-stack.sh` — OTel Collector config, Prometheus rules, Grafana dashboard validation
- `scripts/generate-slo-dashboard.sh` — Automated Grafana SLO dashboard JSON generation from SLI definitions
- `evals/eval_cases.json` — 5 trigger cases + 2 near-miss negatives
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation). | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK). | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |