Observability and telemetry engineering skill. Enforces OpenTelemetry distributed tracing, structured JSON logging with correlation IDs, and health probes.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Observability & Distributed Telemetry (`/observability`)
> **Philosophy**: *If it cannot be observed in production, it cannot be debugged. Correlate every log with a trace ID. Instrument every RPC boundary. Never emit unredacted PII.*
This skill establishes production observability standards across backend microservices, serverless functions, background workers, and containerized platforms.
---
## 1. Quick Navigation & Progressive Disclosure
| Resource Type | Document | Description |
| :--- | :--- | :--- |
| **Reference** | [references/opentelemetry-semantic-conventions.md](references/opentelemetry-semantic-conventions.md) | W3C traceparent headers, span semantic attributes for HTTP/DB/RPC. |
| **Reference** | [references/structured-json-logging.md](references/structured-json-logging.md) | JSON log schemas, correlation IDs, PII redaction rules. |
| **Utility** | [scripts/verify_telemetry_standards.py](scripts/verify_telemetry_standards.py) | Audits services for console.log statements, missing correlation IDs, and uninstrumented endpoints. |
---
## 2. The Three Pillars of Telemetry
```mermaid
flowchart TD
subgraph Ingestion["1. Trace Context Injection"]
…
The line at the top of this page pins the label git:20261029.1aa6bef, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
GET https://markdownregistry.com/api/v1/artifacts/art_u64vypihfv3synoe
GET https://markdownregistry.com/api/v1/resolve?ref=darknecrocities/skillbuilder/.cursor/rules/observability.mdc
GET https://markdownregistry.com/api/v1/blob/ffa5575b825fb607981344a262f37e43d1ab1037d6ecff2b50c99b43b2691b1e
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
darknecrocities/skillbuilder · .cursor/rules/ai.mdc · Architect, implement, and maintain production AI systems, Gemini API agents, Antigravity multi-agent orchestration…
ericrisco/rsc-harness · skills/observability/SKILL.md · Use when instrumenting a service from the inside so an incident can be explained from telemetry alone — wiring…
nahid-sparktales/agent-dispatcher · skills/devops/observability/SKILL.md · Instrument a service so the questions asked during an incident are answerable from data already being collected — rate…
rjmurillo/ai-agents · .claude/skills/observability/SKILL.md · Use when you say `query agent logs`, `find slow tool calls`, `show agent errors`, or `what to log`. Query and analyze…
rjmurillo/ai-agents · src/claude/skills/observability/SKILL.md · Use when you say `query agent logs`, `find slow tool calls`, `show agent errors`, or `what to log`. Query and analyze…
outlinedriven/odin-claude-plugin · plugins/odin-infra/skills/observability/SKILL.md · Use when adding telemetry, composing an observability surface, reviewing alerts, shipping a production feature, or…