ns-analyze-tracing
Analyzes N|Solid/OpenTelemetry tracing evidence for request latency, HTTP errors, and service dependencies. Use when the user asks about slow endpoints, API timeouts, distributed traces/spans, N+1 queries, await chains, microservice latency, cascading failures, or trace IDs. Query N|Solid only when no trace data was provided. Builds the span waterfall with `tracing-detail` when the console offers it.
Install
With your agent
Install OMGSkills skill "nodesource/nsolid-plugin:skills/ns-analyze-tracing" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.
Manual command
git clone https://github.com/nodesource/nsolid-plugin /tmp/nsolid-plugin && ln -s /tmp/nsolid-plugin/skills/ns-analyze-tracing ~/.claude/skills/ns-analyze-tracingFrom README
Use Provided Trace Data First Treat the prompt as primary evidence. Parse any provided trace ID, span list, app name, endpoint name, status code, duration, or error stack before calling tools. If the user supplied a trace tree/export or any other host-provided trace data, treat it as authoritative: map that hierarchy directly and do not fall through to live enrichment (information-dashboard, tracing, tracing-detail), even when the export includes its trace ID. The connected-services discovery (step 2) and live tracing queries (steps 3–4) are only for when no sufficient host data is present. If the user supplied only a trace ID (not a full tree), call tracing-detail with spantraceId and showLimit: 150. Every span comes back whole, so a bigger page can pass the client's limit on tool output. If the metadata's totalSpans is at most 150, that is the whole trace. If it is larger, don't ask for more: say the waterfall covers returnedSpans of totalSpans spans, in no particular order.
More from this repo
ns-audit-dependencies
Audits a local Node.js project dependency tree with NCM vulnerability data.
ns-switch-org
Switches which NodeSource organization nsolid-plugin is authenticated against.
ns-memory-spike-analysis
Diagnoses memory growth, heap spikes, RSS increases, OOMs, and suspected leaks in Node.js apps using supplied heap...