Observability
Add production observability to a service. Use when a service is hard to debug in prod or lacks logging/metrics/tracing. Adds structured logs, key metrics, and trace context — without noise.From its SKILL.md
npx -y skills add vaibhavsaxena022/skills --skill observabilityAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.1 KB, 158 tokens by cl100k_base, as published. Nobody here has run it
Observability
Make the service debuggable in production.
Add
- Structured logs — key events at the right level, each carrying a correlation/trace id. No secrets/PII. No logging in hot loops.
- Metrics — RED for endpoints (Rate, Errors, Duration) plus key business counters; histograms for latency.
- Tracing — propagate a trace/correlation id across the service and its external calls.
- Health — liveness and readiness endpoints.
Rules
- Log intent and outcomes, not noise — every line should be actionable.
- Prefer metrics over log-scraping for rates and latencies.
- Thread one correlation id through a request end-to-end.
- Never log request bodies containing sensitive data.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.