otel-trace-analysis

Analyze OpenTelemetry trace JSON to diagnose latency, errors, and dependency bottlenecks.

5|Updated Mar 11, 2026

Search Tags:#debugging #distributed systems #tracing #latency #performance analysis #errors #otel

Ready to run

npx skills add https://github.com/SteveFeldman/agents-skills --skill otel-trace-analysis

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: otel-trace-analysis
Source: https://github.com/SteveFeldman/agents-skills/tree/main/skills/otel-trace-analysis
Command: npx skills add https://github.com/SteveFeldman/agents-skills --skill otel-trace-analysis

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you pinpoint performance bottlenecks, errors, and unexpected behavior within distributed systems by analyzing OpenTelemetry traces.

Core Features & Use Cases

Deep Trace Analysis: Provides a comprehensive breakdown of trace execution, including critical paths, error sources, and dependency performance.
Triage Mode: Offers a quick summary for rapid issue identification when time is critical.
Use Case: When a user reports slow API response times, you can use this Skill to analyze the OTEL trace, identify the specific service and operation causing the latency, and understand the root cause of any errors.

Quick Start

Analyze the provided OpenTelemetry trace JSON file for performance issues.

Frequently Asked Questions about otel-trace-analysis

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

FAQPage Schema

How do I diagnose latency bottlenecks in distributed systems using OpenTelemetry traces?▼

To diagnose latency bottlenecks in distributed systems, this Skill parses OpenTelemetry trace JSON data to identify span relationships, timing anomalies, and dependency performance issues. It highlights critical paths and pinpoints the specific operations causing delays.

Can I analyze OpenTelemetry traces for error propagation and retries?▼

Yes, you can analyze OpenTelemetry traces for error propagation and retries. The Skill examines trace spans to track how errors propagate across services and identifies retry patterns to help locate the root cause of unexpected behavior.

What is the best way to quickly triage slow API response times from trace data?▼

The best way to quickly triage slow API response times is using the Skill's triage mode, which provides a rapid summary of the OpenTelemetry trace. This allows for fast issue identification when time is critical before conducting a full investigation.

Do I need to provide trace data in a specific format to analyze distributed system performance?▼

Yes, you need to provide trace data in OpenTelemetry JSON format. The Skill requires parsing JSON trace data to evaluate span relationships, identify timing anomalies, and accurately diagnose distributed system performance issues.

How does deep trace analysis differ from a quick summary when debugging performance issues?▼

Deep trace analysis provides a comprehensive breakdown of trace execution including critical paths and dependency performance, while a quick summary offers rapid issue identification. Both methods debug performance issues but differ in investigation depth.