analyze-trace
/analyze-trace
Walk a Lensflare trace span-by-span and explain timing, errors, and parent/child structure. Use when the user pastes a trace id, asks "why is this slow", or wants a request-level post-mortem of a real production / dev request captured in Lensflare.
- Author
- voidhashcom ↗
- Repository
- lensflare ↗
- Licence
- MIT
- Last repository change
- 25.06.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 25.06.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Walk a Lensflare trace span-by-span and explain timing, errors, and parent/child structure. Use when the user pastes a trace id, asks "why is this slow", or wants a request-level post-mortem of a real production / dev request captured in Lensflare.
Triggers from the description
Original author description
Walk a Lensflare trace span-by-span and explain timing, errors, and parent/child structure. Use when the user pastes a trace id, asks "why is this slow", or wants a request-level post-mortem of a real production / dev request captured in Lensflare.
How it works
SKILL.md has no level-two headings · 10 lines, 158 words
SKILL.md preview
--- name: analyze-trace description: Walk a Lensflare trace span-by-span and explain timing, errors, and parent/child structure. Use when the user pastes a trace id, asks "why is this slow", or wants a request-level post-mortem of a real production / dev request captured in Lensflare. --- # Analyze a trace in Lensflare 1. If the user supplied a `traceId`, use it. Otherwise call `lensflare:queryTelemetry` to find a relevant trace (filter by `serviceName`, time, or attributes). Pick the trace whose root span has the highest `durationUs` or whose `status = "error"`. 2. Call `lensflare:getTrace` with the resolved `datasetId` and `traceId`. If it returns `null`, double-check the `traceId` with `queryTelemetry` (`traceId = "<id>"`) before reporting back. 3. Read `summary.spanCount` and `summary.erroredSpanCount`. If errors exist, lead with them: name + service + `durationUs`. 4. Walk `spans` in order. Highlight the longest span, the deepest chain, and any span whose `status = "error"` or whose duration is more than 50% of its parent's. 5. Surface `relatedEvents` only when they materially explain a failure (e.g. an exception event on the failing span). 6. End with a one-line root-cause hypothesis and a suggested follow-up query. Example: _"to see all requests with this error: `attributes.http.status_code = 500 and serviceName = \"api\"`"_.
Versions
The database has no other skills named analyze-trace.
Database snapshot: 13.11.2026 · package version ca32bcba8a55 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 86find-error
Find recent errors in a Lensflare dataset and summarise their root cause. Use when the user asks "what's broken", "what errors are happening", or pastes a vague stack trace and wants the actual failure context from the running system. - 96query-logs
Translate a natural-language question about logs or telemetry into a Lensflare query and return the results. Use when the user asks "find logs that…", "show me…", or describes a filter in prose that should map to a structured query. - 100matlab-instrument-opentelemetry-tracing
Add OpenTelemetry tracing to MATLAB code. Use when the user asks to "add tracing", "instrument with spans", "add OpenTelemetry", "trace my code", "add observability" (when about tracing), or mentions "spans", "distributed tracing", or "OTel tracing" in the context of MATLAB… - 100span-timeline-events
Use when adding, modifying, or debugging OTel span timeline events in the trace view. Covers event structure, ClickHouse storage constraints, rendering in SpanTimeline component, admin visibility, and the step-by-step process for adding new events. - 100dt-obs-tracing
Distributed traces, spans, service dependencies, and request flow analysis. Use when investigating span-level details, failures, performance bottlenecks, or trace correlation. Trigger: "trace analysis", "slow requests", "failed spans", "service dependencies", "distributed… - 100trace-diagram
Draw a trace as an interactive, self-contained sequence diagram (archify) from its Grafana Tempo spans, without investigating it. Use when the user wants to see, share or export the call sequence of a trace id - who called whom, where the time went, which span failed first - and…