error-logger

Generate structured JSON logs with correlation IDs for distributed services.

1|Updated Jan 4, 2026
One-click install
npx skills add https://github.com/BarisSozen/claude --skill error-logger
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: error-logger
Source: https://github.com/BarisSozen/claude/tree/main/.claude/skills/error-logger
Command: npx skills add https://github.com/BarisSozen/claude --skill error-logger

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Structured JSON logging with correlation IDs for multi-service systems.

Core Features & Use Cases

  • Standardized JSON log messages across services for easy correlation.
  • Correlation ID generation and propagation via headers to enable end-to-end tracing.
  • Integrates with common logging frameworks and supports levels: error, warn, info, debug.

Quick Start

Start by integrating the logger into your service and passing a correlation ID from the incoming request. Then log events with the context to ensure traceability across service boundaries.

Frequently Asked Questions about error-logger

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

FAQPage Schema
How do I trace requests across distributed services with inconsistent logging?

Trace requests across distributed services by implementing structured JSON logging with correlation IDs. This enforces a standardized log format and propagates correlation IDs via HTTP headers to ensure end-to-end traceability across multi-service architectures.

How do I propagate a correlation ID for structured logging in multi-service architectures?

Propagate a correlation ID for structured logging by passing it via HTTP headers across service boundaries. The logger integrates into your service from the incoming request, ensuring standardized JSON log messages and easy correlation across components.

What log levels are supported for structured JSON tracing in APIs?

Structured JSON tracing in APIs supports common log levels including error, warn, info, and debug. These levels integrate with common logging frameworks to categorize events while maintaining standardized correlation IDs for traceability.

Does structured logging with correlation IDs work for multi-service APIs?

Yes, structured logging with correlation IDs is designed for multi-service APIs where traceability across requests and components is essential. It applies to multi-service architectures by enforcing a standardized JSON log format propagated through HTTP headers.

Why do I need correlation IDs for debugging distributed systems?

You need correlation IDs for debugging distributed systems because they solve the problem of inconsistent logging across services. By generating and propagating these IDs via HTTP headers, you achieve end-to-end tracing and standardized JSON logs for easy correlation.