Design or troubleshoot telemetry, SLOs, and incident diagnostics. Route to the relevant signal, system boundary, or vendor guide.
60%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./skills/oma-observability/SKILL.mdRoute, design, tune, and review observability work across MELT+P signals, layers, boundaries, vendor categories, transport choices, meta-observability, and incident forensics.
Load resources conditionally: start with the execution protocol and one intent guide. Read only relevant matrix rows, then add a boundary, signal, or transport section when evidence requires it. The reference list is an index, not a preload list.
resources/| Action | SSL primitive | Evidence |
|---|---|---|
| Classify observability intent | SELECT | Intent rules |
| Read telemetry/config evidence | READ | OTel/vendor configs, dashboards, samples |
| Route vendor/category | SELECT | Vendor categories |
| Infer coverage gaps | INFER | Matrix and signal/boundary mapping |
| Validate meta-observability | VALIDATE | Clock, cardinality, retention, health |
| Write guidance/config | WRITE | OaC/config/docs when requested |
| Notify result | NOTIFY | Routed recommendation |
1. Classify intent: setup, migrate, investigate, alert, trace, tune, or route.
2. Select layer/boundary/signal coverage from `resources/matrix.md`.
3. Load the specific vendor, transport, incident, or signal guide before producing guidance.When CNCF/vendor status is load-bearing, verify live state at https://landscape.cncf.io.
| Scope | Resource target |
|---|---|
CODEBASE | Observability config, dashboards, alert rules, instrumentation |
LOCAL_FS | Resource guides and generated docs |
NETWORK | Vendor/CNCF status and telemetry backends when checked |
USER_DATA | Incident symptoms, logs, metrics, traces, profiles |
resources/vendor-categories.md only when category selection or vendor delegation is needed.resources/boundaries/cross-application.md where required.The coverage matrix has four layers (L3, L4, mesh, L7), four boundaries (multi-tenant, cross-application, SLO, release), and seven signals (metrics, logs, traces, profiles, cost, audit, privacy). Read matching rows in resources/matrix.md; N/A cells do not require implementation.
| Intent | Primary target | Fallback |
|---|---|---|
setup | resources/vendor-categories.md → vendor-owned skill | Generic OTel semconv in resources/standards.md |
migrate | Current upstream migration docs + resources/vendor-categories.md log-pipeline section | OTel Collector bridge config |
investigate | resources/incident-forensics.md (MRA + 6-dim localization) | resources/signals/traces.md + resources/signals/logs.md |
alert | resources/boundaries/slo.md (burn-rate alert rules) | resources/observability-as-code.md |
trace | resources/boundaries/cross-application.md (propagator matrix) | resources/layers/mesh.md (zero-code auto-instrumentation) |
tune | resources/transport/ (4 files: UDP/MTU, OTLP, topology, sampling) | resources/meta-observability.md (cardinality guardrails) |
route | resources/boundaries/multi-tenant.md + resources/transport/collector-topology.md | resources/boundaries/cross-application.md (data residency) |
For example: /oma-observability --investigate "5xx spike in checkout".
Other skills pass the intent, system boundary, and evidence; the result returns guidance, checks, and any vendor handoff.
Read resources/execution-protocol.md first. Use the selected route above, then only relevant checklist sections before delivery. Load resources/examples.md for an unfamiliar output shape and resources/anti-patterns.md only for the affected category. Do not load all transport, layer, boundary, and signal guides together.
| Skill | Integration point |
|---|---|
oma-debug | On failure: pull traces + logs by request_id → trigger resources/incident-forensics.md 6-dim localization playbook |
oma-qa | Canary post-deploy loop via chrome-devtools MCP: console errors + Core Web Vitals trend; INP/LCP/CLS from resources/layers/L7-application/web-rum.md |
oma-tf-infra | Terraform modules for OTel Collector, Grafana, and Loki stack provisioning |
oma-scm | Deployment SHA → service.version OTel attribute + release marker events; see resources/boundaries/release.md |
oma-backend | Propagator and baggage rules; DB N+1 + Kafka patterns in resources/signals/traces.md. Back-reference: oma-backend/SKILL.md §References "Observability handoff" |
oma-frontend | resources/layers/L7-application/web-rum.md INP/LCP/CLS checklist. Back-reference: oma-frontend/SKILL.md §References "Observability handoff" |
oma-mobile | resources/layers/L7-application/mobile-rum.md offline-queuing pattern. Back-reference: oma-mobile/SKILL.md §References "Observability handoff" |
oma-db | resources/signals/traces.md DB patterns (N+1, connection pool). Back-reference: oma-db/SKILL.md §References "Observability handoff" |
otel_spec / otel_semconv keys in each file's frontmatter document the assumed version. If content depends on a specific attribute stability tier, the tier is stated inline.resources/standards.md and the affected file, bump minor version.resources/standards.md.vendor-categories.md (Graduated / Archived / acquired) → update the vendor table.https://landscape.cncf.io for CNCF project status. This skill does not promise to track it on any schedule; verify at use time if the information is load-bearing.git log path/to/file to inspect file changes; verify upstream status separately when it affects the task.Run resources/checklist.md §1 Setup validation before merging observability changes.
resources/execution-protocol.mdresources/intent-rules.mdresources/matrix.mdresources/standards.mdresources/vendor-categories.mdresources/incident-forensics.mdresources/meta-observability.mdresources/observability-as-code.mdresources/anti-patterns.mdresources/checklist.mdresources/examples.mdresources/transport/udp-statsd-mtu.mdresources/transport/otlp-grpc-vs-http.mdresources/transport/collector-topology.mdresources/transport/sampling-recipes.mdresources/layers/L3-network.mdresources/layers/L4-transport.mdresources/layers/mesh.mdresources/layers/L7-application/web-rum.mdresources/layers/L7-application/mobile-rum.mdresources/layers/L7-application/crash-analytics.mdresources/layers/L7-application/waf.mdresources/boundaries/multi-tenant.mdresources/boundaries/cross-application.mdresources/boundaries/slo.mdresources/boundaries/release.mdresources/signals/metrics.mdresources/signals/logs.mdresources/signals/traces.mdresources/signals/profiles.mdresources/signals/cost.mdresources/signals/audit.mdresources/signals/privacy.mdfirst-fluke/oh-my-agent
8a03eb1
Also appears in
since Sep 12, 2026
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.