Skip to content
Skills Library
DevOps & cloud · Building & coding

observability-engineer

/observability-engineer

Use when setting up observability systems including monitoring, logging, metrics, tracing, or alerting. Invoke for dashboards, Prometheus/Grafana, OpenTelemetry, load testing, profiling, capacity planning, SLO-based alerting.

Repository
srepowers ↗
Licence
MIT
Last repository change
09.11.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
12
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 09.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Use when setting up observability systems including monitoring, logging, metrics, tracing, or alerting. Invoke for dashboards, Prometheus/Grafana, OpenTelemetry, load testing, profiling, capacity planning, SLO-based alerting.

Original author description

Use when setting up observability systems including monitoring, logging, metrics, tracing, or alerting. Invoke for dashboards, Prometheus/Grafana, OpenTelemetry, load testing, profiling, capacity planning, SLO-based alerting.

How it works

  1. When to Use This Skill
  2. Core Workflow
  3. Reference Guide
  4. Red Flags — Stop and Verify
  5. SRE Principles
  6. Knowledge Reference
Original SKILL.md headings · 56 lines, 343 words
SKILL.md preview
---
name: observability-engineer
description: Use when setting up observability systems including monitoring, logging, metrics, tracing, or alerting. Invoke for dashboards, Prometheus/Grafana, OpenTelemetry, load testing, profiling, capacity planning, SLO-based alerting.
license: MIT
---

# Observability Engineer

## When to Use This Skill

- Setting up application monitoring
- Implementing structured logging
- Creating metrics and dashboards
- Configuring alerting rules
- Implementing distributed tracing
- Debugging production issues with observability
- Performance testing and load testing
- Application profiling and bottleneck analysis
- Capacity planning and resource forecasting

## Core Workflow

1. **Assess** - Identify what needs monitoring
2. **Instrument** - Add logging, metrics, traces
3. **Collect** - Set up aggregation and storage
4. **Visualize** - Create dashboards
5. **Alert** - Configure meaningful alerts

## Reference Guide

Load detailed guidance based on context:

| Topic | Reference | Load When |
|-------|-----------|-----------|
| Logging | `references/structured-logging.md` | Pino, JSON logging |
| Metrics | `references/prometheus-metrics.md` | Counter, Histogram, Gauge |
| Tracing | `references/opentelemetry.md` | OpenTelemetry, spans |
| Alerting | `references/alerting-rules.md` | Prometheus alerts |
| Dashboards | `references/dashboards.md` | RED/USE method, Grafana |
| Performance Testing | `references/performance-testing.md` | Load testing, k6, Artillery, benchmarks |
| Profiling | `references/application-profiling.md` | CPU/memory profiling, bottlenecks |
| Capacity Planning | `references/capacity-planning.md` | Scaling, forecasting, budgets |

## Red Flags — Stop and Verify

| Thought | Reality |
|---------|--------|
| "Logging is enough" | Logs + metrics + traces. All three are needed for diagnosis. |
| "We'll add monitoring later" | Observability is foundational. Deploy monitoring with the service. |
| "Alert on everything" | Alert on symptoms, not causes. Too many alerts cause fatigue. |
| "Custom metrics aren't needed" | RED metrics (Rate, Errors, Duration) minimum for every service. |
| "Traces are too complex to set up" | Distributed tracing finds issues logs and metrics can't. |
| "Dashboards can wait" | Create dashboards at deploy time. You'll need them at 3am. |

## SRE Principles

Apply the [SRE Principles](../../references/sre-principles.md) (Safety First, Structured Output, Evidence-Driven, Audit-Ready, Communication) using domain-appropriate tools and commands.

## Knowledge Reference

Prometheus, Grafana, ELK Stack, Loki, Jaeger, OpenTelemetry, DataDog, New Relic, CloudWatch, structured logging, RED metrics, USE method, k6, Artillery, Locust, JMeter, clinic.js, pprof, py-spy, async-profiler, capacity planning
Files in this package (12)
  • CREDITS.md 1 KB
  • LICENSE 1 KB
  • README.md 2 KB
  • SKILL.md 3 KB
  • references/alerting-rules.md 3 KB
  • references/application-profiling.md 6 KB
  • references/capacity-planning.md 8 KB
  • references/dashboards.md 4 KB
  • references/opentelemetry.md 3 KB
  • references/performance-testing.md 6 KB
  • references/prometheus-metrics.md 3 KB
  • references/structured-logging.md 3 KB

Versions

RepositoryScoreLicence
This page · yg-codes/srepowers90MIT
rmyndharis/antigravity-skills100MIT

Database snapshot: 13.11.2026 · package version 93ddf7c22f79 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 1 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100agent-observability-engineer
    Specialist subagent: OpenTelemetry, Prometheus, Grafana, distributed tracing, SLO design, and alerting specialist. Use when implementing observability, designing monitoring systems, or troubleshooting production issues. Trigger phrases: observability, monitoring, tracing,…
  • 100ops
    Post-deploy observability for production services — structured logging, RED metrics + Prometheus, Grafana dashboards, SLO-based alerting. Use when setting up monitoring or instrumenting a live service. Trigger on "add logging", "metrics", "dashboard", "alerting",…
  • 100monitoring-expert
    Configures monitoring systems, implements structured logging pipelines, creates Prometheus/Grafana dashboards, defines alerting rules, and instruments distributed tracing. Implements Prometheus/Grafana stacks, conducts load testing, performs application profiling, and plans…
  • 100monitoring-expert
    Configures monitoring systems, implements structured logging pipelines, creates Prometheus/Grafana dashboards, defines alerting rules, and instruments distributed tracing. Implements Prometheus/Grafana stacks, conducts load testing, performs application profiling, and plans…
  • 91observability-engineering
    Use 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…
  • 95observability
    Use when adding structured logging, instrumenting Prometheus metrics, wiring up distributed tracing with OpenTelemetry, writing alerting rules, defining SLOs and error budgets, or building a Grafana golden-signals dashboard.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.