observability

Review Node.js and TypeScript code for OpenTelemetry observability standards.

3|1|Updated Mar 11, 2026
One-click install
npx skills add https://github.com/jon23d/skillz --skill observability-jon23d
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: observability
Source: https://github.com/jon23d/skillz/tree/main/skills/observability
Command: npx skills add https://github.com/jon23d/skillz --skill observability-jon23d

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the critical need for code to be observable in production, ensuring that developers can understand system behavior through logs, metrics, traces, and health checks.

Core Features & Use Cases

  • Defines Observability Standards: Establishes clear guidelines for the four key observability signals: logs, metrics, traces, and health.
  • Promotes Best Practices: Details universal principles and stack-specific conventions (e.g., Node.js/TypeScript with OpenTelemetry) for implementing observability.
  • Use Case: When reviewing a new microservice, load this skill to ensure it emits structured logs with correlation IDs, measures key performance metrics, propagates trace context, and exposes a meaningful health endpoint.

Quick Start

Use the observability skill to review the attached code for adherence to logging standards.

Frequently Asked Questions about observability

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I ensure my Node.js code is observable and debuggable in production?

Code review for observability involves checking if a service emits structured logs with correlation IDs, measures performance metrics, propagates trace context, and exposes a meaningful health endpoint. This skill facilitates that review process to identify and rectify observability gaps.

What are the key observability signals I need to implement for a new microservice?

The four key observability signals you need to implement are logs, metrics, traces, and health checks. This skill defines these observability standards and details universal principles for applying them effectively across your software development lifecycle.

Does this observability skill provide specific guidance for TypeScript and OpenTelemetry?

Yes, this skill provides stack-specific conventions for implementing observability in Node.js and TypeScript using OpenTelemetry. It details how to properly instrument your code with logs, metrics, traces, and health checks for these specific technologies.

How do I add tracing and health checks during a code review?

During a code review, you load this observability skill to check adherence to instrumentation conventions. It identifies missing trace context propagation and verifies that services expose meaningful health endpoints, rectifying observability gaps before deployment.

When do I need structured logging with correlation IDs for application monitoring?

You need structured logging with correlation IDs when reviewing microservices to ensure code is observable in production. This skill enforces logging standards to guarantee logs are properly structured and correlated for effective application monitoring.