What problem does it solve? Teams often ship features with inconsistent or missing observability, making production issues hard to diagnose and debug. This Skill enforces a consistent baseline for logging, metrics, tracing, and health checks so every service is diagnosable from day one. ## Core Features & Use Cases - Structured Logging Standards: Enforces JSON or key=value log formats with required fields like timestamp, level, and trace_id, while blocking secrets and PII from logs. - Metrics & Tracing Guidance: Defines minimum instrumentation for latency percentiles, error rates, and distributed trace propagation across service boundaries. - Health Check & CI Visibility Rules: Standardizes health endpoints for CLIs and servers, plus machine-readable test results and versioned build artifacts. - Use Case: When implementing a new API endpoint, apply this Skill to ensure the code emits structured logs with trace context, records p95 latency metrics, and exposes a compliant /health endpoint. ## Quick Start Apply the observability baseline standards to the new feature I am implementing, including structured logging, metrics, and a health check.
