Common Observability Agent Skill
Enforce structured JSON logging, OpenTelemetry distributed tracing, and RED metrics across backend services. Use when adding request correlation, setting up tracing spans, defining SLO burn-rate alerts, or instrumenting middleware.
Install
one command, takes just this skill from the repositorynpx skills add https://github.com/HoangNguyen0403/agent-skills-standard --skill common-observabilityWhat comes with it
3 194 bytes besides the instructionThe instruction itself
7 sections, as written by the authorCommon Observability Standards
Priority: P1 (HIGH)
Logging & Tracing
- JSON Logs: Always emit JSON structured logs. Never plain-text in prod.
- Correlation: Extract
X-Request-Idortraceparent. Attach to async context. - Tracing: Use OpenTelemetry. Propagate W3C
traceparent. - Spans: Name spans like
<HTTP_METHOD> <route>(GET /users/:id).
See implementation examples for structured logger setup with Pino.
Metrics
- Required: Request rate, Error rate, Latency histogram (p50/p95/p99), Saturation.
- SLOs: Alert on SLO burn rates, not raw threshold spikes.
Instrumentation Workflow
- Define the operation and route-normalized span name before adding code.
- Propagate request/trace context across every async or service boundary.
- Log one structured event with correlation fields; redact secrets and request bodies.
- Add RED metrics with route-safe labels, then define an SLO and burn-rate alert.
- Exercise a success and failure path; confirm spans close and IDs join logs to traces.
Anti-Patterns
- Console.log: not use in prod; use structured logger (
pino,zap). - PII in Logs: Never log tokens, passwords, or full request bodies.
- Dynamic Span Names:
GET /users/123causes cardinality explosion. UseGET /users/:id. - Missing Cleanup: Always end tracing spans.
References
- Observability Data Formats
Other skills for the same job
different authors, same section of the catalogue
Query the OFR (Office of Financial Research) Hedge Fund Monitor API for hedge fund data including SEC Form PF aggregated statistics, CFTC Traders in Financial Futures, FICC Sponsored Repo volumes, and FRB SCOOS dealer financing terms. Access time series data on hedge fund size, leverage, counterparties, liquidity, complexity, and risk management. No API key or registration required. Use when working with hedge fund data, systemic risk monitoring, financial stability research, hedge fund leverage or leverage ratios, counterparty concentration, Form PF statistics, repo market data, or OFR financial research data.
Design and automate Extract, Transform, Load data pipelines for data integration and analytics
Track and analyze US government shutdown liquidity impacts by monitoring TGA (Treasury General Account), bank reserves, EFFR, and SOFR data from FRED API. Use when user wants to (1) analyze current or past government shutdown effects on financial markets, (2) track liquidity conditions during fiscal policy disruptions, (3) assess "stealth tightening" effects, (4) compare shutdown episodes across different monetary policy regimes (QE vs QT), or (5) generate liquidity stress reports with historical context. Recommended usage frequency is weekly on Wednesdays after TGA/reserve data releases.
Auto-instrument Node.js applications with distributed tracing, metrics, and logs.
Azure Monitor Query SDK for Java. Execute Kusto queries against Log Analytics workspaces and query metrics from Azure resources.
Azure Monitor Query SDK for Python. Use for querying Log Analytics workspaces and Azure Monitor metrics.
Use this skill when you need to search Datadog logs, query metrics, tail logs in real-time, trace distributed requests, investigate errors, compare time periods, find log patterns, check service health, or export observability data.
Write comprehensive clinical reports including case reports (CARE guidelines), diagnostic reports (radiology/pathology/lab), clinical trial reports (ICH-E3, SAE, CSR), and patient documentation (SOAP, H&P, discharge summaries). Full support with templates, regulatory compliance (HIPAA, FDA, ICH-GCP), and validation tools.
How to use it
Take hoangnguyen0403/common-observability from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.