What problem does it solve? Diagnosing slow endpoints, API timeouts, and cascading failures across distributed Node.js services requires sifting through trace data manually. This Skill structures that investigation by analyzing supplied trace trees or querying live N|Solid tracing data to pinpoint bottlenecks and failing endpoints. ## Core Features & Use Cases - Trace Evidence Analysis: Parses provided trace IDs, span trees, status codes, and durations as authoritative evidence before querying live systems. - Live Tracing Queries: Uses N|Solid MCP tools to find slow requests via duration filters and failing endpoints via HTTP status code filters, with app-coverage reconciliation to avoid false absence claims. - Architectural Recommendations: Proposes fixes such as Redis caching, parallelizing independent requests with Promise.all, or message queues, and validates improvements after deployment. - Use Case: A user reports that a checkout API intermittently takes over 2 seconds. The Skill filters traces by duration, identifies the slow service and endpoint, explains the likely cause, and produces a markdown report with a validation plan. ## Quick Start Analyze the attached trace export and tell me which endpoint is causing the latency spike in my checkout service.
